Editorial principles
Useful before optimized
Content is created to help readers learn or prepare, not to manufacture pages for every keyword variation.
Accurate before fast
A clear uncertainty or version limitation is better than an unsupported definitive claim.
Original value
Pages should add explanation, examples, structure, or practical context instead of merely restating another source.
Transparent responsibility
Every published page should identify a named contributor or the collective editorial team responsible for maintaining it.
Editorial workflow
- 1
Define the intent
A page should answer a real learning or interview-preparation need and stay within FrontendPro's technical scope.
- 2
Research the topic
Primary sources such as standards, official documentation, release notes, and reproducible examples are preferred for factual claims.
- 3
Draft for understanding
The direct answer comes first when appropriate, followed by reasoning, examples, limitations, common mistakes, and related concepts.
- 4
Review before publication
Technical accuracy, clarity, source quality, internal links, and any stated version assumptions should be checked before a page is marked as reviewed.
- 5
Maintain and correct
Material errors should be corrected promptly, and content should be revisited when the underlying technology changes significantly.
Sources and technical verification
We prefer specifications, official product documentation, standards bodies, release notes, and maintainers' documentation. Secondary sources can provide context, but they should not replace an available primary source for a technical claim.
Code examples should be internally consistent and tested when a runnable environment is available. Relevant runtime, browser, library, or framework versions should be named when behavior depends on them.
Use of AI and automation
AI tools may assist with research organization, drafting, translation, formatting, or consistency checks. AI assistance does not remove the need to verify technical claims, review examples, disclose uncertainty, and meet the same editorial standard as manually drafted material. Content should not be mass-published solely to capture search traffic.
Corrections and updates
- Material technical errors should be corrected as soon as they are confirmed.
- A page's update date should change only when its content changes meaningfully.
- Outdated guidance should be revised, clearly scoped to an older version, consolidated, or removed.
- Corrections should preserve the original question's intent while making the answer accurate and unambiguous.
Independence and commercial content
Sponsorship, affiliate relationships, paid placement, or other material commercial relationships must be disclosed near the affected content. Commercial considerations must not determine a technical conclusion or be presented as independent editorial judgment.
Policy ownership
This policy is maintained by the FrontendPro Editorial Team. Learn more about the platform on the About FrontendPro page.