How to author content locally? #246
-
We've installed Outstatic on our Next.js website. It's awesome, but I'd like to avoid pushing unfinished posts to I want to have a workflow I had with Hugo/Jekyll:
This process keeps Instead, what I'm doing now - I create a post with Outstatic, pull from main, edit the markdown locally, create a PR, merge to Is there a way to use Outstatic with local files? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
Hey, |
Beta Was this translation helpful? Give feedback.
-
Just want to 2nd this. In addition to keeping the git history to a minimum, I'd also like to call out the metadata doesn't 100% catch up with content changes (especially around deletes). Local would, I think, make this a tad more efficient (given it's essentially a search index file roll-up of the files themselves). Wouldn't need to traverse the branch from afar and commit changes, but instead could monitor/track local. In addition, I could see the "publish" behavior (in "local mode") as the final commit of the content itself and the metadata changes. Just a thought. |
Beta Was this translation helpful? Give feedback.
-
Personally, I would love it if Outstatic could create files and metadata.json entry for a new post without a commit. I prefer editing Markdown directly and would love to be able to run a script to create a new post that I could work on locally and publish as a single commit when it's ready. |
Beta Was this translation helpful? Give feedback.
Hey,
Unfortunately Outstatic doesn't currently support saving to local files.
I'm adding the ability of picking the branch you want to work with in the next version.