Editorial policy

Useful PDF guidance starts with claims we can verify.

This policy explains who is responsible for Novus PDF Studio's articles and help content, how product statements are checked, when an updated date is earned, and how to request a correction.

Version 1.0 · Effective August 8, 2026 · Last updated August 8, 2026

Responsible editor

Novus Stream Solutions Editorial Team

The Novus Stream Solutions Editorial Team maintains Novus PDF Studio's product documentation, tutorials and PDF explainers. The team checks product claims against the current browser-local implementation and tests, prefers primary specifications and vendor documentation, and corrects material errors openly. The byline identifies the responsible organization; it does not imply a named expert or professional adviser.

Published by Novus Stream Solutions. For an editorial correction, email pdf@novusstreamsolutions.com. Product support and vulnerability reports use the same address but follow the routes on the contact page.

Review and accountability

Product-technical claims are checked against the current application before publication.

The editorial team verifies workflows against the current code, registries, tests and locally produced output. A feature is not described as available merely because it appears on a roadmap.
Articles explain limitations where they affect a reader's decision, including the distinction between covering content and removing it, electronic and certificate-backed signatures, and selectable text versus tagged PDF structure.
PDF guidance is educational product documentation, not legal, tax, immigration, medical or financial advice. Readers remain responsible for the requirements of the organization receiving a document.

Corrections

Specific correction reports go to the team that can amend the article and its product references.

Report the page URL, the statement at issue and a primary source or reproducible product result when possible. The correction link on every article prepares an email with the article URL.
Material corrections update the article's modified date and are reflected in its metadata, sitemap entry and feeds. Spelling, formatting and link maintenance do not receive a freshness date that suggests the substance changed.
When a correction changes how a shipped feature should be used, the relevant help links and product copy are reviewed with it rather than leaving two competing instructions.

AI assistance

AI may assist drafting or organization, but it is never the accountable author or final reviewer.

The team may use AI tools to organize notes, identify questions to verify or improve a draft's clarity. Every factual and product claim remains subject to human review against primary material and the current application.
No named expert persona is invented for authority. The organizational byline identifies who is responsible for publication and corrections.
Documents opened in Novus PDF Studio are not sent to an editorial or generative-AI service. Browser-local document processing is separate from the editorial workflow used to maintain public pages.

Primary sources

Specifications, standards bodies and first-party technical documentation take priority.

PDF format claims prefer ISO records, implementation documentation and the upstream libraries that perform the work. Accessibility claims prefer W3C/WCAG material and the actual automated checks in this repository.
External sources are linked where they substantively support a claim. Product behaviour is verified in the current application rather than inferred from generic descriptions of a dependency.
Secondary sources may provide context, but they do not replace an available primary source for security, standards, privacy or compatibility claims.

Freshness and revision dates

Dates describe real publication and substantive revision events, not routine rebuilds.

Every article records its publication date. An updated date appears only when the prose or guidance materially changes after publication.
Feature-dependent content is reviewed when the related product behaviour changes. The dated changelog provides the historical product context an older article was written against.
A route's sitemap date is derived from the same revision metadata used by its page and structured data, so a deployment alone does not manufacture a freshness signal.

Topic clusters

Articles are organized into a small set of durable subject areas. Each category points to a cornerstone guide, while focused tutorials answer narrower questions and link back into the same model.

Report a correction

Use the correction link on an article or email the team directly. Include the URL, the exact statement, what you believe is wrong and, when available, a primary source or a reproducible result from the current app.

Email an editorial correction