Website TODO List

Project Type: [PERSONAL] Time Allocation: Part of 12 hours/week personal brand work (post-recovery)

This document tracks improvements and enhancements for christaylor.codes. Tasks are organized by priority to help maintain and enhance the website.

Time Allocation

Recovery Window (Nov 12-26, 2025):

Week 1 (Nov 12-18): Blog content creation focus (Blog Posts #2-3) - 28-44 hours
Week 2 (Nov 19-25): Website infrastructure (SEO, accessibility) - 20-30 hours

Post-Recovery (Nov 26+):

Fridays: 8-10 hours (primary deep work block for blog posts and LinkedIn content)
Scattered: 2-4 hours (engagement, small updates, monitoring)
Monthly Total: ~48 hours/month average (12 hours/week)

Milestones

Milestone: 90-Day Post-Launch Review ✅ COMPLETE

Status: Complete Go-Live Date: November 3, 2025 Review Date: February 1, 2026 (90 days post-launch) Type: Major project milestone

Review Objectives:

Analyze website performance and user engagement metrics
- GA4 (G-FMRJQ6FDPJ) and Cloudflare Analytics configured and collecting data
- Lighthouse CI configured with thresholds (Performance 90%, Accessibility 85%, SEO 90%)
- Core Web Vitals optimized (LCP, CLS, FCP commits in Nov 2025)
- Gap: No analytics baseline snapshot document created yet
Content performance assessment
- 14 blog posts published (1 new since launch: “The AI Doom Coefficient”)
- 9 projects showcased with automated weekly stat updates
- Gap: Only 1 new post in 90 days; content heavily ConnectWise-focused (11/14 posts)
- Opportunity: Diversify into MSP operations, AI integration, automation patterns
Technical health check
- Site uptime stable on GitHub Pages + Cloudflare CDN
- html-proofer validates links on every dev push
- Security: GitHub Actions pinned to commit SHAs, Aikido security badge active
- All 3 automated workflows running reliably (deploy, dev-build, project-stats)
- Weekly project stat updates confirmed (8 successful runs since launch)
SEO effectiveness
- Custom meta descriptions on all major pages (index, about, blog, projects, contact, privacy)
- Structured data (Person, Website schemas) implemented
- Sitemap and robots.txt configured
- ~~Gap: Google Search Console setup needs verification~~ (Verified, 21 pages indexed)
- Gap: No backlink strategy execution started
Accessibility review
- ARIA labels present on navigation toggle, search, footer links
- Semantic HTML structure (nav, main, section, article, footer)
- Color contrast meets WCAG AA (primary text #f1f5f9 on #0f172a)
- Lighthouse CI accessibility checks enforced (image-alt, document-title, html-lang, meta-description)
- Gap: No skip-nav link (WCAG 2.1 AA requirement)
- Gap: No screen reader testing conducted
- Gap: Keyboard navigation not fully tested
User feedback collection
- No contact form submissions to review (form replaced with direct contact methods)
- Utterances comment system configured for blog posts
- GitHub project issues monitored via automated workflows
Action items and priorities
- Lessons learned documented below
- TODO reorganized with new sprint structure
- Next 90-day goals defined (content acceleration, accessibility, analytics baseline)

Lessons Learned:

Infrastructure before content was the right call - CI/CD, analytics, and automation are solid
Content velocity is the bottleneck - Only 1 post in 90 days despite having the tooling
Several Sprint 2 items were completed but not tracked - Better task management needed
Privacy/compliance resolved early - Was marked CRITICAL but implemented by Nov 8
Automated workflows are reliable - Weekly stat updates running without intervention

Coordinate with: docs/WEBSITE-MATURITY-FRAMEWORK.md quarterly review (2026-02-07)

Milestone: 180-Day Post-Launch Review 🎯

Status: Scheduled Review Date: May 1, 2026 (180 days post-launch) Type: Major project milestone Focus: Content growth, SEO traction, accessibility compliance Coordinate with: Maturity framework Q2 2026 review (2026-05-07)

Site Maturity Tracking:

docs/WEBSITE-MATURITY-FRAMEWORK.md - Comprehensive maturity assessment and growth roadmap
Review quarterly to track progress across 7 key dimensions
Next review: 2026-02-07

Project Documentation:

CLAUDE.md - Complete project maintenance guide
README.md - Setup and deployment instructions

SEO & Growth:

docs/BACKLINK-STRATEGY.md - Comprehensive backlink building and organic discovery strategy
10 core strategies with implementation roadmap
Metrics tracking and quarterly review process

Sprint Planning

Tasks below have been organized into 9 focused sprints that group similar work and optimize for efficiency. Each sprint is designed to minimize context switching and token usage.

Sprint 1: Performance & Image Optimization ✅ COMPLETE

Priority: HIGH | Token Usage: MEDIUM (~75K tokens) | Completed: 2025-11-04

Foundation sprint establishing performance baselines and asset optimization workflows.

Completed Tasks:

Analyze PageSpeed insights and implement fixes (excluding Cloudflare items)
Create image optimization workflow (WebP conversion process)
Implement lazy loading for images
Optimize Font Awesome usage (documentation created - implementation pending)
Minify CSS for production

Deliverables:

Created optimize-images.ps1 - Automated WebP conversion script
Created docs/IMAGE-OPTIMIZATION-GUIDE.md - Complete image optimization guide
Created docs/FONT-AWESOME-OPTIMIZATION.md - Font Awesome optimization strategy
Created docs/PERFORMANCE-TESTING-GUIDE.md - Testing and validation procedures
Created docs/SPRINT-1-SUMMARY.md - Comprehensive sprint summary
Updated about.html - WebP picture element + lazy loading
Updated index.html - Hero backgrounds with WebP support
Updated assets/js/main.js - WebP detection + lazy loading fallback
Updated _config.yml - Enabled Sass compression

Performance Impact (Projected):

File size reduction: 73% (~2,060 KB savings)
PageSpeed improvement: +20-25 points
LCP improvement: -1.0s to -1.5s

Next Steps:

Generate WebP images (run script or use Squoosh.app)
Create Font Awesome Kit (5-10 minutes)
Test and deploy changes
Measure actual performance improvements

Sprint 2: SEO & Accessibility ✅ PARTIALLY COMPLETE

Priority: HIGH | Project Type: [PERSONAL] Timeline: Nov 2025 - Jan 2026 (completed items spread across multiple sessions) Status: SEO items mostly done; accessibility items carried to Sprint 11

SEO Optimization - Completed:

Add custom meta descriptions to all pages [PERSONAL] [HIGH]
- Homepage, About, Blog, Projects, Contact, Privacy all have custom descriptions
- Terms page uses default (low priority, not typically indexed)
Set up Google Analytics 4 and Cloudflare Web Analytics [PERSONAL] [HIGH]
- GA4: G-FMRJQ6FDPJ (active, with custom event tracking)
- Cloudflare: 6110fc51fbf24e7dbe0fb1b3bb30fedd (active, cookieless)
Set up conversion tracking (blog engagement, GitHub clicks) [PERSONAL] [HIGH]
- GA4 custom events: outbound links, social clicks, form submissions
Review and enhance existing structured data [PERSONAL] [MEDIUM]
- Person schema enhanced (Nov 8, 2025): givenName, familyName, knowsLanguage, credentials, interaction stats

SEO Optimization - Carried to Sprint 11:

Configure Google Search Console and submit sitemap [PERSONAL] [HIGH]
Create analytics baseline dashboard [PERSONAL] [MEDIUM]

Accessibility - Completed:

Add ARIA labels to navigation and interactive elements [PERSONAL] [HIGH]
- Navigation toggle, search icon, search input, footer social links, RSS link
Ensure all images have descriptive alt text [PERSONAL] [HIGH]
- Profile photo, Aikido badge verified; Lighthouse CI enforces image-alt as build error
Test color contrast ratios for WCAG AA compliance [PERSONAL] [MEDIUM]
- Primary text #f1f5f9 on #0f172a passes AAA; secondary text #cbd5e1 passes AA

Accessibility - Carried to Sprint 11:

Add skip navigation link for keyboard users [PERSONAL] [HIGH]
Run WAVE/axe/Lighthouse accessibility audits [PERSONAL] [HIGH]
Fix critical accessibility issues found [PERSONAL] [HIGH]
Test with screen readers [PERSONAL] [MEDIUM]

Priority: MEDIUM | Project Type: [PERSONAL] | Duration: 4-6 hours Timeline: Q1 2026 (Friday workflow)

Tasks:

Implement active navigation state for all pages [PERSONAL] [MEDIUM] (2-3 hours)
Add breadcrumb navigation for better UX [PERSONAL] [MEDIUM] (2-3 hours)

Sprint 4: Advanced Analytics 📅 DEFERRED (Q2 2026)

Priority: LOW | Project Type: [PERSONAL] | Duration: 4-6 hours Timeline: Q2 2026 (after Sprint 2 basic analytics in place)

Context: PSWebsiteHealth module suite in development to automate website monitoring. See c:_Code\CHRIS\projects\pswebsitehealth.md

Tasks:

Add privacy-focused analytics (Plausible or Fathom) [PERSONAL] [LOW] (2-3 hours)
Add performance monitoring (automated via PSLighthouse) [PERSONAL] [LOW] (3-4 hours)
Implement error tracking [PERSONAL] [LOW] (2-3 hours)
Set up automated weekly performance checks [PERSONAL] [LOW] (2-3 hours)
Create monitoring dashboard for maturity framework metrics [PERSONAL] [LOW] (4-6 hours)

Note: Sprint 2 includes basic analytics (GA4/Cloudflare). Sprint 4 is for advanced monitoring tools.

Priority: LOW | Project Type: [PERSONAL] | Duration: 2-3 hours Timeline: Q2 2026

Tasks:

Add professional social media links (Twitter, etc.) [PERSONAL] [LOW] (1-2 hours)
Consider adding Calendly/scheduling link for consultations [PERSONAL] [LOW] (1 hour)

Sprint 6: Advanced Interactive Features 📅 DEFERRED (Q3 2026)

Priority: MEDIUM | Project Type: [PERSONAL] | Duration: 20-30 hours Timeline: Q3 2026 (low priority, nice-to-have features)

Session A - Theme Toggle:

Add dark/light mode toggle (currently dark only) [PERSONAL] [MEDIUM] (8-10 hours)

Session B - Print & Export:

Add print stylesheet [PERSONAL] [LOW] (2-3 hours)
Create PDF export functionality for blog posts [PERSONAL] [LOW] (6-8 hours)

Session C - Gallery:

Add image galleries/lightbox for projects [PERSONAL] [MEDIUM] (6-8 hours)

Sprint 7: Content Types Expansion 📅 DEFERRED (Q4 2026)

Priority: LOW | Project Type: [PERSONAL] | Duration: 38-52 hours Timeline: Q4 2026 (after core brand established)

Tasks:

Create “Case Studies” section for detailed project write-ups [PERSONAL] [LOW] (10-12 hours)
Add “Talks” or “Presentations” section [PERSONAL] [LOW] (4-6 hours)
Add “Tools” or “Resources” page for useful automation tools [PERSONAL] [LOW] (6-8 hours)
Create newsletter signup functionality [PERSONAL] [LOW] (6-8 hours)
Add “Books” section for recommended reading or reading list [PERSONAL] [LOW] (6-8 hours)
- Professional development books, technical references, favorites
- Cover images, ratings, and personal notes/reviews
- Consider integration with Goodreads or similar service
- Group by categories (PowerShell, Automation, Leadership, etc.)
Add “Careers/Jobs” section with Google JobPosting structured data [PERSONAL] [LOW] (8-12 hours)
- Goal: Enable posting job opportunities with proper schema.org/JobPosting markup for Google Jobs integration
- Implementation Tasks:
  - Add _jobs collection to _config.yml (similar to projects collection)
  - Create _layouts/job.html with job detail display and JSON-LD structured data
  - Create jobs.html listing page with filterable job cards
  - Add _sass/oceanic/_jobs.scss for styling (import in oceanic.scss)
  - Create example job posting template in _jobs/ directory
  - Add “Careers” navigation link
  - Document usage in CLAUDE.md
- Required Structured Data Fields:
  - title - Job title
  - description - Full job description (HTML formatted)
  - datePosted - Posting date (ISO 8601 format)
  - validThrough - Application deadline
  - hiringOrganization - Company info (name, logo, URL)
  - jobLocation - Location (address or remote)
  - employmentType - FULL_TIME, PART_TIME, CONTRACTOR, etc.
  - baseSalary - Salary range (optional but recommended)
- Design Decisions Needed:
  - Hiring organization name (i.t.NOW vs. Chris Taylor personal brand)
  - Default job types and locations (remote vs. specific locations)
  - Application process (contact form, email, external ATS)
  - Salary display preferences (show publicly or not)
  - Auto-hide expired jobs (after validThrough date)
- Testing/Validation:
  - Test with Google Rich Results Test tool (https://search.google.com/test/rich-results)
  - Verify JSON-LD validates against schema.org/JobPosting
  - Check mobile responsiveness
  - Test filtering and search functionality
- References:
  - Schema.org: https://schema.org/JobPosting
  - Google Search Central: https://developers.google.com/search/docs/appearance/structured-data/job-posting

Sprint 8: Development Workflow & Testing ⏳ IN PROGRESS

Priority: HIGH → MEDIUM | Project Type: [PERSONAL] | Duration: 12-16 hours Timeline: Phase 1 Complete (Nov 2025), Phase 2 Deferred (Q2-Q3 2026)

Phase 1 - Core CI/CD Pipeline ✅ COMPLETE (Nov 8, 2025)

Create dev branch workflow with automated promotion tooling [PERSONAL] [HIGH] (4-5 hours)
- Created dev branch as primary development environment
- Built comprehensive promotion script (promote-to-main.ps1) with safety checks
- Documented complete workflow in CLAUDE.md
Set up automated testing for HTML validation [PERSONAL] [HIGH] (2-3 hours)
- Implemented html-proofer for link checking and HTML validation
- Validates images, scripts, and internal links on every dev branch push
- Configured to check Images and Scripts only (removed overly strict Favicon check)
Add markdown linting for blog posts [PERSONAL] [HIGH] (1-2 hours)
- Configured markdownlint with sensible rules for technical content
- Ensures consistent formatting across all blog posts
Add Lighthouse CI for performance/accessibility/SEO [PERSONAL] [HIGH] (2-3 hours)
- Automated performance testing on 5 key pages
- Tracks accessibility, SEO, and best practices scores
- Saves results as artifacts for trend analysis
- Adjusted thresholds for practical quality checks (accessibility: 85%, warnings for color-contrast)
- Removed overly strict “lighthouse:recommended” preset (documented restoration in Sprint 10 Phase 3)
Add JavaScript minification to build pipeline [PERSONAL] [HIGH] (2-3 hours)
- Implemented terser-based minification for production deployments
- Conditional loading (main.min.js in production, main.js in development)
- ~40-50% file size reduction for faster page loads
- Added to both deploy.yml and dev-build.yml workflows
- Enhanced build.ps1 with optional local minification support

Phase 2 - Enhanced Quality Checks 📅 PLANNED (Q2 2026) Estimated Duration: 6-8 hours

Session A - Content Quality (3-4 hours):

Add front matter validation for blog posts [PERSONAL] [MEDIUM] (1-2 hours)
- Verify required fields: layout, title, date, excerpt, categories
- Ensure consistent metadata across all posts
- Prevent publishing posts with missing SEO data
Add spell checking for markdown content [PERSONAL] [MEDIUM] (1-2 hours)
- Automated spell checking for blog posts and documentation
- Custom dictionary for technical terms and abbreviations
- Catches typos before publication
Add structured data validation [PERSONAL] [MEDIUM] (1-2 hours)
- Validate JSON-LD schema markup
- Ensure schema.org compliance for rich search results
- Test with Google Rich Results validator

Session B - Code Quality & Security (3-4 hours):

Add SCSS linting (stylelint) [PERSONAL] [MEDIUM] (2-3 hours)
- Enforce consistent SCSS formatting
- Catch CSS syntax errors and best practice violations
- Maintain clean, maintainable stylesheets
Add security scanning for dependencies [PERSONAL] [MEDIUM] (1 hour)
- bundler-audit for Ruby gem vulnerabilities
- Automated alerts for security updates
- Integrate with GitHub security features
Add HTML validation in development [PERSONAL] [LOW] (1-2 hours)
- W3C HTML validator integration
- Catch markup errors during local development

Session C - Git & Tooling (2-3 hours):

Add .gitattributes for consistent line endings [PERSONAL] [LOW] (30 min)
Create git tags for major releases [PERSONAL] [LOW] (1 hour)
Add GitHub issue templates and PR template [PERSONAL] [LOW] (2 hours)
Add npm scripts for common tasks [PERSONAL] [LOW] (1-2 hours)

Benefits of Completed Phase 1:

✅ Safe development environment (dev branch prevents accidental production deployments)
✅ Automated quality checks catch issues before production
✅ Performance/accessibility/SEO monitoring with every build
✅ Professional-grade CI pipeline with comprehensive validation
✅ Lighthouse scores tracked over time for continuous improvement
✅ JavaScript minification reduces payload by 40-50% for faster page loads
✅ Practical quality thresholds balance standards with development velocity
✅ Production-ready build pipeline with automated optimization

Sprint 9: SEO & Link Building 📅 PLANNED (Q1-Q2 2026)

Priority: MEDIUM-HIGH | Project Type: [PERSONAL] | Duration: 12-16 hours total Timeline: Q1-Q2 2026 (after Sprint 2 basic SEO foundation)

Strategy Document: docs/BACKLINK-STRATEGY.md - Comprehensive backlink building strategy

Strategic sprint to build domain authority and organic discovery through natural, high-quality backlinks from relevant sources in the MSP, PowerShell, and IT automation communities.

Target Metrics (6 months):

Total backlinks: 50-100
Referring domains: 30-50 unique domains
Domain Authority: Increase to 25+
Referral traffic: 200-500 visits/month

Month 1-2: Quick Wins (4-6 hours) - Low effort, immediate impact:

Update all GitHub README files with links to tutorials and christaylor.codes [PERSONAL] [HIGH] (2 hours)
Add comprehensive metadata to PowerShell Gallery modules [PERSONAL] [MEDIUM] (1 hour)
Cross-post top 3 blog posts to Dev.to and Hashnode with canonical links [PERSONAL] [MEDIUM] (1-2 hours)
Submit modules to awesome-powershell GitHub list [PERSONAL] [MEDIUM] (30 min)
Create author accounts: Stack Overflow, Reddit, PowerShell.org [PERSONAL] [MEDIUM] (1 hour)
Join and participate in r/PowerShell, r/msp communities [PERSONAL] [MEDIUM] (ongoing)
Answer 5 ConnectWise/PowerShell questions on Stack Overflow [PERSONAL] [MEDIUM] (2 hours)
Reach out to 5 MSP bloggers with “Free tools for your readers” pitch [PERSONAL] [LOW] (1 hour)

Month 3-4: Content Creation (4-6 hours) - Medium effort, high long-term value:

Create “Ultimate Guide to ConnectWise Manage API Automation” (5000+ words) [PERSONAL] [HIGH] (6-8 hours)
Design one infographic: “MSP Automation Maturity Model” [PERSONAL] [MEDIUM] (2-3 hours)
Write guest post for Dev.to or DZone [PERSONAL] [MEDIUM] (4-5 hours)
Create “PowerShell for MSPs” resource list page on site [PERSONAL] [MEDIUM] (2 hours)
Competitor backlink analysis (identify 20 link opportunities) [PERSONAL] [LOW] (2 hours)
Broken link building outreach (10 site owners) [PERSONAL] [LOW] (2 hours)

Month 5-6: Outreach & Scaling (4-6 hours) - Higher effort, compounding returns:

Pitch guest posts to Channel Futures, MSP Alliance [PERSONAL] [MEDIUM] (2-3 hours)
Apply for ConnectWise integration partner listing [PERSONAL] [LOW] (1-2 hours)
Create second linkable asset: “50 MSP Automation Scripts” [PERSONAL] [MEDIUM] (6-8 hours)
Reach out to 10 more MSP bloggers with new resource [PERSONAL] [LOW] (1-2 hours)
Submit tools to 5 additional directories [PERSONAL] [LOW] (1 hour)
Continue Stack Overflow participation (target 20 answers total) [PERSONAL] [LOW] (ongoing)

Ongoing Activities (1-2 hours/week):

Sign up for HARO and respond to 2-3 queries/week [PERSONAL] [LOW] (30 min/week)
Monitor backlinks monthly in Google Search Console [PERSONAL] [MEDIUM] (30 min/month)
Track referral traffic and domain authority growth [PERSONAL] [MEDIUM] (quarterly)

Integration:

Builds on Sprint 2 SEO foundation (meta descriptions, analytics, Search Console)
Supports christaylor-codes-brand.md Phase 5: SEO & Discovery
Aligns with docs/WEBSITE-MATURITY-FRAMEWORK.md SEO dimension (current 30% → target 60%)

Sprint 10: Code Quality Standards Improvement 📅 PLANNED (Q2-Q3 2026)

Priority: LOW | Project Type: [PERSONAL] | Duration: 18-28 hours total Timeline: Q2-Q3 2026 (after higher priority content and SEO work)

This sprint restores stricter quality standards that were temporarily relaxed to get the CI/CD pipeline operational. While the site currently meets minimum quality thresholds, these improvements will bring it up to professional best-practice standards.

Context: During CI/CD implementation (November 2025), we relaxed certain quality standards to accommodate existing content:

Markdown linting: Relaxed 6 cosmetic rules (MD022, MD025, MD031, MD032, MD040, MD049)
Accessibility: Lowered threshold from 90% to 85%, made color-contrast a warning
Lighthouse preset: Removed “lighthouse:recommended” preset to eliminate strict PWA and performance checks
Current state: Site passes all critical checks, but has improvement opportunities

Phase 1: Markdown Quality Restoration (4-6 hours):

Fix markdown linting violations in existing blog posts (98 errors across 15 posts) [PERSONAL] [LOW] (3-4 hours)
- Most common: MD032 (blanks around lists), MD031 (blanks around code), MD040 (code language)
- Use markdownlint _posts/*.md to identify specific issues
- Fix systematically, starting with posts that have most errors
- Update posts in batches to avoid large commits
Re-enable strict markdown rules in .markdownlint.json [PERSONAL] [LOW] (30 min)
- MD022: true (blanks around headings)
- MD025: true (single H1)
- MD031: true (blanks around fences)
- MD032: true (blanks around lists)
- MD040: true (code language specification)
- MD049: { “style”: “underscore” } (consistent emphasis)
Verify all posts pass strict linting [PERSONAL] [LOW] (30 min)
Update CLAUDE.md to reflect restored standards [PERSONAL] [LOW] (30 min)

Phase 2: Accessibility Improvements (4-6 hours):

Fix color contrast issues causing 88% accessibility score [PERSONAL] [LOW] (2-3 hours)
- Identify elements with insufficient contrast (check Lighthouse report)
- Review secondary text color (#cbd5e1) on backgrounds
- Test button text contrast on all color variations
- Verify link colors meet WCAG AA standards (4.5:1 minimum)
- Update CSS variables in _sass/oceanic/_variables.scss as needed
Restore stricter Lighthouse thresholds in .lighthouserc.json [PERSONAL] [LOW] (30 min)
- categories:accessibility: [“error”, {“minScore”: 0.90}]
- color-contrast: “error” (from current “warn”)
Verify all pages pass 90% accessibility threshold [PERSONAL] [LOW] (1-2 hours)
- Run Lighthouse on all 5 key pages
- Address any remaining issues
- Document any intentional exceptions
Update CLAUDE.md and workflow documentation [PERSONAL] [LOW] (30 min)

Phase 3: Lighthouse Recommended Preset Restoration (6-10 hours):

Evaluate and fix Lighthouse recommended preset violations [PERSONAL] [LOW] (4-6 hours)
- Fix link-in-text-block issues (ensure links are visually distinct)
- Fix heading-order problems (ensure logical heading hierarchy)
- Fix label-content-name-mismatch (ensure labels match accessible names)
- Fix identical-links-same-purpose (ensure unique link text or context)
- Review and address performance recommendations:
  - Offscreen images (implement lazy loading if not already done)
  - Render-blocking resources (optimize CSS/JS loading)
  - Unused CSS/JavaScript (consider code splitting)
  - Text compression (verify Cloudflare gzip/brotli is working)
- Evaluate PWA requirements (installable-manifest, themed-omnibox)
  - Decision needed: Does this portfolio site need PWA features?
  - If yes: Add web app manifest and theme colors
  - If no: Document decision to exclude PWA from preset
Re-enable “lighthouse:recommended” preset in .lighthouserc.json [PERSONAL] [LOW] (30 min)
- Add back: “preset”: “lighthouse:recommended”
- May need to add exceptions for PWA requirements if not desired
- Update explicit assertions to complement preset
Verify all pages pass recommended preset checks [PERSONAL] [LOW] (2-3 hours)
- Run Lighthouse CI on all 5 key pages
- Review and address any remaining failures
- Test edge cases (blog posts, project pages)
- Document any intentional exceptions with rationale
Update documentation and CI/CD configuration [PERSONAL] [LOW] (1 hour)
- Update CLAUDE.md with restored preset documentation
- Update dev-build.yml if needed
- Document decision on PWA features

Success Criteria:

All blog posts pass strict markdown linting (0 errors)
All pages achieve 90%+ accessibility score
Color contrast meets WCAG AA standards (4.5:1 for normal text, 3:1 for large)
All pages pass “lighthouse:recommended” preset checks
PWA features evaluated and decision documented
CI/CD enforces strict standards without false positives

Benefits:

Professional quality: Site meets industry best practices for content formatting
Accessibility: Better experience for users with visual impairments
Maintainability: Consistent formatting makes content easier to update
SEO: Search engines favor well-structured, accessible content
Brand reputation: Demonstrates attention to detail and quality

Dependencies:

Sprint 2 (Blog Posts 2-4) should be complete to avoid rework
Can be done incrementally without impacting site functionality
No user-facing changes (improvements are in source quality only)

Related Documentation:

.markdownlint.json - Current relaxed configuration
.lighthouserc.json - Current Lighthouse thresholds
CLAUDE.md - Markdown Standards - Full documentation
CLAUDE.md - Development Workflow - Quality check process

Sprint 11: Accessibility & SEO Foundations ✅ COMPLETE

Priority: HIGH | Project Type: [PERSONAL] | Duration: 8-12 hours total Timeline: February - March 2026 Completed: 2026-02-01 Source: Carried from Sprint 2 incomplete items + 90-day review findings

This sprint addresses the remaining accessibility gaps identified during the 90-day review and completes the SEO foundation needed before backlink work can begin.

Phase 1: Accessibility Compliance (5-7 hours):

Add skip navigation link to _layouts/default.html [PERSONAL] [HIGH] (1 hour)
- Added <a href="#main-content" class="skip-nav">Skip to main content</a> as first focusable element
- Added id="main-content" to main content area
- Styled with visually hidden + focus-visible pattern
Run WAVE accessibility audit on all pages [PERSONAL] [HIGH] (1 hour)
- Tested: home, about, blog, projects, contact
- Found contrast issues, all resolved
Run axe DevTools audit in browser [PERSONAL] [HIGH] (1 hour)
- Cross-referenced with WAVE findings
Fix critical accessibility issues found in audits [PERSONAL] [HIGH] (2-3 hours)
- Fixed contrast issues identified by WAVE
- Improved keyboard navigation for interactive elements
Test keyboard navigation end-to-end [PERSONAL] [MEDIUM] (1 hour)
- Tabbed through every page, all interactive elements reachable
- Enter/Space activation working on buttons and links
- Escape closes mobile menu

Phase 2: SEO Foundation Completion (3-5 hours):

Verify Google Search Console is configured and submit sitemap [PERSONAL] [HIGH] (1-2 hours)
- Verified DNS ownership via Cloudflare
- Sitemap.xml submitted and accepted
- 21 pages indexed, 30 clicks, 5,805 impressions in first 90 days
- Detailed data captured in docs/ANALYTICS-BASELINE-2026-02.md
Create analytics baseline document [PERSONAL] [HIGH] (1-2 hours)
- Google Search Console data exported and documented
- GA4 data exported and documented (Jan 4-31, 2026; low volume due to cookie consent opt-in)
- Cloudflare data exported and documented (100,040 requests across 123 countries)
- Document saved as docs/ANALYTICS-BASELINE-2026-02.md
Set up GA4 conversion goals [PERSONAL] [MEDIUM] (1 hour)
- Event tracking code added for: GitHub clicks, PowerShell Gallery clicks, social media clicks, contact form submissions, contact page visits, blog post reads
- Marked click event as key event in GA4 admin (covers GitHub, Gallery, and social clicks)
- Note: submit event not applicable - contact form replaced with direct contact methods

Success Criteria:

Skip-nav link present and functional on all pages
WAVE audit: 0 errors across all 5 key pages
All interactive elements keyboard-accessible
Google Search Console verified and sitemap submitted
Analytics baseline document completed (GSC + GA4 + Cloudflare)
GA4 events marked as key events in admin interface

Sprint 12: Content Acceleration 📅 PLANNED (Q1-Q2 2026)

Priority: HIGH | Project Type: [PERSONAL] | Duration: 24-32 hours total Timeline: February - April 2026 Source: 90-day review finding: only 1 new post in 90 days

Content velocity is the primary bottleneck. Infrastructure and tooling are solid. This sprint focuses on publishing diverse, high-quality content to build authority and organic traffic.

Phase 1: Content Planning (2-3 hours):

Create Q1-Q2 2026 editorial calendar [PERSONAL] [HIGH] (1 hour)
- Plan 6 posts across content pillars (PowerShell, MSP Operations, AI, Lessons Learned)
- Define publish dates (target: 1 post every 2-3 weeks)
- Balance technical depth with accessibility
Define minimum publishing cadence [PERSONAL] [HIGH] (30 min)
- Commit to 2 posts per month minimum
- Document in CLAUDE.md content strategy section
Create content pipeline in TODO format [PERSONAL] [MEDIUM] (30 min)
- Track: Ideation → Outline → Draft → Review → Publish → Promote

Phase 2: Blog Post Creation (18-24 hours):

Blog Post #15: Diversified topic (non-ConnectWise) [PERSONAL] [HIGH] (4-5 hours)
- Suggested: “PowerShell Automation Patterns for MSP Operations”
- Or: “AI Integration Lessons from Production MSP Environments”
Blog Post #16: Technical tutorial [PERSONAL] [HIGH] (4-5 hours)
- Suggested: “Building Reliable Multi-Tenant Automation with PowerShell”
- Or: “Azure Key Vault for MSPs: Secrets Management at Scale”
Blog Post #17: Experience/lessons learned [PERSONAL] [MEDIUM] (3-4 hours)
- Suggested: “20 Years in IT: What I’d Tell My Younger Self”
- Or: “From Engineer to vCTO: Building an MSP Automation Practice”
Blog Post #18: Tool/project deep dive [PERSONAL] [MEDIUM] (4-5 hours)
- Suggested: “How ConnectWiseAutomateAgent Reached 1.6M Downloads”
- Or: Deep dive into any project with real-world usage data
Blog Post #19: Industry insight [PERSONAL] [LOW] (3-4 hours)
- Suggested: “The State of MSP Automation in 2026”
- Or: “Why Every MSP Should Invest in PowerShell”
Blog Post #20: Community/open source [PERSONAL] [LOW] (3-4 hours)
- Suggested: “Contributing to Open Source as an MSP Professional”
- Or: “Building a PowerShell Module from Scratch”

Phase 3: Content Distribution (4-5 hours):

Cross-post top 2 new blog posts to Dev.to with canonical links [PERSONAL] [MEDIUM] (1-2 hours)
Share each new post on LinkedIn with professional commentary [PERSONAL] [MEDIUM] (1 hour)
Update project READMEs to link relevant blog posts [PERSONAL] [MEDIUM] (1-2 hours)

Success Criteria:

Editorial calendar created with 6 months of planned content
At least 4 new blog posts published (reaching 18+ total)
Content diversity improved (at least 2 non-ConnectWise posts)
At least 2 posts cross-posted to Dev.to
All new posts shared on LinkedIn

Sprint 13: Maturity Framework Quarterly Review ✅ COMPLETE

Priority: MEDIUM | Project Type: [PERSONAL] | Duration: 2-3 hours Timeline: February 7, 2026 (one-time review session) Completed: 2026-02-01

First quarterly maturity review since framework creation (Nov 7, 2025).

Tasks:

Update all 7 category scores in maturity framework [PERSONAL] [HIGH] (1 hour)
- Strategy & Content Planning: 35% (no change)
- Privacy & Compliance: 70% (up from 15%)
- Accessibility: 50% (up from 30%)
- Analytics & Metrics: 50% (reassessed, previously reported as 60%)
- Design System: 65% (up from 55%, reassessed upward)
- Content Governance: 40% (up from 25%)
- Automation & CI/CD: 75% (up from 50%)
Create docs/MATURITY-REVIEW-2026-Q1.md using template [PERSONAL] [HIGH] (1 hour)
- Documented score changes from baseline with evidence
- Identified risks (cookie consent mode, DNT implementation gap)
- Set Q2 2026 priorities (accessibility, content, cookie fix, analytics, SEO)
Update overall maturity score and level [PERSONAL] [MEDIUM] (30 min)
- Previous: 37% (Level 2 Developing)
- Current: 55% (Level 3 Defined)
- Change: +18%
Plan Q2 2026 improvement priorities [PERSONAL] [MEDIUM] (30 min)

Success Criteria:

All 7 categories re-scored with evidence
Quarterly review document created
Next quarter priorities defined
Overall maturity score improved from 37% baseline (now 55%)

Priority 1: Maintenance & Project Management

Content Management

Replace placeholder blog posts with real content about automation, PowerShell, and network operations (Completed 2025-11-04)
Standardize blog post filenames to use simpler titles (e.g., YYYY-MM-DD-title.md instead of YYYY-MM-DD-long-descriptive-title.md)
Rename existing blog posts to follow simplified naming convention
Update project entries in _projects/ with actual projects from your portfolio (Completed 2025-11-04)
Replace placeholder project URLs (#) with real demo and GitHub repository links (Completed 2025-11-04)

Code Organization

Add code comments in main.css to document major sections (Completed 2025-11-04)

Documentation

Update CLAUDE.md with oceanic color palette documentation (Completed 2025-11-04)
Add content contribution guidelines to CLAUDE.md (Completed 2025-11-04)

Priority 2: Features & Functionality

Blog Enhancements

Update the Featured Projects section of the homepage with concise short descriptions (Completed 2025-11-04)
Add reading time estimates to blog posts (Completed 2025-11-04)
Implement pagination for blog posts (Completed 2025-11-04)
Add category/tag filtering functionality on blog index page (Completed 2025-11-04)
Add copy button to code blocks in blog posts (Completed 2025-11-04)
Add search functionality for blog posts (Completed 2025-11-04)
Add “Related Posts” section to blog post layout (Completed 2025-11-04)
Add comments system using utterances for GitHub-based comments (Completed 2025-11-04 - requires utterances app installation, see UTTERANCES-SETUP.md)
Add RSS feed icon/link in navigation or footer (Completed 2025-11-04)

Project Enhancements

Add project detail pages (set output: true in _config.yml for projects collection) (Completed 2025-11-04)
Add “View Project Details” functionality (Completed 2025-11-04)
Create project categories for filtering (Completed 2025-11-04)
Add project screenshots/images functionality (Completed 2025-11-04)
- Created assets/images/projects directory
- Updated project template with image field documentation
- Enhanced project layout to display hero images and screenshot galleries
- Added comprehensive CSS styling with hover effects
- Updated sample projects with placeholder image paths
- Documented image specifications and optimization guidelines in CLAUDE.md Create a process to properly process image files. Conver images to webp format and optimize them with WebP Express.
- Create a process to properly process image

Contact Enhancements

Add LinkedIn profile link (uncomment in _config.yml:10) (Completed 2025-11-04)
Add Professional Resume section to About page (Completed 2025-11-08)
- Added resume download section with call-to-action
- LinkedIn and contact page links
- Placeholder for PDF resume (ready to activate)
- Styled with gradient background and cyan border
- Documented in CLAUDE.md
Add professional social media links (Twitter, etc.)
Consider adding calendly/scheduling link for consultations

Add breadcrumb navigation for better UX
Add “Back to Top” button for long pages (Completed 2025-11-04)
Implement active navigation state for all pages

Priority 3: SEO & Performance

SEO Optimization

Add custom meta descriptions to all pages using front matter (Completed by Feb 2026 - all major pages have custom descriptions)
Add Open Graph tags for better social media sharing (Completed 2025-11-03)
Add Twitter Card meta tags (Completed 2025-11-03)
Add structured data (JSON-LD) for better search results (Completed 2025-11-04 - Enhanced schema for all page types)
Enhance Person structured data for recruiter discovery (Completed 2025-11-08)
- Added givenName/familyName fields
- Added knowsLanguage field
- Added experience years to hasOccupation
- Added support for credentials/certifications
- Added interaction statistics (blog posts, projects)
- Fixed “seeks” field (removed incorrect JobPosting type)
- Documented in CLAUDE.md with testing instructions

Performance

Work to correct pagespeed errors https://pagespeed.web.dev/analysis/https-christaylor-codes/xd0l97cc3z?form_factor=mobile Ignore anything related to cloudflare

Implement image optimization workflow (Completed Sprint 1 - optimize-images.ps1, WebP conversion)
Add lazy loading for images (Completed Sprint 1 - loading=”lazy” on below-fold images)
Minify CSS for production (Completed Sprint 1 - Sass compression enabled)
Consider adding service worker for offline functionality
Optimize Font Awesome usage (documentation created Sprint 1 - implementation pending kit creation)

Accessibility

Add ARIA labels to navigation and interactive elements (Completed - nav toggle, search, footer links)
Ensure all images have descriptive alt text (Completed - Lighthouse CI enforces image-alt)
Test color contrast ratios for WCAG compliance (Completed - primary/secondary text verified AA+)
Add skip navigation link for keyboard users (Carried to Sprint 11)
Test with screen readers (Carried to Sprint 11)

Priority 4: Advanced Features

Analytics & Monitoring

Add Google Analytics or privacy-focused alternative (Completed - GA4 G-FMRJQ6FDPJ + Cloudflare Analytics)
Add performance monitoring
Implement error tracking

Interactive Features

Add dark/light mode toggle (currently dark only)
Add print stylesheet
Create PDF export functionality for blog posts
Add image galleries/lightbox for projects

Content Types

Create “Case Studies” section for detailed project write-ups
Add “Talks” or “Presentations” section
Add “Tools” or “Resources” page for useful automation tools
Create newsletter signup functionality

Priority 5: Development Workflow

Testing

Set up automated testing for HTML validation (Completed Sprint 8 - html-proofer in dev-build.yml)
Add link checker to prevent broken links (Completed Sprint 8 - html-proofer checks internal links)
Create CI/CD pipeline for automated deployments (Completed Sprint 8 - deploy.yml + dev-build.yml + promote-to-main.ps1)
Add accessibility testing in build process (Completed Sprint 8 - Lighthouse CI checks accessibility on 5 pages)

Version Control

Add .gitattributes for consistent line endings
Create git tags for major releases
Add GitHub issue templates
Add pull request template

Development

Set up local development environment documentation
Add npm scripts for common tasks
Consider adding Webpack/Gulp for asset pipeline
Add CSS linting (stylelint)
Add HTML validation in development

Quick Wins (Easy, High Impact)

These tasks can be completed quickly and provide immediate value:

Add LinkedIn profile link to config and footer (Completed 2025-11-04)
Create first real blog post about PowerShell automation (Completed 2025-11-04 - Added 4-post series on ConnectWiseAutomateAgent)
Add at least one real project from your portfolio (Completed 2025-11-04)
Add Open Graph and Twitter Card meta tags for better social sharing (Completed 2025-11-03)
Add structured data (JSON-LD) for improved search results (Completed 2025-11-04 - See STRUCTURED-DATA-SUMMARY.md)

Notes

Test all changes locally before pushing to GitHub Pages
Maintain responsive design for all new features
Current color theme: Oceanic palette (dark cyan, midnight green, tiffany blue with warm accents)
Blog post naming: Use simplified titles with required date prefix (e.g., YYYY-MM-DD-title.md)
Prioritize page load performance
Ensure all new content aligns with Chris Taylor’s professional brand

Completed Tasks

Initial Setup (2024)

November 2025 Updates

Performance Optimizations (November 2025)

Fix render blocking requests - Font Awesome async loading (commit: 2113c91)
Fix render blocking requests - main.js defer attribute (commit: 2113c91)
Add font-display: swap for faster text rendering (commit: 2113c91)
Add preconnect hints for CDN resources (commit: 2113c91)
Add JavaScript minification to build pipeline (commit: 49a283a)
- Terser-based minification for production
- 40-50% file size reduction
- Conditional loading (main.min.js vs main.js)
- Integrated into GitHub Actions workflows

CI/CD & Quality Improvements (November 2025)

Implement dev branch workflow with automated promotion (commits: multiple)
- Created promote-to-main.ps1 script with comprehensive safety checks
- Documented complete development workflow in CLAUDE.md
Add markdown linting to CI/CD pipeline (commit: multiple)
- Configured markdownlint with practical rules for technical content
- Relaxed 6 cosmetic rules for existing content compatibility
Add HTML validation with html-proofer (commits: 9d4d275)
- Validates images, scripts, and internal links
- Removed overly strict Favicon check (false positive on GitHub Pages)
Add Lighthouse CI for automated quality testing (commits: b0c7e7a, b88cf95)
- Tests performance, accessibility, SEO, best practices
- Adjusted thresholds to 85% for practical development workflow
- Removed “lighthouse:recommended” preset (restoration planned in Sprint 10 Phase 3)
- Color-contrast changed from error to warning
- Disabled bf-cache check (not critical for static site)
Fix Lighthouse mixed content warning (commit: 34838d9)
- Disabled cookie consent geolocation feature (was causing HTTP request to ipinfo.io)
- Removed ipinfo.io from CSP policy
- Universal consent approach (simpler, still GDPR/CCPA compliant)

Content Organization (November 2025)

Standardize blog post filenames to simpler naming convention (commit: 2667c27)
Rename existing blog posts to follow simplified format (commit: 2667c27)
Update CLAUDE.md and templates with simplified naming documentation (commit: 2667c27)
Update project entries in _projects/ with actual projects from portfolio (2025-11-04)
Replace placeholder project URLs with real GitHub repository links (2025-11-04)
Add LinkedIn profile link to config and footer (2025-11-04)
Add comprehensive code comments to main.css documenting all major sections (2025-11-04)

Documentation (November 2025)

Update CLAUDE.md with oceanic color palette documentation (2025-11-04)
Add comprehensive content contribution guidelines to CLAUDE.md (2025-11-04)

Homepage Enhancements (November 2025)

Add short_description field to all project files for concise homepage summaries (2025-11-04)
Update index.html Featured Projects section to use short_description (2025-11-04)
Update project-template.md with dual description field guidance (2025-11-04)

Website TODO List

Time Allocation

Milestones

Milestone: 90-Day Post-Launch Review ✅ COMPLETE

Milestone: 180-Day Post-Launch Review 🎯

Related Documentation

Sprint Planning

Sprint 1: Performance & Image Optimization ✅ COMPLETE

Sprint 2: SEO & Accessibility ✅ PARTIALLY COMPLETE

Sprint 3: Navigation & UX Enhancements 📅 DEFERRED (Q1 2026)

Sprint 4: Advanced Analytics 📅 DEFERRED (Q2 2026)

Sprint 5: Contact & Social Enhancements 📅 DEFERRED (Q2 2026)

Sprint 6: Advanced Interactive Features 📅 DEFERRED (Q3 2026)

Sprint 7: Content Types Expansion 📅 DEFERRED (Q4 2026)

Sprint 8: Development Workflow & Testing ⏳ IN PROGRESS

Sprint 9: SEO & Link Building 📅 PLANNED (Q1-Q2 2026)

Sprint 10: Code Quality Standards Improvement 📅 PLANNED (Q2-Q3 2026)

Sprint 11: Accessibility & SEO Foundations ✅ COMPLETE

Sprint 12: Content Acceleration 📅 PLANNED (Q1-Q2 2026)

Sprint 13: Maturity Framework Quarterly Review ✅ COMPLETE

Priority 1: Maintenance & Project Management

Content Management

Code Organization

Documentation

Priority 2: Features & Functionality

Blog Enhancements

Project Enhancements

Contact Enhancements

Navigation

Priority 3: SEO & Performance

SEO Optimization

Performance

Accessibility

Priority 4: Advanced Features

Analytics & Monitoring

Interactive Features

Content Types

Priority 5: Development Workflow

Testing

Version Control

Development

Quick Wins (Easy, High Impact)

Notes

Completed Tasks

Initial Setup (2024)

November 2025 Updates

Performance Optimizations (November 2025)

CI/CD & Quality Improvements (November 2025)

Content Organization (November 2025)

Documentation (November 2025)

Homepage Enhancements (November 2025)

Blog Content (November 2025)