Closed jcdwyer1 closed 10 years ago
To solve this issue I broke press releases and products out in to collections of their own. In other words, press and products will not live in the _posts
directory alongside blog posts; instead they will live in the _press
and _products
directories, respectively.
Within each of the new directories I created subdirectories that organize markdown files by date for ease of content management.
Thank you. Questions for our call this afternoon: 1) Blog posts do not currently have year/month subdirectories, and Press posts do not have a month subdirectory; do you recommend I create these for consistency? 2) Will this approach end up crowding the Github folder interface as I create more subdirectories?
Questions were answered on our call today.
In summary:
_products
and _posts
directories will show up at the top level once more content is added (i.e. empty directories are shows in grey in github).
When a new post is created, regardless of post type the resulting auto-generated URL includes the "/blog/" directory. Not a big deal, but ideally different types of posts (e.g. press, product) would get their own directory listings in their URLs, or else perhaps we could change /blog/ to something more generic?