devopsmigrationhellodklaunch

Launch Checklist: What Still Needs Fixing Before hellodk.io Goes Live

Deepak Gupta · ·4 min read
Launch Checklist: What Still Needs Fixing Before hellodk.io Goes Live

TL;DR — The theme and integrations are ready. Thirteen of twenty-two published posts still need body work (thin stubs, legacy HTML, or migration debris). You own secrets, DNS, and personal content. Scripts and agent passes can restore and rewrite the rest from _jekyll-backup.

For the interactive version with animated diagrams, see the visual content migration guide.

Where problems live

The homepage can look great while individual posts still hurt. These are separate layers:

  1. Layout C (theme) — Cards, hero, sidebars, search, chat. Done.
  2. Post markdown body — src/content/blog/*.md. 13 posts need work.
  3. Reader view — Title + cover + prose. Only as good as the body.

Published posts audit (22 scanned)

StatusCountMeaning
Clean9Proper markdown, headings, readable — ship as-is
Thin4Title exists; body is notes or wrong topic
HTML-heavy6Legacy Jekyll <p> / <ul> markup — needs conversion
Migration junk3Chirping layout text baked into the body

Clean (9)

Thin (4) — restore or rewrite

PostIssue
Exploring the Linux top CommandBody is QEMU/Vagrant commands — wrong topic
Generating SSL CertificatesStub — only a few lines
Vagrant with QEMU/KVMCommand fragments, not an article
Understanding DNS RecordsProse wrapped in <html> tags, no headings

HTML-heavy (6) — convert to markdown

PostIssue
Kubernetes Cluster on VagrantLegacy HTML lists
MySQL Master-Master ReplicationLegacy HTML from Jekyll
Understanding LVM BasicsHeavy <ul> / <code> HTML
Yum Commands Quick ReferenceHTML table/list reference
The Road to KingdomFiction — HTML paragraphs (manual review)
DataStax Cassandra CertBody may be wrong post — verify source

Migration junk (3) — strip debris

PostIssue
kri + graphify Knowledge GraphChirping sidebar chrome in body
macOS VMs with tart + SaltBroken heading lines + layout debris
Browser RDP Zero PortsLiquid/code-fence artifacts possible

Who does what

You

  1. Cloudflare environment variables — PUBLIC_GISCUS_*, PUBLIC_BREVO_FORM_URL, PUBLIC_GA4_ID, PUBLIC_GOATCOUNTER_CODE, PUBLIC_CF_BEACON_TOKEN. See docs/LAUNCH-CHECKLIST.md.
  2. Workers AI binding — Bind Workers AI as AI in Cloudflare Pages → Functions. Without this, chat uses search-only fallback. See wrangler.toml.
  3. Contact form secret — BREVO_API_KEY + CONTACT_* emails for /api/contact. See .env.example.
  4. Domain redirects — hellodk.in → hellodk.io and www → apex. See docs/cloudflare-dns.md.
  5. Personal / fiction posts — Review The Road to a Kingdom and any draft fiction — only you can judge tone and privacy.
  6. Proofread after auto-rewrite — When posts are restored from _jekyll-backup, skim for accuracy.
  7. 44 legacy drafts — Files in _drafts/ and _jekyll-backup/_drafts/ — decide publish, merge, or archive.

Scripts / agent passes

  • Run scripts/fix-empty-posts.mjs against _jekyll-backup HTML sources
  • Convert html-heavy posts to clean markdown (headings, lists, code blocks)
  • Rewrite thin posts from backup or scratch using original intent
  • Strip Chirping migration junk (“On This Page”, sidebar blocks)
  • Fix wrong-body duplicates (e.g. Cassandra cert vs K8s cluster)

Say “fix all html-heavy posts” or “fix thin posts from backup” to run the next batch.

Enjoyed this post?

Get the next one in your inbox — only when I ship something worth reading.

Newsletter form not configured.

Or follow on Substack for the newsletter.

Comments via GitHub Discussions

Comments not configured. Set GISCUS env vars to enable.

Related Posts