Read on Twitter
When its just me managing content on my site, I go jamstack. Jekyll + Netlify 
But once I need to delegate blog posting to someone, there still isn’t an easy/fast setup for that.
I might begrudgingly port the site to WP just to have blog post publishing CMS.
But once I need to delegate blog posting to someone, there still isn’t an easy/fast setup for that.
I might begrudgingly port the site to WP just to have blog post publishing CMS.
I tried implementing NetlifyCMS and Forestry.
Both were clunky, hard for my team to use, preview posts, etc. And both have a painful wait time for deployment just to see changes.
Both were clunky, hard for my team to use, preview posts, etc. And both have a painful wait time for deployment just to see changes.
Also—I don’t want to spend time rebuilding the site. I *just* want to plug in simple CMS-ability *only* for blog posts. I’ll continue to manage the other pages in code.
Why is this such a pain?
Why is this such a pain?
Conclusions:
1. The internet needs more CMS’s (hah!). Tried many of em now.
2. Wordpress still checks all the boxes for a blog CMS (inviting team, saving drafts, scheduling, previewing, etc.).
3. My static pages will remain HTML wrapped in WP theme. Kinda rediculous.
1. The internet needs more CMS’s (hah!). Tried many of em now.
2. Wordpress still checks all the boxes for a blog CMS (inviting team, saving drafts, scheduling, previewing, etc.).
3. My static pages will remain HTML wrapped in WP theme. Kinda rediculous.
