This didna€™t remain completely really with me, and ita€™s perhaps not because ita€™s some disturbing to create a fresh subfolder per blog post a€” i really could easily make a program or projects to one-line that section everytime (like rake post within my Jekyll website).

It actually was more because if We comprise to switch how blog post data is structured, Ia€™m unsure that Ia€™d like it to be the Wintersmith default ways. Watching most of the blog post files with day and brands in a single destination merely appeared more convenient. Additionally, easily could get it to be hired in Wintersmith, ita€™d mean I could duplicate my personal posts nearly undamaged from _posts in Jekyll to contents/articles .

Nevertheless, used to dona€™t need figure it outa€¦ a man by the name of Andrew Clark (whoa€™s own Wintersmith weblog we leaned on heavily in this migration) customized Wintersmith to scrape a single folder for uniquely called Markdown documents a€” exactly as i desired. The important thing was a student in Wintersmitha€™s plugin/paginator.coffee ; specifically, this bit:

Which Andrew changed into this:

a€¦leveraging the filename as opposed to the directory site names to create several articles (that are actually pages , which have been really my personal stuff). And with that, i really could literally copy most of my personal blog post documents from _posts/ to contents/articles .

Altering Permalinks

Wintersmith content and pages automagically bring urls like /this-is-my-post-title/index.html , because of the one-for-one mapping in the subfolders under contents/articles . Read more