Migrate customer stories to Nuxt - #5596
Open
ZJvandeWeg wants to merge 6 commits into
Open
Conversation
Serve /customer-stories/** through Nuxt (StoryTile component + listing/detail pages) while keeping source markdown at src/customer-stories/ and giving 11ty's copy permalink: false so the few live 11ty pages that still read collections.stories keep working without 11ty writing output files.
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Yndira-E
approved these changes
Aug 14, 2026
Yndira-E
enabled auto-merge
August 14, 2026 16:06
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
/customer-stories/**through Nuxt: newstoriescontent collection (source stays atsrc/customer-stories/),StoryTile.vue, and listing/detail pages undernuxt/pages/customer-stories/.src/customer-stories/customer-stories.jsonsetspermalink: falseso 11ty keeps populatingcollections.stories(still read bysrc/landing/tulip.njk,src/node-red/index.njk,src/_includes/stories-block.njk) without writing duplicate output files;.eleventyignoredrops the oldsrc/customer-stories.njklisting template.nuxt/content.config.ts:logo/story.urlmade nullable to handle blank YAML keys (logo:with no value parses asnull, not omitted).images/...→./images/...) to resolve correctly under Nuxt Content.storiesto the sitemap content sources and/customer-storiesto Nuxt's dev-proxy prefixes; dropped the now-unneeded redirect for a retired stories slug.Test plan
npm run dev:nuxt→ verify/customer-stories/listing and an individual story page render correctlysrc/landing/tulip.njk,src/node-red/index.njk, andsrc/_includes/stories-block.njkstill render their story blocks from 11ty