Skip to content

Expand development environment order recommendations with rationale and how-to guidance #434

Description

@coderNini

Summary

The Notes section recommends a development order but does not explain why, what the risks entail, or how developers should actually work in each environment.

Proposed Changes

  • Explain the reasoning behind the recommended development order
  • Describe what the risks of deviating from the order actually are
  • Provide instructions for how to begin developing in each environment
  • Define what "developing in an environment" means in practice: how do developers switch between environments, and how can they verify which environment they are currently in?

Make changes in #408 (and refer to comments for further detail)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions