Solanasis Docs

03-content-creation-strategy

8 min read

Solanasis — Content Creation Strategy

What this is: The content strategy that governs all blog posts, newsletter content, and thought leadership published on the Solanasis website. Claude (via Code or Cowork) drafts all content; Dmitri reviews and approves before publishing.

Status: Initial version — will be fleshed out as the content engine matures.

Referenced by: 02-claude-build-plan.md (Phase 3.7 — Blog Setup)

Content Mission

Position Solanasis as the trusted operational resilience partner for growing organizations and nonprofits by publishing practical, actionable security and operations content that:

  1. Builds domain authority — targets keywords SMBs and nonprofits actually search for
  2. Demonstrates expertise — shows we understand their pain points without jargon
  3. Earns trust — gives away genuinely useful advice so prospects think “if the free content is this good…”
  4. Generates leads — every post includes a relevant CTA (Call-To-Action) to a service page or contact form

Publishing Workflow

How Content Gets Created and Published

1. PLAN     → Select topic from content calendar (below)
2. DRAFT    → Claude writes the post as a .md file in src/content/blog/
3. REVIEW   → Dmitri reviews the draft (either raw markdown or local preview)
4. REVISE   → Claude incorporates feedback
5. APPROVE  → Dmitri gives the go-ahead
6. PUBLISH  → Claude commits and pushes to GitHub → Cloudflare auto-deploys
7. PROMOTE  → (Future) Share on LinkedIn, send to newsletter subscribers

Publishing Cadence

  • Target: 1 post per week (published on Tuesdays — optimal for B2B engagement)
  • Batch strategy: Claude drafts 4 posts per month in a single session. Dmitri reviews the batch. Posts are committed with sequential future dates so they “go live” automatically each week.

Pro Tip: Astro content collections can be configured to filter by date — posts with a future date won’t appear on the blog listing or sitemap until that date arrives. This gives you a “scheduled publishing” capability with zero infrastructure. Claude Code will set this up during the build.

Content Pillars

All content maps to one of these pillars, which align directly with Solanasis service offerings:

PillarMaps to ServiceTarget Audience Pain Point
Cybersecurity for Non-Technical LeadersSecurity Assessment”I know security matters but I don’t know where to start”
Disaster Recovery & Business ContinuityDisaster Recovery Verification”Would we survive if our systems went down tomorrow?”
Data & SystemsData Migrations, Systems Integration”Our tools don’t talk to each other and data is everywhere”
CRM & OperationsCRM Setup, Systems Integration”We’re outgrowing spreadsheets but don’t know what to adopt”
AI & AutomationResponsible AI Implementation”Everyone’s talking about AI but I don’t know what’s real vs. hype”
Operational Resilience (Umbrella)All services”I need someone to look at everything and tell me what’s broken”

Content Types

1. Educational Posts (Primary — 60% of content)

  • Practical how-to guides and checklists
  • “X Signs You Need…” diagnostic posts
  • “What to Look For When Choosing…” buyer guides
  • Example: “Why Every Growing Organization Needs a Password Manager (And How to Pick One)“

2. Thought Leadership (Secondary — 25% of content)

  • Industry trends and what they mean for SMBs/nonprofits
  • Frameworks and mental models for operational decisions
  • Contrarian takes on common practices
  • Example: “The Biggest Lie in IT: ‘We Back Everything Up‘“

3. Case Study / Story Posts (Tertiary — 15% of content)

  • Anonymized client scenarios (with permission)
  • “What Went Wrong” post-mortems (industry examples, not client-specific)
  • Before/after transformation stories
  • Example: “How a 50-Person Nonprofit Cut Their System Downtime by 90%“

Blog Post Structure

Every blog post follows this template for consistency and SEO:

Frontmatter (YAML in the .md file)

---
title: "Post Title — Clear, Keyword-Rich, Under 60 Characters"
description: "SEO meta description — compelling, under 155 characters, includes primary keyword"
date: 2026-03-11  # Publication date (future dates = scheduled)
author: "Solanasis Team"
tags: ["cybersecurity", "password-managers", "smb-security"]
pillar: "cybersecurity"  # Maps to content pillar above
image: "/images/blog/post-slug-hero.jpg"  # Optional hero image
imageAlt: "Descriptive alt text for accessibility and SEO"
readingTime: 7  # Estimated minutes (Claude calculates this)
draft: false  # Set to true to hide from listing
---

Body Structure

  1. Hook (1-2 paragraphs) — Open with a relatable pain point or surprising stat. Make the reader think “that’s exactly my situation.”

  2. The Problem (2-3 paragraphs) — Expand on why this matters specifically for growing organizations or nonprofits. Acknowledge what makes it hard.

  3. The Solution / Framework (the bulk of the post) — Practical, actionable advice. Use subheadings (H2/H3) to break it into scannable sections. Include specific steps, not vague recommendations.

  4. What Solanasis Does Differently (1-2 paragraphs) — Soft CTA tying back to a relevant service. Not a hard sell — more like “here’s how we approach this for our clients.”

  5. Key Takeaways (3-5 bullet points) — Summary for skimmers.

  6. CTA — Contextual call-to-action: “Want us to assess your [topic]? Contact us” or link to a relevant service page.

Tone and Voice

  • Professional but human — write like a smart friend who happens to be an expert, not a vendor whitepaper
  • No jargon without explanation — if you use a technical term, explain it inline (e.g., “MFA (Multi-Factor Authentication — that second code you get on your phone)”)
  • Confident but not arrogant — “here’s what works” not “you’re doing it wrong”
  • Actionable — every post should leave the reader with something they can do today
  • Honest — if something is complex, say so. Don’t oversimplify to the point of being misleading.

Reference: See also content-style-guide.md (created during the build) for terminology standards, brand language, and writing conventions.

SEO Guidelines

Keyword Strategy

  • Target long-tail keywords that SMBs and nonprofits actually search for
  • Focus on informational intent keywords (“how to…”, “what is…”, “why do I need…“)
  • Include the primary keyword in: title, description, first paragraph, at least one H2, and the URL slug
  • Use related keywords naturally throughout — don’t keyword-stuff

Technical SEO (built into the site)

  • Every post auto-generates: sitemap entry, RSS feed entry, JSON-LD article schema, Open Graph tags
  • URL structure: solanasis.com/blog/[slug] (slug is the filename without .md)
  • Image alt text is required (accessibility + SEO)
  • Internal linking: every post should link to at least one service page and one other blog post

Initial Content Calendar

The first month of content, starting with the launch post. Dates will be set in the post frontmatter during the build.

WeekDateTitlePillarTarget Keyword
1 (Launch)TBDWhy Every Growing Organization Needs a Password ManagerCybersecuritypassword manager for small business
2TBD5 Signs Your Business Needs a Disaster Recovery PlanDisaster Recoverydisaster recovery plan small business
3TBDWhat Happens During a Security Assessment (And Why It’s Not Scary)Cybersecuritysecurity assessment what to expect
4TBDYour CRM Isn’t Working If You’re Still Using SpreadsheetsCRM & Operationswhen to get a crm

These are starting points. The calendar will be expanded and refined as part of the ongoing content strategy. Future topics will be informed by keyword research, client questions, and industry trends.

First Blog Post Brief

”Why Every Growing Organization Needs a Password Manager (And How to Pick One)”

Pillar: Cybersecurity for Non-Technical Leaders

Target audience: Founders, executive directors, and operations leads at SMBs (10-100 employees) and nonprofits who know passwords are a problem but haven’t done anything about it yet.

Primary keyword: password manager for small business

Secondary keywords: business password management, team password sharing, password security for nonprofits

Key points to cover:

  1. The problem is worse than people think

    • The average person reuses passwords across 5+ accounts
    • In a team environment, shared passwords (the WiFi, the social media login, the vendor portal) are usually in a spreadsheet, sticky note, or Slack message
    • A single compromised password can cascade — especially with shared logins
    • Nonprofits are increasingly targeted because they’re perceived as having weaker security

  2. What a password manager actually does

    • Generates strong unique passwords for every account
    • Stores them encrypted — one master password unlocks everything
    • Team sharing: grant/revoke access without revealing the actual password
    • Explain the difference between personal (1Password, Bitwarden) and business tiers (admin controls, audit logs, SSO integration)

  3. How to pick one for your organization

    • Key criteria: team sharing, admin controls, cost per user, ease of onboarding
    • Recommend 2-3 options with honest pros/cons (Bitwarden for budget-conscious, 1Password for ease of use, Keeper for compliance-heavy orgs)
    • Don’t be afraid to name names — readers want specific recommendations, not “consider your options”

  4. The 30-minute setup — make it feel doable

    • Step 1: Pick a manager, sign up for a business trial
    • Step 2: Install the browser extension for yourself
    • Step 3: Import your existing passwords (Chrome/Firefox can export)
    • Step 4: Invite your team and share your first vault
    • Step 5: Start changing your most critical passwords to generated ones

  5. Soft CTA to Solanasis

    • “Password management is one piece of the security puzzle. If you’re wondering what else might be exposed, our Resilience Checkup gives you a full picture in 10 days — and it’s less intimidating than you think. Learn more about our Resilience Checkup”

Estimated length: 1,200-1,500 words (~6-7 minute read)

Internal links:

  • Link to the Resilience Checkup section on home page (/#resilience-checkup)
  • Link to the Contact page

Newsletter CTA at bottom: “Get practical security and operations tips like this every week — no jargon, no fear-mongering.”

Future Enhancements (Not Yet Implemented)

  • Keyword research tooling — use Ahrefs, SEMrush, or free alternatives to validate keyword opportunities
  • Content scoring — develop a rubric for evaluating draft quality before publishing
  • Promotion workflow — LinkedIn posts, newsletter sends, cross-posting strategy
  • Analytics integration — Plausible or Umami to track which posts drive traffic and conversions
  • Guest posts / partnerships — co-authored content with complementary service providers
  • Substack migration — when/if newsletter audience grows, consider moving newsletter content to Substack while keeping blog on the main site (see security playbook for the dual-system architecture)

This document is a living strategy. Update it as the content engine matures and you learn what resonates with your audience.

Graph View

Backlinks