A change in law
Regulatory wording shifts reach the owner of the affected page, who decides whether the rule changes or only the explanation does.
Arlington, Virginia
Paldorin Digital official policy documentation
This site is where Paldorin Digital keeps its policies, style standards, and compliance guidelines in one place. No login, no sales pitch, no newsletter popup. You land, you find the rule you need, you read it.
Start here if you are new
Most people arrive here for one of two reasons. Either you need to check what a policy actually says before you act on it, or you are writing documentation for us and want the standards we publish under. Both are covered.
If you are not sure where to start, the Policy Handbook is the spine of everything else. The Style Guide governs how we write. Accessibility Standards, Content Governance, and the legal pages fill in the rest.
- Organizational rules and approvals live in the Policy Handbook.
- Wording, dates, and headings are set by the Documentation Style Guide.
- Structure and contrast rules sit in Accessibility Standards.
- Reviews and update triggers are described in Content Governance.
Start with the handbook
The Policy Handbook is the core document. It defines what we mean by a policy (a statement of principles, rules, and directions that guide decision-making), how long one should run, and what has to be in it before it counts as approved.
Individual policies reference it rather than restating its logic, which is why the handbook reads shorter than you would expect. Read it first if you are new; skim the index if you have been here before.
Two questions come up most often. What makes a document official? An owner, a stated review interval, and a recorded approval. What happens when nothing covers a case? You write it down, route it through the handbook's process, and the next reader inherits the answer instead of guessing.
Writing standards live in one place
Our Documentation Style Guide sets the editorial rulebook: plain language, active voice, sentence case headings, serial commas, and a single unambiguous date format. It follows the pattern used by large technical documentation systems, where consistency across thousands of pages is what makes individual pages trustworthy.
If you write for us, the guide is not optional reading. If you only read our policies, it explains why they are phrased the way they are.
Accessibility is a requirement, not a preference
A plain background and legible type are not a design mood here. They are a requirement we can point to, and they set the visual tone for the whole site.
- Contrast
- Text and background keep a high contrast ratio so pages stay readable in bright rooms, on low-quality screens, and at large zoom levels.
- Modular content
- A topic is broken into discrete blocks with its own heading, so a screen reader or a search result can lift one section without dragging the rest along.
- Short pages
- Pages stay short enough to avoid heavy scrolling. If a rule needs more room, it moves to its own page rather than growing a long one.
- Section 508 practice
- Those choices come from the compliance side of the work, and they are the standard we hold drafts to before review.
How documents stay current
Policy that is not maintained is worse than no policy. Content Governance explains who reviews what, how often, and what triggers an update: a change in law, a change in how we operate, or a reader telling us something is unclear.
Every page on this site carries an owner and a review path. If you spot a gap, the Contact page reaches the team that can fix it.
A change in how we operate
When a process is retired or replaced, the page that described it is revised rather than left standing as a stale description.
A reader reports a gap
Questions that arrive through Contact mark the sections that need rewriting, and they set the order of the review queue.
Minimalist by method, not by accident
We display only what the page needs. That is a deliberate usability position, not an aesthetic shorthand: clutter, redundant content, and unnecessary interactions all cost the reader time.
The trade-off is that we cannot hide behind decoration. If a page feels sparse, the reason is that the rule is short and the explanation has to carry its weight. That is the intent.
What we leave out, and why
- No product pages, no pricing, no case studies. This is not a marketing site and does not pretend to be one.
- No client-specific or personnel information. Those records live in controlled systems with their own access rules.
- No duplicated pages. What is here is the public layer of our documentation: the standards we are willing to be held to openly.
A map of the library
The full set of pages is small on purpose. Nothing here duplicates another page, and each one holds a single kind of rule.
Organizational rules
Policy Handbook
What counts as a policy, how long it runs, and what has to be in it before it is approved.
Open the handbook Editorial standardsDocumentation Style Guide
Plain language, active voice, sentence case headings, serial commas, and one clear date format.
Open the guide Section 508 practiceAccessibility Standards
How contrast, modular content, and short pages are built into everything we publish.
Review the standards Update processContent Governance
Who reviews a page, on what interval, and what has to happen before a document changes.
See the review process The teamAbout Us
Who maintains the library and how the documentation work is organized.
Feedback channelContact
Name the page and section, and your report reaches the document owner.
Legal pagesPrivacy, cookies, and terms
How the site itself works, alongside our Terms of Service and Cookie Policy.
Reading order, if you want one
There is no required sequence. But if you are new to the site and want the shortest path to understanding how it is organized, read the handbook's definition of a policy, then the Style Guide's plain-language section, then Accessibility Standards. Together they explain why every page here looks and reads the way it does. Fifteen minutes covers all three.
For external readers
You may be here because a contract, a grant, or an internal process pointed you at one of these pages. Start with the specific document named in your reference. If nothing was named, the Privacy Policy and Terms of Service explain how the site itself works, while the handbook covers organizational rules. You do not need to read the whole library to answer one question.
- Policy pages are written to be cited, not just read top to bottom. Headings are stable, sections are numbered where they need to be, and changes are noted in the governance log rather than quietly edited.
- If you are linking to us from a document of your own, link to the section, not the page, so your reference survives an update.
For internal writers and editors
If you draft policy or documentation for Paldorin Digital, three pages apply to nearly everything you produce: the Style Guide for wording, Accessibility Standards for structure, and Content Governance for review and sign-off. Templates and the formal approval process are described in the handbook.
Following them at draft stage is faster than fixing formatting at review, and it keeps a rule from being restated in a second place where it can drift out of date.
Questions readers ask before they cite us
Do I need an account to read these policies?
No. Every page in the library is public and readable without registration.
How often are these documents updated?
Each page has an assigned reviewer and a review interval set in Content Governance. Updates also trigger on legal changes or reported errors.
Can I quote or cite these policies?
Yes, with attribution to Paldorin Digital and a link to the specific section you are citing. That is why headings are kept stable between revisions.
I found something unclear or out of date. Where do I report it?
Use the Contact page and name the page and section. Reports go to the document owner listed in Content Governance.
Feedback shapes the next revision
We track which pages readers reach from search, which sections get linked externally, and which questions come in through Contact. That is how the review queue gets prioritized. If a page confused you, saying so is useful, not a nuisance. Plain language only works when the people reading it say where it failed.
Paldorin Digital Policy Center, 1201 Wilson Boulevard, Suite 700, Arlington, VA 22209, United States. Open Monday to Friday, 9:00 AM – 6:00 PM Eastern Time. Email [email protected] or call +1 202-432-8110.