Fix home page copy and remove leftover template FAQ section

[MorganGodden]

Fixes the copy errors on the home page and strips the starter-template content that was still sitting in content/index.yml.

1. "Software Engineer developer" in the OG thumbnail

seo.description read "a Software Engineer developer based in the United Kingdom" — redundant, and it read as a mistake. app/pages/index.vue passes this field to both useSeoMeta and defineOgImage('Portfolio', …), so the phrase was baked into the social share card as well as the meta description.

The replacement is also shorter, for a reason worth noting: app/components/OgImage/Portfolio.takumi.vue clamps the description to 2 lines. The old string was 209 characters, well past what fits, so the card was truncating mid-sentence — which is why the odd phrase was so prominent in the visible portion. The new string is 130 characters and fits within the clamp.

Before: Welcome to my portfolio! I'm Morgan Godden, a Software Engineer developer based in the United Kingdom. I specialize in creating user-centered digital experiences that are both beautiful and functional.

After: I'm Morgan Godden, a UK-based Software Engineer creating user-centered digital experiences that are both beautiful and functional.

2. Hero said "Based in Boston"

The hero description claimed Boston, contradicting the United Kingdom used in nuxt.config.ts (site.description), content/about.yml, and the meta description. Changed to the United Kingdom.

3. Hero title missing punctuation

title read "Hi, I'm Morgan Godden Software Engineer". Now "Hi, I'm Morgan Godden, a Software Engineer".

Both of these fields are hero-only on the home page — seo.title and seo.description take precedence for the meta tags and OG image, so neither affects the share card.

4. Removed the leftover template FAQ section

The faq block was unmodified starter-template content: UX/UI agency services, USD pricing ($5,000 engagements, a $700 day rate), deposit and retainer terms, and hobbies set in Boston. None of it described this site.

LandingFAQ was never rendered by any page, so the block was data-only, but it still shipped in the prerendered content payload. Removing it takes three coupled changes:

• drop the faq block from content/index.yml
• drop the faq schema from content.config.ts — it was a required key, so collection validation would fail without it
• delete the orphaned app/components/landing/FAQ.vue, which read page.faq and no longer type-checks against the collection

This also clears the last US references in the repo. grep for boston|$<digits>|USA?|united states across all .yml/.ts/.vue/.md now returns nothing.

Testing

Installed dependencies and ran the real build this time, since the schema change is riskier than a string edit:

• npm run build — passes; the content collection validates without the faq key
• Verified the prerendered .output/public/index.html carries the corrected og:description and description meta tags
• Rendered the generated home page OG PNG and confirmed the new description fits in 2 lines with no mid-sentence truncation
• Grepped the built output for boston, USD amounts, "frequently asked", and "day rate" — no leakage
• npm run lint reports 41 pre-existing problems in app/app.vue and app/pages/about.vue, both untouched here. Confirmed identical on master; the files changed in this PR are lint-clean.

Deployment note

nuxt.config.ts sets ogImage: { zeroRuntime: true }, so cards are generated at build time — this needs a redeploy to take effect. Social platforms also cache scrapes, so the URL may need re-scraping in Facebook's Sharing Debugger / LinkedIn's Post Inspector to pick up the new image.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
godden.dev	Ready	Preview, Comment	Jul 28, 2026 2:32pm