Migrate blog from 11ty to Nuxt - #5441
Open
ZJvandeWeg wants to merge 3 commits into
Open
Conversation
Reuses the changelog migration's shape: a content.config.ts collection
sourced directly from src/blog/**/*.md, a catch-all page handling the
index, 13 tag listings (with pagination), post detail, and an RSS feed
server route. Posts stay at their existing src/blog/YYYY/MM/slug.md
location. Reuses HandbookToc, AlgoliaSearch, TeamCardSmall, and
HubSpotForm rather than rebuilding them.
Also fixes two pre-existing bugs surfaced by this change: customer-stories.njk
checked the wrong collection for its empty-state, and llms.njk's blog
section relied on collections.posts, which is now empty since 11ty no
longer processes blog markdown (replaced with src/_data/blogPosts.js).
One post had frontmatter that failed strict YAML parsing, and another had
a leftover Nunjucks {% include %} baked into a raw href.
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
BlogPagination and ChangelogPagination were identical apart from a hardcoded base path; merged into a single Pagination component. Also extracted the repeated authors -> team-member/name mapping (duplicated across both list items, the featured blog post, and both post detail pages) into useAuthorMembers/useAuthorNames in useTeam.
ZJvandeWeg
marked this pull request as ready for review
July 31, 2026 17:35
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Fixes prerender 404: @nuxt/content lowercases page paths via slugify, but the source filename had mixed case, so the SSG build generated a route that never matched the actual content path.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/blog(index, 13 tag listings + pagination, post detail, RSS feed) from Eleventy to Nuxt, following the same pattern established by the changelog migration (Migrate changelog from 11ty to Nuxt #5420). Posts stay at their existingsrc/blog/YYYY/MM/slug.mdlocation.HandbookToc,AlgoliaSearch,TeamCardSmall,HubSpotForm,useTeam.customer-stories.njkwas checkingcollections.posts.length(should becollections.stories) for its empty-state fallback.llms.njk's Blog Posts section relied oncollections.posts, which is now empty since 11ty no longer processes blog markdown — replaced with a smallsrc/_data/blogPosts.jsthat reads frontmatter directly.{% include %}baked into a rawhref, which crashed the Nuxt markdown parser.Test plan
npm run dev:nuxt: verified/blog/, a post detail page, a tag listing, tag pagination, and/blog/index.xmlall render correctly (hero image, video embed, TL;DR, FAQ, related articles, sign-up form, pagination links).eleventybuild succeeds with no errors;/blogoutput is images-only (no HTML), confirming 11ty no longer renders blog pages.customer-storiespage andllms.txtverified to still list content correctly after the collection change.🤖 Generated with Claude Code