Skip to content

[checklist] Standardise guides & blueprints #3

@sabman

Description

@sabman

When we create a blueprint or a guide:

  • I have a standard section for prerequisites
  • I have a standard .env.example
  • I have a standard migrations directory structure and instructions

We can create a template repo for this then always fork from it to create our guides and blueprints

related https://github.com/decision-labs/auth-geobase-svelte/issues/1

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    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