Interface and content style

DigitalPlat Domain OSS uses direct, operational language. The interface should read like a maintained infrastructure product, not a marketing demonstration.

Writing rules

• Name the page or task directly: Overview, Add domain, DNS providers.
• Describe observable behavior and limits. Avoid unsupported claims and exaggerated praise.
• Use short sentences and specific nouns. Remove filler, repeated summaries, editorial asides, and formulaic conclusions.
• Do not invent usage statistics, testimonials, activity, or product screenshots.
• Use sentence case for headings and controls. Reserve uppercase for DNS record types and established protocols.
• Put warnings beside the action they affect and state the recovery step.
• Keep terminology consistent with DNS standards and provider documentation.

Visual rules

• Use the product name as a wordmark without a decorative letter logo.
• Prefer standard navigation, tables, forms, status labels, and restrained color.
• Do not use arbitrary symbols as navigation icons.
• Use actual product screenshots with example data when a visual explanation is needed.
• Keep information density appropriate for administration work and preserve mobile access.

Review checklist

Before merging interface text, ask whether it helps a user decide, complete, verify, or recover from an action. If it does none of those, remove it.