Editorial Guidelines
These guidelines define Sitka Theme's content standards, submission requirements, and link policy. Every article — whether staff-written or guest-contributed — must meet these standards before publication.
Content Requirements
- Word count: 1,500–3,500 words. Shorter pieces lack depth; longer pieces should be split into a series.
- Originality: 100% original content. We run every submission through plagiarism detection tools. Previously published articles (including on your own blog) are not accepted.
- Technical depth: Articles should go beyond surface-level overviews. Include code examples, benchmarks, architecture diagrams, or real-world implementation details.
- Tested code: All code examples must work. Include the runtime version, framework version, and any dependencies needed to reproduce results.
- Recency: Content must reflect current best practices. References to deprecated APIs, outdated patterns, or EOL software will be flagged during review.
Accepted Topics
We publish articles in these areas:
- Frontend frameworks and libraries (React, Vue, Svelte, Angular, Solid)
- Backend development (Node.js, Python, Go, Rust, Java, .NET)
- DevOps and CI/CD (GitHub Actions, GitLab CI, Jenkins, Terraform)
- Container orchestration (Docker, Kubernetes, Nomad)
- SaaS product engineering (billing, multi-tenancy, feature flags)
- Database design and scaling (PostgreSQL, MySQL, MongoDB, Redis)
- API design patterns (REST, GraphQL, gRPC, event-driven)
- Cloud infrastructure (AWS, GCP, Azure, serverless)
- Software architecture (microservices, monoliths, domain-driven design)
- Testing strategies (unit, integration, E2E, performance)
Link Policy
One contextual dofollow link per article. The link must point to a relevant resource that adds value for the reader. It must appear naturally within the article text, not in the author bio or as a standalone call-to-action.
Links we accept:
- Links to technical documentation, tools, or open-source projects directly relevant to the article topic
- Links to the author's published technical work (GitHub repos, conference talks, technical blog posts)
- Links to verifiable data sources, benchmarks, or research papers
Links we reject:
- Links to commercial landing pages, pricing pages, or product signup pages
- Links with exact-match anchor text optimized for SEO keywords
- Links to content farms, low-quality directories, or unrelated sites
- Affiliate links, tracking URLs, or URL shorteners
- Multiple links to the same domain
Prohibited Content
- AI-generated content that has not been substantially rewritten and verified by the author
- Thinly veiled product promotions or advertorials
- Content that duplicates existing articles on Sitka Theme
- Articles without working code examples (when the topic involves code)
- Content promoting illegal activities, security exploits without responsible disclosure, or black-hat SEO practices
Formatting Standards
Articles are published as server-rendered HTML. The following elements are permitted:
- Headings (
h2,h3,h4), paragraphs, lists - Code blocks (
pre/code) with syntax context - Tables for comparison data
- Blockquotes for callouts or important notes
- Images with descriptive alt text
- One anchor link with appropriate attributes
No JavaScript is permitted in article content. Articles are rendered as pure HTML and CSS for performance and security.
Review Process
- Submission: Author submits article with author bio, credentials, and proposed link.
- Technical review: An editor with domain expertise reviews for accuracy, depth, and code correctness.
- Originality check: Content is checked against plagiarism tools and existing Sitka Theme articles.
- Link review: The proposed link is evaluated for relevance, quality, and compliance with our link policy.
- Publication: Approved articles are formatted, schema markup is added, and the article is published with the author's byline.
Average review time is 3–5 business days. We may request revisions before approval.
Author Attribution
All published articles include the author's name and a brief bio. We encourage authors to provide:
- Current role and company (or "independent engineer")
- Relevant credentials or years of experience
- LinkedIn profile or personal website
Author bios appear at the end of each article and are included in the Article schema markup for search engines.