cmneal26 / Tech-Writing-Project

Class repository
2 stars 1 forks source link

Edit: Edit our-mission page content #56

Closed ghost closed 2 years ago

ghost commented 2 years ago

We now have a space within our git workflow to focus on content. Treat the documents in the 'drafts' folder as more of a playground where we can worry about editing and content outside the constraints of the technology. This seems especially important when the content itself is difficult.


ghost commented 2 years ago

clarification note: We aren't actually going to use this drafts folder in our workflow for this project. Why? Because for this project, it's fine to update the production website with partially completed content (everyone needs easy access to partially completed content for editing). This will allow us to iterate faster by viewing the current version of any content-heavy page on our production site, and then returning to the PR for that partially completed thing, and commenting, but using the visual representation and not the markdown PR as the source for the editing advice.

If we're not going to use it in our workflow, then why did I add it? Because usually you can't put partially complete content on a production site. So, in that case, you would want somewhere to store the partially completed work. Just work in the drafts folder, and then when you want to see the visual representation paste it into the actual page index.md file. But don't commit it, and delete the partial content when you're done viewing it.