I have a ton of stuff I want to write about, yet I rarely do. The reason is very simple... it's the following checklist to publish a new blog post:
- [ ] Create branch
- [ ] Run `npm run generate` to create a new blog post
- [ ] Write post in Google Docs, use Markdown where necessary (e.g. headings, lists, etc.)
- [ ] Copy content to `src/routes/blog/{slug}/index.svx`
- [ ] Add jpg assets to `static/blog-posts/{slug}/`
- [ ] Run `npm run images` in the `services/website` directory to generate next-gen image formats
- [ ] Open PR & review preview deployment
- [ ] Record the code review video and publish to the Software Architect's YouTube channel
- [ ] Link from the YouTube video to the PR
- [ ] Update the blog post and link to the YouTube video
- [ ] Merge PR
- [ ] Share on Twitter
- [ ] ? Cross-post to DEV. GitHub Actions step on master only. Update on DEV if post exists ?
☝️ that is, scientifically said, bananas 🍌!
What I need instead is this:
- [ ] Write post in Google Docs, use Markdown where necessary (e.g. headings, lists, etc.)
- [ ] Start dev workspace
- [ ] Answer new post questions in the terminal
- [ ] Copy content to `src/routes/blog/{slug}/index.svx`
- [ ] (optional) Add jpg assets to `static/blog-posts/{slug}/`
- [ ] Open PR & review preview deployment
- [ ] Merge PR
- [ ] Share on Twitter
- [ ] ? Cross-post to DEV. GitHub Actions step on master only. Update on DEV if post exists ?
What does that mean under the hood?
Image assets should be optimized automatically, ideally let a GitHub Action deal with that
Remove a post's header image - worse social media preview and possibly worse SEO, which is fine
I have a ton of stuff I want to write about, yet I rarely do. The reason is very simple... it's the following checklist to publish a new blog post:
☝️ that is, scientifically said, bananas 🍌!
What I need instead is this:
What does that mean under the hood?