Editorial Policy
This page documents how Spec Coding produces, reviews, corrects, and monetizes content. It exists so readers can evaluate the trustworthiness of the information and understand who is responsible for it.
1. Who Is Responsible for This Content
All articles, guides, and templates on Spec Coding are written and maintained by Daniel Marsh, the site's lead author and editor. Daniel has 12 years of experience as a software engineer and tech lead in B2B SaaS environments. Full background is on the author page.
There are no anonymous contributors. If content is ever contributed by a guest author, that author will be named, linked, and their background disclosed on the relevant page.
2. Topic Selection
Topics are selected based on two criteria:
- Practical relevance — the topic must map to a real decision a developer, PM, or QA engineer faces during delivery. Theoretical overviews without actionable guidance are not published.
- Gap in existing coverage — priority is given to topics where existing public resources are abstract, outdated, or missing concrete examples.
Topics are never selected based on advertiser preference, affiliate relationships, or commercial agreements of any kind. Spec Coding does not accept paid content requests.
3. Research and Writing Standards
Every article is drafted from the author's direct engineering experience or from documented industry practice. Before publication, each article is reviewed against the following checklist:
- Is the guidance actionable in a real engineering task without additional interpretation?
- Are examples concrete — named failure modes, specific edge cases, testable acceptance criteria — rather than abstract?
- Does the article avoid filler text, vague hedges, and content that only restates the topic title without adding substance?
- For high-risk topics (billing, migrations, security, concurrency), is failure-path and rollback coverage included?
- Does the article length match the complexity of the topic? Articles are not padded to hit a word count target.
4. Corrections and Updates
Spec Coding treats corrections as a first-class editorial obligation, not an afterthought.
Report — Send a correction through the contact page or by email. Include the specific claim, the article URL, and your suggested correction or source.
Review — The author reviews the reported issue within 5 business days. If additional research is needed, the review may take longer, and the reporter will receive an acknowledgment.
Update — If the report is verified, the article is corrected and the dateModified metadata is updated. Corrections that materially change the article's advice are noted at the top of the relevant section.
Proactive review — Articles covering tools, platforms, or API behaviors are periodically reviewed when the underlying technology publishes significant changes, even without a reader report.
5. Advertising and Commercial Disclosure
Spec Coding may display advertising, including Google AdSense, to support site hosting and content maintenance costs. The following disclosures apply:
- Advertising revenue does not influence which topics are covered, how tools or approaches are evaluated, or which templates are recommended.
- Spec Coding does not sell paid placement within articles, guides, or template recommendations.
- Spec Coding does not participate in affiliate marketing programs. Links to external resources are included on editorial merit only.
- If this policy ever changes — for example, if affiliate links are introduced — the change will be disclosed explicitly on every page where it applies, not just on this policy page.
6. Content Removal
Content is removed or unpublished in the following circumstances:
- The article's core guidance is no longer valid and a correction would require a full rewrite.
- A legal or privacy concern is identified that cannot be resolved by editing.
- The topic is superseded by a more comprehensive guide that makes the original redundant.
Removed pages redirect to the closest relevant current content. Permanent removal without a redirect is avoided to prevent broken links in external citations.
7. Use of AI Tools
Spec Coding uses AI tools as writing aids during content production. Transparency about this is part of the site's editorial standards.
- AI tools may be used for drafting assistance, editing suggestions, and translation between English and Chinese.
- All AI-assisted content undergoes human review and editorial judgment before publication. AI-generated text is not published without substantial human editing and fact-checking.
- Daniel Marsh personally reviews and approves every piece of published content. The author is responsible for the accuracy and quality of the final result, regardless of what tools were used during drafting.
- Translation between English and Chinese uses AI assistance to produce initial drafts. These translations are then reviewed by the author for technical accuracy, natural phrasing, and consistency with the source material.
- AI tools do not influence topic selection, editorial opinions, or recommendations. The author's engineering experience and editorial judgment remain the basis for all published guidance.
8. Linking Policy
External links in Spec Coding articles point to primary sources: official documentation, specification documents, or original research. Links are not added for SEO reciprocity or as part of any link exchange arrangement. All external links use rel="noopener" for security.
9. Contact for Policy Questions
For questions about this editorial policy, requests for corrections, or concerns about a specific article, use the contact page or email guoking678@gmail.com. The author responds to all editorial messages within three business days.