feat(ui): automatically inject objective letter badges

- Add JavaScript to automatically inject letter badges when letter_prefix is present in frontmatter
- Remove manual HTML badge code from all 13 objective pages
- Add letter_prefix field to frontmatter of objective pages
- Update CSS for standalone badge styling with reduced spacing
- Expose letter_prefix metadata to JavaScript via content template
- Add objective-badges.js to mkdocs.yml extra_javascript

This maintains visual consistency while keeping markdown clean and improving SEO by removing letter prefixes from H1 headings.

Author: jgeluk

SITE_REVIEW.md

@@ -0,0 +1,371 @@
+# Site Review & Recommendations for method.ekgf.org
+
+**Review Date:** January 2025  
+**Reviewer:** AI Assistant  
+**Site:** https://method.ekgf.org
+
+## Executive Summary
+
+The Use Case Tree Method documentation site is well-structured with
+good technical foundations. The site uses Material for MkDocs with
+proper SEO infrastructure, responsive design, and excellent diagram
+support. However, there are several areas for improvement,
+particularly around content completeness, SEO optimization, and user
+experience enhancements.
+
+## Overall Assessment
+
+**Strengths:**
+
+- ✅ Excellent technical setup (MkDocs, Material theme, proper SEO
+  infrastructure)
+- ✅ Good navigation structure with awesome-pages plugin
+- ✅ Well-organized content hierarchy (intro → objective → concept →
+  process → vocab)
+- ✅ Good use of audience-specific tabs (Business & Management vs Data
+  & Tech)
+- ✅ Comprehensive FAQ section
+- ✅ Good diagram support (PlantUML, Mermaid)
+- ✅ Proper structured data (JSON-LD) implementation
+
+**Areas for Improvement:**
+
+- ⚠️ Content completeness (6 pages with TODOs)
+- ⚠️ SEO optimization (missing dates on concept pages)
+- ⚠️ Internal linking could be more systematic
+- ⚠️ Some pages lack related content sections
+
+---
+
+## Priority 1: Critical Issues (Fix Immediately)
+
+### 1.1 Complete TODO Content
+
+**Issue:** 6 pages have incomplete content marked with TODOs:
+
+1. **`docs/objective/strategic-usecases.md`** - Only has a TODO
+   comment, no actual content
+2. **`docs/vocab/silo.md`** - Only has a TODO, no content
+3. **`docs/vocab/positive-learning.md`** - Only has a TODO and a link,
+   no content
+4. **`docs/process/build/design.md`** - Summary section has "TODO"
+   instead of actual summary
+5. **`docs/process/run/operate.md`** - "## Audience" section has TODO
+6. **`docs/process/run/optimize.md`** - "## Audience" section has TODO
+
+**Impact:** High - Incomplete content hurts user experience and SEO
+
+**Recommendation:** Complete all TODO sections with proper content.
+For the strategic use cases page, this is particularly important as
+it's a key objective.
+
+---
+
+## Priority 2: SEO Improvements (High Impact)
+
+### 2.1 Add `date_published` to Concept Pages
+
+**Issue:** Concept pages are missing `date_published` fields, which
+Google uses as a freshness signal.
+
+**Files Affected:**
+
+- `docs/concept/use-case.md`
+- `docs/concept/use-case-tree.md`
+- `docs/concept/ontology.md`
+- `docs/concept/data-product.md`
+- `docs/concept/persona.md`
+- `docs/concept/story.md`
+- `docs/concept/outcome.md`
+- `docs/concept/workflow.md`
+- `docs/concept/concept.md`
+- `docs/concept/term.md`
+
+**Recommendation:** Add `date_published: "2022-01-01"` (or actual
+publication date) to frontmatter of all concept pages.
+
+### 2.2 Add Related Content Sections
+
+**Issue:** Not all pages have "Related Content" sections, which
+improves internal linking and helps users discover related
+information.
+
+**Recommendation:** Add a "Related Content" section to all concept and
+objective pages that don't already have one. This should include:
+
+- Related concepts
+- Related objectives
+- Related process steps
+- Related vocabulary terms
+
+**Template:**
+
+```markdown
+## Related Content
+
+- **[Related Concept](link.md)** - Brief explanation of relationship
+- **[Related Objective](link.md)** - Brief explanation of relationship
+- **[Related Process Step](link.md)** - Brief explanation of
+  relationship
+```
+
+### 2.3 Improve Meta Descriptions
+
+**Issue:** Some descriptions could be more compelling and
+action-oriented.
+
+**Recommendation:** Review all descriptions to ensure they:
+
+- Start with action words ("Learn", "Discover", "Get started")
+- Are 150-160 characters
+- Include specific benefits
+- Are compelling enough to click
+
+**Example:** Current: "Enable interoperability across the
+enterprise..." Better: "Learn how to achieve enterprise-wide
+interoperability using the Use Case Tree Method. Practical guide to
+semantic standards and data integration."
+
+---
+
+## Priority 3: Content Quality Enhancements
+
+### 3.1 Complete Summary Sections
+
+**Issue:** `docs/process/build/design.md` has "TODO" in the summary
+section instead of an actual summary.
+
+**Recommendation:** Replace TODO with a proper summary that describes
+what the Design phase accomplishes.
+
+**Suggested Summary:**
+
+```markdown
+<!--summary-start-->
+
+_Design the EKG Platform architecture and use case specifications,
+organizing both technical platform design and business-focused use
+case designs._
+
+<!--summary-end-->
+```
+
+### 3.2 Add "What is..." Sections
+
+**Issue:** Some pages could benefit from clearer introductory "What
+is..." sections for better search intent matching.
+
+**Recommendation:** Ensure all concept pages have clear "What is
+[Concept]?" sections at the beginning, especially for users arriving
+from search engines.
+
+### 3.3 Enhance Process Pages
+
+**Issue:** Some process pages (operate.md, optimize.md) have
+incomplete "Audience" sections.
+
+**Recommendation:** Complete the Audience sections with information
+about who should read these pages and why.
+
+---
+
+## Priority 4: User Experience Improvements
+
+### 4.1 Add Breadcrumb Navigation Context
+
+**Issue:** While Material for MkDocs provides breadcrumbs, some pages
+could benefit from more explicit navigation context.
+
+**Recommendation:** Consider adding "Next Steps" or "Continue Reading"
+sections at the end of key pages to guide users through the
+documentation journey.
+
+### 4.2 Improve Internal Linking
+
+**Issue:** Internal linking exists but could be more systematic.
+
+**Recommendation:**
+
+- Add 3-5 internal links per page
+- Use descriptive anchor text (not "click here")
+- Link from high-traffic pages (homepage, intro) to important content
+- Create a "See Also" section on key pages
+
+### 4.3 Add "Last Updated" Indicators
+
+**Issue:** No visible indication of when content was last updated.
+
+**Recommendation:** Consider adding `date_modified` fields and
+displaying "Last updated" indicators on pages. The
+git-revision-date-localized plugin is already configured, so this
+could be enabled.
+
+---
+
+## Priority 5: Technical Enhancements
+
+### 5.1 Add Missing Schema Types
+
+**Issue:** Some pages may benefit from more specific schema types.
+
+**Recommendation:** Review schema types:
+
+- Process pages should use `"HowTo"` (already done)
+- Concept pages should use `"Article"` (already done)
+- FAQ page uses `"FAQPage"` (good)
+- Consider `"Course"` or `"LearningResource"` for the overall method
+
+### 5.2 Enhance Search Functionality
+
+**Issue:** Search is functional but could be enhanced.
+
+**Recommendation:**
+
+- Ensure all important terms are in content (not just keywords)
+- Consider adding a glossary/index page
+- Add search aliases for common terms
+
+### 5.3 Optimize Images
+
+**Issue:** Some external images are used (Unsplash) which may have
+loading delays.
+
+**Recommendation:** Consider downloading and hosting frequently-used
+images locally for better performance and reliability.
+
+---
+
+## Priority 6: Content Strategy
+
+### 6.1 Add Case Studies or Examples
+
+**Issue:** The method is described but lacks concrete examples or case
+studies.
+
+**Recommendation:** Consider adding:
+
+- Real-world examples of use cases
+- Before/after scenarios
+- Success stories (if available)
+- Common patterns and anti-patterns
+
+### 6.2 Create Getting Started Guide
+
+**Issue:** While there's an intro page, a dedicated "Getting Started"
+guide could help new users.
+
+**Recommendation:** Create a step-by-step "Getting Started" guide that
+walks users through:
+
+1. Understanding the method
+2. Key concepts to learn first
+3. Recommended reading order
+4. Next steps
+
+### 6.3 Add Visual Learning Aids
+
+**Issue:** While diagrams exist, more visual aids could help
+understanding.
+
+**Recommendation:** Consider adding:
+
+- Flowcharts for the process
+- Decision trees
+- Comparison tables (e.g., Use Case Tree Method vs other approaches)
+- Infographics for key concepts
+
+---
+
+## Implementation Roadmap
+
+### Week 1: Critical Fixes
+
+- [ ] Complete TODO content in strategic-usecases.md
+- [ ] Complete TODO content in silo.md
+- [ ] Complete TODO content in positive-learning.md
+- [ ] Fix design.md summary section
+
+### Week 2: SEO Improvements
+
+- [ ] Add date_published to all 10 concept pages
+- [ ] Add related content sections to all concept pages
+- [ ] Add related content sections to remaining objective pages
+- [ ] Review and improve meta descriptions for top 20 pages
+
+### Week 3: Content Quality
+
+- [ ] Complete Audience sections in operate.md and optimize.md
+- [ ] Enhance internal linking throughout site
+- [ ] Add "What is..." sections where missing
+- [ ] Review and improve all summary sections
+
+### Week 4: UX Enhancements
+
+- [ ] Add "Next Steps" sections to key pages
+- [ ] Create getting started guide
+- [ ] Add last updated indicators
+- [ ] Optimize images
+
+### Ongoing: Content Strategy
+
+- [ ] Add case studies/examples
+- [ ] Create visual learning aids
+- [ ] Build backlinks from related sites
+- [ ] Regular content updates
+
+---
+
+## Metrics to Track
+
+After implementing improvements, track:
+
+- **Search Console Metrics:**
+  - Impressions (target: 10x increase in 3 months)
+  - Clicks (target: 5% CTR)
+  - Average position (target: top 20 for key terms)
+- **User Engagement:**
+
+  - Time on page
+  - Bounce rate
+  - Pages per session
+  - Scroll depth
+
+- **Content Quality:**
+  - Pages with incomplete content (target: 0)
+  - Pages with related content sections (target: 100%)
+  - Pages with date_published (target: 100%)
+
+---
+
+## Quick Wins Summary
+
+1. ⏳ **Complete TODOs** - Better user experience (in progress)
+2. ⏳ **Add date_published** - Freshness signal for search (pending)
+3. ⏳ **Add related content** - Better internal linking (pending)
+4. ⏳ **Improve descriptions** - Better click-through rates (pending)
+
+---
+
+## Notes
+
+- The site already has excellent technical foundations
+- SEO infrastructure is solid (sitemap, robots.txt, structured data)
+- The content structure is logical and well-organized
+- Most improvements are content-focused rather than technical
+- The SEO.md file already documents many of these issues - this review
+  provides a comprehensive action plan
+
+---
+
+## Conclusion
+
+The Use Case Tree Method documentation site is well-built with strong
+technical foundations. The main improvements needed are:
+
+1. Content completeness (fix TODOs)
+2. SEO optimization (add dates to concept pages)
+3. Enhanced internal linking and related content sections
+4. Better user guidance (getting started, next steps)
+
+With these improvements, the site should see significant improvements
+in search visibility and user engagement.

docs-overrides/partials/content.html

@@ -40,6 +40,9 @@ <h1>{{ page.title | d(config.site_name, true)}}</h1>
 {% endif %}
 
 <!-- Page content -->
+{% if page.meta.letter_prefix %}
+<script type="application/json" id="page-meta-letter-prefix">{{ page.meta.letter_prefix | tojson }}</script>
+{% endif %}
 {{ page.content }}
 
 <!-- Source file information -->