3 ms·
Coming from wordpress to a website that uses markdown for posts I have run into a few problems or inconvenience that I haven't seen addressed. There's a lot of
by wodenokoto 10y ago
Coming from wordpress to a website that uses markdown for posts I have run into a few problems or inconvenience that I haven't seen addressed.
There's a lot of boiler-plate in markdown posts. Author, date, etc. Wordpress does all this for you.
My editor doesn't know which categories, authors or tags already exists. I can't remember if I use the category "car" or "cars".
I haven't found a nice way of handling inline images.
- ryanSrich 10y agoThat's not a markdown problem. Its a consequence of using markdown within a framework, generator, etc that uses frontmatter or an equivalent to define meta data. Several frameworks and tools allow for markdown and static site rendering that also support an admin UI where one can define this data more easily.
- iamdave 10y agoalso support an admin UI where one can define this data more easily. I'm looking for one such or a couple, can you enumerate?
- ryanSrich 10y agoNot all of these fit the bill exactly, but they all have their own advantages. - prose.io - siteleaf.com - statamic.com - getkirby.com - github.com/jekyll/jekyll-admin - github.com/netlify/netlify-cms - federalist.18f.gov You can also always build your own on top of whatever generator you want to use (example: http://willschenk.com/building-a-gui-for-managing-middleman-blogs/ http://willschenk.com/building-a-gui-for-managing-middleman-...). My favorite setup though is middleman + contentful + codeship. Static site generation happens with middleman. Content management happens with Contentful. Publishing happens with codeship.
- daviddumenil 10y agoThat's interesting in that it suggests why more blogs don't follow Daring Fireball's style.