Remaining Issues & Action Items
Last updated: 2026-01-28
Critical Issues (Block Launch)
✅ TLS/SSL Certificate RESOLVED
Status: ✅ Complete (Resolved: 2026-01-28)
Solution: Let’s Encrypt certificate successfully provisioned
Final Configuration:
- ✅ Certificate issued by Let’s Encrypt (CN=R13)
- ✅ Covers both medullalabs.io and www.medullalabs.io
- ✅ HTTPS enforcement enabled
- ✅ Certificate expires: 2026-04-28 (auto-renews)
- ✅ Cloudflare DNS in DNS-only mode (grey cloud)
- ✅ Both domains working:
- https://medullalabs.io - HTTP 200 ✅
- https://www.medullalabs.io - HTTP 301 redirect to apex ✅
What Fixed It:
The issue was GitHub’s certificate provisioning getting stuck. The solution was to:
- Remove custom domain completely from GitHub Pages
- Wait 60 seconds for GitHub to clear cached state
- Re-add custom domain
- Wait 3-5 minutes for certificate provisioning
This triggered a fresh certificate request that succeeded.
Key Learnings:
- Cloudflare proxy (orange cloud) prevents GitHub from provisioning certificates
- DNS-only mode (grey cloud) is required for GitHub Pages certificate provisioning
- Certificate provisioning can get stuck and requires domain removal/re-add to reset
- Wait time needed: 60+ seconds between removal and re-adding
High Priority (Should Fix Before Heavy Use)
Status: ✅ Complete (Resolved: 2026-01-28)
Impact: Repository now has proper description and homepage
Configuration:
- ✅ Description: “Medulla Labs - AI Infrastructure & Intelligence Solutions”
- ✅ Homepage: https://medullalabs.io
Status: Placeholder ID in code
Impact: No analytics tracking
What’s needed:
- Create Google Analytics 4 property
- Get Measurement ID (format: G-XXXXXXXXXX)
- Replace placeholder in
_includes/cookie-consent.html:
// Line 75 and 82
gtag('config', 'G-XXXXXXXXXX'); // ← Replace this
Action: See seo-analytics agent documentation for setup steps
Note: Not critical for launch, but important for tracking traffic
Medium Priority (Nice to Have)
✅ Repository Cleanup - RESOLVED
Status: ✅ Complete (Resolved: 2026-01-27 & 2026-01-28)
Completed Actions:
- ✅ Removed
assets/images/team/bob.jpg (placeholder text file)
- ✅ Removed
assets/images/splash.svg (deprecated, replaced by hero-mountains.jpg)
- ✅ Committed
CLOUDFLARE-DNS-CONFIG.md to repository
All cleanup completed in commit 20f4e65.
Low Priority (Future Enhancements)
🔵 Service Icons Could Be More Polished
Status: Functional but basic
Impact: Visual polish
Files:
/assets/images/infrastructure-icon.svg
/assets/images/agentic-icon.svg
/assets/images/analytics-icon.svg
Current: Simple SVG placeholders with blue gradients
Future: Consider professional icon design
Action: Defer to future design iteration
🔵 Logo is Placeholder
Status: Intentional placeholder
Impact: Branding
File: /assets/images/logo.svg
Current: Blue circle with “ML” text
Future: Professional logo design
Note: This was intentionally made a placeholder per your request
Action: Commission professional logo design when ready
Status: Missing
Impact: Browser tab icon uses default
Files needed:
favicon.ico (16x16, 32x32)
favicon.svg (scalable)
apple-touch-icon.png (180x180)
Action: Create favicons from final logo design
🔵 Blog Section Not Implemented
Status: Not started
Impact: None (not in MVP)
Location: _posts/ directory exists but only has welcome post
Action: Defer until content strategy is defined
Resolved Issues ✅
The following were previously issues but are now resolved:
- ✅ Typography system implemented (Tailwind-inspired with Inter font)
- ✅ Mountain image incorporated as hero
- ✅ Logo replaced with placeholder
- ✅ Team page removed
- ✅ Redundant H1 headers removed from all pages
- ✅ Accessibility email changed to support@medullalabs.io
- ✅ Legal pages created (Privacy, Terms, Cookies, Accessibility)
- ✅ Cookie consent banner implemented (GDPR compliant)
- ✅ Navigation updated (team link removed)
- ✅ Footer legal links added
- ✅ Custom CSS typography with proper font sizing
- ✅ Cookie consent uses Inter font (was Open Sans)
- ✅ All agents created and documented
- ✅ CNAME file created for custom domain
- ✅ TLS configuration documented
- ✅ Let’s Encrypt SSL certificate provisioned (2026-01-28)
- ✅ HTTPS enforcement enabled
- ✅ Both medullalabs.io and www.medullalabs.io working with HTTPS
- ✅ GitHub repository metadata configured (description + homepage)
- ✅ Unused files removed (bob.jpg, splash.svg)
- ✅ Cloudflare DNS configuration documentation committed
Testing Checklist
Before considering the site “launch ready”, verify:
Pre-Launch Critical Tests
Content Tests
Mobile Tests
Accessibility Tests
Quick Action Summary
To resolve critical issues right now:
- Verify Cloudflare DNS (5 minutes)
- Check 4 A records point to GitHub Pages IPs
- Check www CNAME points to medullalabs.github.io
- All records should be “DNS only” (grey cloud)
- Wait for SSL certificate (10-60 minutes)
- GitHub automatically provisions Let’s Encrypt cert
- Monitor at: https://github.com/medullalabs/medullalabs.github.io/settings/pages
- Add repository metadata (2 minutes)
gh repo edit medullalabs/medullalabs.github.io \
--description "Medulla Labs - AI Infrastructure & Intelligence Solutions" \
--homepage "https://medullalabs.io"
- Clean up unused files (2 minutes)
git rm assets/images/team/bob.jpg assets/images/splash.svg
git add CLOUDFLARE-DNS-CONFIG.md _includes/cookie-consent.html
git commit -m "Clean up: remove unused assets, add Cloudflare docs, fix cookie banner font"
git push origin main
Total time to “launch ready”: ~1 hour (mostly waiting for SSL)
Non-Blocking Future Work
These can be done after launch:
- Set up Google Analytics (when ready to track)
- Design professional logo (replace placeholder)
- Design service icons (replace simple SVGs)
- Create favicon set
- Add blog posts (if/when content is ready)
- Potentially add team page back (with real team info)
Questions to Consider
Before finalizing launch:
- Google Analytics: Do you want to set this up now or later?
- Repository visibility: Should the repo remain private or be made public?
- Logo: Do you want to commission a professional logo or keep placeholder for now?
- Content review: Have all pages been reviewed for accuracy and tone?
- Email setup: Are all emails (contact@, support@, privacy@, gdpr@, legal@) properly configured to receive?
If issues arise:
GitHub Pages: https://docs.github.com/en/pages
Cloudflare: https://support.cloudflare.com
Let’s Encrypt: https://letsencrypt.org/docs/
Internal Documentation:
- TESTING.md - Full testing procedures
- TLS-CONFIGURATION.md - SSL/TLS setup guide
- CLOUDFLARE-DNS-CONFIG.md - DNS configuration guide
- TYPOGRAPHY.md - Typography system documentation
- .claude/agents/ - Agent documentation for ongoing management