Phase 7 - Content
What performance challenges are you facing? I’d love to hear about your optimization wins and struggles. Reach out on Twitter or email me.
Overview
Section titled “Overview”- Track: Both (MVP & Showcase)
- Duration: 3-5 days
- Dependencies: Phase 0-6 completed
- Deliverables: Written content, optimized images, meta descriptions, content fixtures
Entry Criteria
Section titled “Entry Criteria”- [ ] Content architecture defined (Phase 1)
- [ ] Page sections built (Phase 6)
- [ ] Image optimization pipeline ready
- [ ] Content schemas validated
Implementation Steps
Section titled “Implementation Steps”| Step | Task | MVP | Showcase | Notes |
|---|---|---|---|---|
| 7.01 | Write homepage content | ✅ | ✅ | Focus on clarity |
| 7.02 | Create about content | ✅ | ✅ | Personal or company |
| 7.03 | Write project case studies | ✅ | ✅ | 3-5 detailed examples |
| 7.04 | Create blog posts | ✅ | ✅ | 3-5 starter posts |
| 7.05 | Optimize all images | ✅ | ✅ | AVIF/WebP formats |
| 7.06 | Write meta descriptions | ✅ | ✅ | SEO optimization |
| 7.07 | Create navigation content | ✅ | ✅ | Menu items, footer |
| 7.08 | Add legal pages | ✅ | ✅ | Privacy, terms |
| 7.09 | Create 404 content | ✅ | ✅ | Helpful error page |
| 7.10 | Generate OG images | ✅ | ✅ | Social sharing |
| 7.11 | Write microcopy | ❌ | ✅ | UI text, tooltips |
| 7.12 | Create email templates | ❌ | ✅ | Contact responses |
Content Strategy
Section titled “Content Strategy”1. Voice and Tone Guidelines
Section titled “1. Voice and Tone Guidelines”# Content Style Guide
## Voice Attributes- **Professional** but approachable- **Clear** and concise- **Helpful** and informative- **Confident** without arrogance
## Tone Variations- **Homepage**: Welcoming and inspiring- **About**: Personal and authentic- **Projects**: Professional and results-focused- **Blog**: Educational and conversational- **Error Pages**: Helpful and human
## Writing Principles1. **Lead with benefits**, not features2. **Use active voice** whenever possible3. **Break up long paragraphs** (3-4 sentences max)4. **Include calls-to-action** that guide next steps5. **Write scannable content** with headers and lists2. SEO Content Checklist
Section titled “2. SEO Content Checklist”# SEO Content Checklist
For each page:- [ ] Unique, descriptive title (50-60 characters)- [ ] Meta description (150-160 characters)- [ ] H1 tag with primary keyword- [ ] Semantic heading hierarchy (H2, H3)- [ ] Internal links to related content- [ ] Image alt text describes content- [ ] URL slug matches content focus- [ ] Schema markup where applicable
For blog posts:- [ ] Focus keyword in title, H1, first paragraph- [ ] Related keywords naturally included- [ ] Minimum 300 words (prefer 800+)- [ ] External links to authoritative sources- [ ] Categories and tags assigned- [ ] Author bio includedFuture-Proofing Your Performance
Section titled “Future-Proofing Your Performance”1. Prepare for Mobile-First Indexing
Section titled “1. Prepare for Mobile-First Indexing”- Test on real devices, not just DevTools
- Optimize for 3G connections
- Consider data saver preferences
2. Embrace Progressive Enhancement
Section titled “2. Embrace Progressive Enhancement”- Start with HTML that works
- Layer on CSS enhancements
- Add JavaScript as final enhancement
3. Invest in Infrastructure
Section titled “3. Invest in Infrastructure”- CDN with edge computing capabilities
- Automated performance testing
- Real user monitoring
Key Takeaways for Performance
Section titled “Key Takeaways for Performance”- INP is the new FID - Optimize for entire interactions
- Edge computing is mainstream - Move logic closer to users
- Islands architecture works - Ship less JavaScript
- Performance budgets need context - Tie to business metrics
- Monitoring is non-negotiable - You can’t improve what you don’t measure
What’s Next?
Section titled “What’s Next?”Performance optimization is a journey, not a destination. Here are your next steps:
- Audit your current metrics using Lighthouse
- Implement RUM to understand real user experience
- Set performance budgets based on business goals
- Create a performance culture with automated testing
Remember: The fastest code is no code. Question every kilobyte.
Common Pitfalls
Section titled “Common Pitfalls”-
Keyword Stuffing: Overusing keywords unnaturally
- Solution: Write for humans first, optimize second
-
Missing Alt Text: Images without descriptions
- Solution: Describe image content and function
-
Duplicate Content: Same content on multiple pages
- Solution: Use canonical URLs, write unique content
-
Slow Image Loading: Unoptimized images hurting performance
- Solution: Use responsive images with modern formats
-
Generic Meta Descriptions: Using same description everywhere
- Solution: Write unique descriptions for each page
Exit Criteria
Section titled “Exit Criteria”- [ ] Homepage content written and polished
- [ ] About page content complete
- [ ] 3-5 project case studies written
- [ ] 3-5 blog posts created
- [ ] All images optimized (AVIF/WebP)
- [ ] Meta descriptions for all pages
- [ ] Navigation structure finalized
- [ ] Legal pages created
- [ ] 404 page designed
- [ ] OG images generated
- [ ] Microcopy documented (Showcase)
- [ ] Email templates created (Showcase)
Rollback Strategy
Section titled “Rollback Strategy”If content needs major revision:
-
Content Issues:
- Keep original drafts in version control
- A/B test different versions
- Get feedback before full rollout
-
Image Problems:
- Keep original high-res versions
- Re-run optimization pipeline
- Test on slow connections
-
SEO Impact:
- Monitor search console
- Keep old URLs with redirects
- Update sitemap immediately
AI Assistant Notes
Section titled “AI Assistant Notes”Key Files to Reference
Section titled “Key Files to Reference”src/content/*- All content collectionssrc/assets/images/*- Image assets- Meta description templates
- Content style guide
Common Prompts for This Phase
Section titled “Common Prompts for This Phase”- “Write engaging homepage hero content”
- “Create SEO-optimized meta descriptions”
- “Generate project case study content”
- “Optimize images for web performance”
Context Requirements
Section titled “Context Requirements”- Brand voice and tone
- Target audience
- Key differentiators
- SEO keywords (if any)