Back to .md Directory

Magic Unicorn Tech Blog Project - Claude Instructions

Defines a content overhaul plan for a tech blog, covering tone, structure, and visual strategy to match a brand voice.

May 2, 2026
0 downloads
2 views
ai claude
View source

What this file does

Defines a content overhaul plan for a tech blog, covering tone, structure, and visual strategy to match a brand voice.

When to use it

  • Planning a blog content refresh with a focus on personality and storytelling
  • Aligning technical blog content with a specific brand voice
  • Restructuring blog series and removing proprietary references
  • Setting up a magazine-style blog layout with hidden content until ready

Assumes this stack

ReactJavaScriptCSS

Magic Unicorn Tech Blog Project - Claude Instructions

šŸŽÆ Project Vision

Transform the current technical blog content into engaging, witty, and entertaining stories that showcase Magic Unicorn's personality while maintaining technical depth.

šŸ“ Current Status: HIDDEN (Under Development)

The blog section is temporarily hidden from the website while we improve the content strategy and tone.

🚨 Content Issues to Fix

1. Remove Non-Open Source Content

  • Meeting-Ops articles - Must be removed (not open source)
  • Review all articles for proprietary technology references
  • Focus only on truly open source tools and approaches

2. Tone & Style Problems

Current Issues:

  • Too technical and dry
  • Lacks personality and humor
  • Doesn't tell engaging stories
  • Missing "irresponsibly cool storytelling" brand voice

Target Tone:

  • Witty and funny
  • Story-driven narratives
  • Technical depth with personality
  • "Hacker culture meets professional insights"
  • Entertaining while educational

3. Visual Strategy

Preferred Approach:

  • Authentic workspace photos (servers, lab setup, behind-the-scenes)
  • Product screenshots and demos
  • Team in action shots
  • Real hardware and development environment
  • Mix with generated graphics for technical diagrams

šŸ“š Content Architecture (Current)

Series Structure:

  1. Unicorn Unleashed (Open Source & Hobbyists) - 6 articles
  2. Forging Silicon (Hardware & Systems) - 6 articles
  3. Engine to Enterprise (Full-Stack Development) - 6 articles
  4. Accelerated Intelligence (AI & ML) - 6 articles
  5. Business of AI (Strategy & Product) - 6 articles

Files to Review/Rewrite:

public/blog/
ā”œā”€ā”€ Open_Source_and_Hobbyists/Unicorn_Unleashed_Guides/
ā”œā”€ā”€ Hardware_and_Systems_Engineers/Forging_the_Silicon/
ā”œā”€ā”€ Full_Stack_and_Product_Developers/From_Engine_to_Enterprise/
ā”œā”€ā”€ AI_and_ML_Engineers/Accelerated_Intelligence/
└── AI_Strategy_and_Product_Management/The_Business_of_AI/

šŸŽØ Design Status: Magazine Layout Complete

  • āœ… Removed hero section
  • āœ… "Latest from the Lab" at top
  • āœ… Magazine-style featured article layout
  • āœ… Responsive design with sidebar
  • āœ… Circuit pattern backgrounds
  • āœ… Improved typography and readability

šŸ”§ Technical Implementation

Blog Service Configuration:

// src/services/blogService.js
// Series definitions with metadata
// Local file fetching from /blog-content
// Article parsing and metadata extraction

Key Components:

  • src/pages/Blog.jsx - Main blog landing (magazine layout)
  • src/pages/BlogSeries.jsx - Series overview pages
  • src/pages/BlogArticle.jsx - Individual article display
  • src/styles/Blog*.css - Magazine-style responsive design

Routing Structure:

/blog - Main blog landing
/blog/series/:seriesId - Series overview
/blog/series/:seriesId/:articleSlug - Individual articles

šŸ“‹ Content Improvement Strategy

Phase 1: Content Audit & Cleanup

  1. Remove Meeting-Ops Content

    • Identify all proprietary references
    • Remove non-open source articles
    • Update series configurations
  2. Rewrite for Personality

    • Add humor and wit
    • Create narrative arcs
    • Include behind-the-scenes stories
    • Technical depth with entertainment value

Phase 2: Visual Enhancement

  1. Authentic Photography

    • Workspace and lab shots
    • Server rack and hardware photos
    • Development environment screenshots
    • Team collaboration moments
  2. Technical Graphics

    • Interactive diagrams
    • Performance charts
    • Architecture visualizations
    • Code examples with syntax highlighting

Phase 3: Interactive Features

  1. Reading Experience

    • Progress indicators
    • Interactive code examples
    • Live demos where possible
    • Series timeline navigation
  2. Performance Metrics

    • Real benchmarks and charts
    • Interactive comparisons
    • Live data where applicable

šŸŽ­ Brand Voice Guidelines

"Irresponsibly Cool Storytelling"

  • Technical Accuracy + Personality
  • Professional Insights + Hacker Culture
  • Educational Content + Entertainment Value

Writing Style:

  • Start with hooks and stories
  • Use analogies and metaphors
  • Include personal anecdotes
  • Technical depth without jargon overload
  • Conversational but authoritative tone

Example Transformation:

Before: "This article explains the implementation of INT8 quantization..." After: "Picture this: You've got a massive neural network that's basically a diva - it wants all the memory, all the compute, and it wants it NOW. But what if I told you there's a way to make that diva perform just as well while using 75% less resources? Welcome to the dark art of INT8 quantization..."

šŸš€ Deployment Strategy

Current State:

  • Blog routes are hidden from navigation
  • Content exists but not publicly linked
  • Magazine layout is ready for content
  • All infrastructure in place

When Ready to Launch:

  1. Update navigation to include blog links
  2. Add blog CTAs to homepage
  3. Enable full blog functionality
  4. Add SEO and social sharing

šŸ“ File Structure Reference

/src
ā”œā”€ā”€ pages/
│   ā”œā”€ā”€ Blog.jsx (magazine layout)
│   ā”œā”€ā”€ BlogSeries.jsx
│   └── BlogArticle.jsx
ā”œā”€ā”€ services/
│   └── blogService.js (content management)
└── styles/
    ā”œā”€ā”€ Blog.css
    ā”œā”€ā”€ BlogSeries.css
    └── BlogArticle.css

/public
└── blog/ (content to be improved)
    └── [series directories...]

šŸŽÆ Success Metrics (Future)

  • Engagement time on articles
  • Social shares and mentions
  • Developer community feedback
  • Technical accuracy + entertainment value balance
  • Brand personality recognition

Next Steps:

  1. Hide blog from public navigation
  2. Content audit and Meeting-Ops removal
  3. Rewrite strategy for personality and wit
  4. Visual content gathering (workspace photos)
  5. Gradual content improvement and testing
  6. Public launch when content meets brand standards

Remember: The technical foundation is solid, the design is magazine-quality, now we just need content that matches the Magic Unicorn personality!

What's inside

6 phases, 5 series, 3 component references, 2 code blocks, and brand voice guidelines

Change this for your project

  • Replace Magic Unicorn with your brand name
  • Replace MagicUnicornInc/magicunicorn.tech with your repository URL
  • Replace Meeting-Ops with your proprietary content to remove

Where it goes

Save in docs/ or the repository root. Gives agents and new contributors a map of the codebase.

Worth borrowing

  • Hide blog routes from navigation until content meets brand standards
  • Use a before/after example to illustrate desired tone shift

Related Documents