Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

decide: should we include a Draft vs. Public view? #32

Open
jensbri opened this issue Dec 12, 2023 · 1 comment
Open

decide: should we include a Draft vs. Public view? #32

jensbri opened this issue Dec 12, 2023 · 1 comment
Assignees

Comments

@jensbri
Copy link
Collaborator

jensbri commented Dec 12, 2023

The idea is that we might want to collect ideas in a md file in the appropriate location of the folder structure.
Maybe each thing has to be tested anyways.
Or approved by the relevant person.
And we could flag it in the yml header that only approved ones
we could also integrate a time-component, so make us check the guides every year if they are still relevant (think: offboarding approach where one year after creation an email is sent to the user, so we'd need a user responsible for each one but we don't want to share email addresses... )

@jensbri jensbri self-assigned this Dec 12, 2023
@neon-ninja
Copy link
Member

neon-ninja commented Dec 13, 2023

branches would be the way to go here imo, Netlify would even build and host them. a PR from a branch to main could have an approver

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants