feat(blog+seo): 12-post blog, 14 FAQs, hero tagline (missed by PR #9 merge) - #10
Merged
Conversation
- Grow the FAQ list from 6 to 14 keyword-targeted Q&As (biodata format, biodata with photo, bride/groom, resume vs biodata, WhatsApp sharing, no sign-up, etc.) — answers kept accurate to what the app does. - Add a "fast, easy and free biodata maker" positioning line in the hero. - Add a short, human-readable intro/about section with the primary keywords woven in naturally (no stuffing). lint, test (50) and build all green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- New /blog index and statically-generated /blog/[slug] pages (all 12 posts prerendered at build time → fast, fully indexable). - 12 keyword-targeted articles (how-to, biodata format, photo tips, biodata for girl/boy, shaadi format, biodata vs resume, etc.) covering short- and long-tail queries, each linking back to /create. - Article + BreadcrumbList JSON-LD per post; Blog JSON-LD on the index. - Per-post canonical + OpenGraph article metadata. - Markdown rendered statically via react-markdown (no client JS), styled with Tailwind component map (no typography plugin). - Blog routes added to the sitemap. - Pure, unit-tested helpers in src/lib/blog.ts (11 new tests, incl. an integrity check that every in-body link points to a real route). - Add a privacy-friendly Feedback (mailto) link + Blog nav links — no third-party chatbot, keeping the data-stays-local promise. react-markdown + remark-gfm added (build-time only, zero client bundle). lint, test (61) and build all green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
pythonsst
added a commit
that referenced
this pull request
Jun 28, 2026
feat(ui): premium wedding-luxury redesign (+ blog & FAQ from #10)
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
1 participant
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.
Why this PR exists
PR #9 was merged while the branch only had its first commit. The next two commits — the FAQ expansion and the entire blog — landed after the merge and never reached
main. This PR brings them in.What's included (the part of the SEO work missing from main)
/blog+ statically-generated/blog/[slug]pages (how-to, biodata format, photo tips, biodata for girl/boy, shaadi format, biodata vs resume, family details, mistakes, WhatsApp sharing, Word vs online).articlemetadata.react-markdownat build time → zero client JS.Quality gates (re-run against current main)
npm run lint✅npm test✅ — 61 passing (18 SEO/blog tests, incl. an integrity check that every in-body link resolves)npm run build✅ — all 12 posts prerendered as static HTMLClean merge: based on the commit already in main, so the diff is exactly the two unmerged commits.
🤖 Generated with Claude Code