Moving from WordPress to Jekyll (and static site generators in general)
7 hours ago
- #Static Site Generator
- #WordPress Migration
- #AI Development
- Migration from WordPress to Jekyll driven by preference, speed, and ease of changes.
- Speed issues and developer bottlenecks with WordPress; AI agents like Claude Code facilitated migration.
- Jekyll chosen for maturity and familiarity, using static site generation without a database.
- Content migration leveraged GSC tools and Claude Code to filter and transfer 288 posts.
- AI-assisted development enabled building dev tools for auditing site structure, Lighthouse, schema, and more.
- Client-side search implemented with local JSON file, eliminating external dependencies.
- SEO architecture includes structured data, automated FAQ schema, environment-aware configurations, and CSP headers.
- Production cutover on Cloudflare Pages with staging and production environments, addressing DNS and favicon issues.
- Future tasks include image optimization and improving post categorization.