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

posts: drafts #129

Closed
mhanberg opened this issue Apr 2, 2025 · 1 comment
Closed

posts: drafts #129

mhanberg opened this issue Apr 2, 2025 · 1 comment
Labels
enhancement New feature or request extension:posts good first issue Good for newcomers

Comments

@mhanberg
Copy link
Collaborator

mhanberg commented Apr 2, 2025

Problem

Other than branching in version control, you can't draft a post and have it not build in production.

Having this as a first class concept is important to ensure that other extensions that use posts don't have to worry about it, similar to how the PostExtension currently handles "future" posts

Solution

Add in the first class concept of drafts.

  • A _drafts folder (configurable), where posts in there are only shown when configured (controlled via application config for the PostExtension)
  • a drafts: true frontmatter key, does the same as the above.
@mhanberg
Copy link
Collaborator Author

Closed by #130

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request extension:posts good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant