Get Page Writing Review > 60 seconds

Executive Summary

The interface copy for Notion's marketing and landing page is generally high-quality, maintaining a professional yet accessible voice. It effectively uses direct address ("you"). However, there are several consistency issues regarding button labeling, capitalization patterns, and link descriptiveness. The most significant improvements can be made by shifting from vague "Try it" calls-to-action to verb-first, specific labels that describe the destination or action.

---

Findings

1. Verb-First Buttons

The page frequently uses generic labels for high-importance primary actions.

Severity	Location	Before	After	Why
MEDIUM	Product Sections	"Try it" (multiple instances)	"Try Notion Docs" / "Start with Wikis"	Core Principle 4: Labels must name the specific action. "Try it" is vague and repetitive.
LOW	Footer/CTA	"Get Notion free"	"Get Notion for free"	Minor polish for natural flow, though the current version is acceptable for brevity.

2. Links Describe Their Destination

Several links rely entirely on surrounding context or visual cues, which fails accessibility standards for screen readers and quick scanning.

Severity	Location	Before	After	Why
HIGH	Use Case Cards	"Triage product feedback→"	"See how to triage product feedback"	Core Principle 6: Links must make sense out of context. The arrow symbol is not a descriptive suffix.
MEDIUM	Hero Section	"Request a demo"	"Contact sales for a demo"	Adds clarity to the outcome of the click.

3. One Capitalization Policy

There is a mixture of Sentence case and Title Case across similar heading levels and UI elements, which creates a sense of "sloppiness."

Severity	Location	Before	After	Why
LOW	Custom Agents Section	"Create your own Custom Agent"	"Create your own custom agent"	Consistency: Most headings use sentence case; "Custom Agent" is treated like a proper noun inconsistently.
LOW	Stats Section	"G2’s #1 knowledge base..."	"G2’s #1 Knowledge Base..."	If using Title Case for stats, apply it to all. Sentence case is the safer default recommended.

4. Plain Words Over Clever Ones

Addressing the reader directly and avoiding ambiguity.

Severity	Location	Before	After	Why
LOW	Hero Section	"Answers questions instantly using knowledge you already have."	"Get answers instantly using your existing knowledge."	Core Principle 3: "You already have" is slightly wordy. More direct phrasing improves scannability.

---

Individual Component Reviews

[Product Feature Grid]

• Current Text: "Try it"
• Proposed Text: "Explore [Feature name]" (e.g., "Explore Projects")
• Severity: Medium
• Rationale: Core Principle 4 & 5. Repeating "Try it" six times on one page leads to "button blindness" and fails to differentiate the varied offerings of the platform.

[Testimonial Section]

• Current Text: "...advantage for us to stay small while doing a lot."
• Proposed Text: No change suggested to quote, but ensure attribution follows sentence case.
• Severity: Low
• Rationale: Quotes are exceptions to voice rules, but the UI surrounding them (titles/labels) should remain consistent with the site-wide policy.

---

Verification and Verdict

Verification Checklist

• Direct Address: Verified use of "you" vs "the user". (Passed: Generally excellent).
• Consistency: Checked "Get Started" vs "Try it" vs "Get Notion free". (Failed: Inconsistent CTA verbs).
• Capitalization: Scanned headings for Sentence case vs Title Case. (Failed: Mixed usage in sub-headings).
• Link Context: Evaluated "Learn more" style links. (Failed: Multi-step links like "Triage product feedback→" need more descriptive text for screen readers).

Verdict

NEEDS CHANGES

Reasoning: While the copy is persuasive, the repetitive use of "Try it" and inconsistent capitalization across product feature headers violate the core principles of Verb-First Buttons and One Capitalization Policy. Addressing the link descriptiveness is also required to meet the HIGH severity accessibility standards defined in the guidelines.

Executive Summary

The Fumadocs landing page features high-quality, developer-centric copy that effectively communicates value. However, the interface text frequently shifts between Sentence case and Title Case, uses passive or ambiguous verbs on primary call-to-action buttons, and relies on bare "Learn More" links. While the voice is modern and engaging, applying stricter consistency to capitalization and button labeling will significantly improve the professional polish of the product.

Findings

1. One Capitalization Policy

The landing page lacks a consistent capitalization strategy, mixing Title Case and sentence case within the same sections and element types.

Severity	Location	Before	After	Why
LOW	Hero Buttons	"Getting Started" beside "Open StackBlitz"	"Get started" and "Open StackBlitz"	Sentence case is the safer default for clarity and localization. Currently inconsistent.
LOW	Features Section	"Syntax highlighting" beside "Codeblock Groups"	"Syntax highlighting" and "Codeblock groups"	Mixing Title and sentence case in a single list reads as sloppiness.
LOW	Headlines	"Docs for Engineers."	"Docs for engineers"	Secondary headings should follow the primary "Build excellent documentation" sentence case style.

4. Verb-First Buttons

Several buttons use vague or non-standard verbs that don't clearly describe the immediate action.

Severity	Location	Before	After	Why
MEDIUM	Story Section	"Explore"	"Explore integrations"	Labels should name the specific action or destination to set expectations.
MEDIUM	CLI Section	"Commands"	"View CLI commands"	A bare noun is less effective than a verb-first action.
MEDIUM	Final CTA	"Read docs"	"Read the documentation"	While brief, "Read docs" feels slightly informal for a primary exit action.

6. Links Describe Their Destination

Multiple links throughout the page use generic phrases that lose meaning when taken out of context.

Severity	Location	Before	After	Why
MEDIUM	Search Section	"Learn More"	"Learn more about search"	Screen-reader users or users scanning the page need context to differentiate links.
MEDIUM	Fumapress Section	"Learn More"	"Learn about Fumapress"	Multiple "Learn More" links on one page create ambiguity.

9. Errors and Status Messages

The CLI/Terminal mockups provided in the content include status messages that could be more direct.

Severity	Location	Before	After	Why
LOW	Terminal Mockup	"New App launched!"	"App launched successfully"	Exclamation marks are unnecessary in routine product feedback.

Verification and Verdict

Verification Checklist

• Voice Check: Confirmed "You" is used where appropriate and "the user" is avoided.
• Device Verbs: Confirmed use of neutral "Open" or "Explore" which works for both click/tap.
• Translation Prep: Identified concatenated-style phrases (none found; mostly static strings).
• Vocabulary Consistency: Checked "Docs" vs "Documentation" usage; found it fluctuates (should be standardized).

Verdict

Needs changes

Rationale: The capitalization inconsistencies (Principle 7) and the repetitive use of "Learn More" (Principle 6) are the primary areas for improvement. While the landing page is aesthetically excellent, the microcopy needs a final polish pass to match that level of quality.

Executive Summary

The landing page for PromptHub features strong, benefit-driven messaging and a clear value proposition. However, the copy is inconsistent in its capitalization policy, occasionally uses passive or "we" phrasing in ways that distance the reader, and includes several placeholder-style strings and generic links that do not clearly describe their destination. The tone is generally appropriate (Professional/Neutral), but structural polish is needed to ensure the interface "disappears" and remains invisible to the user.

---

Findings by Principle

1. One Capitalization Policy

The site oscillates between Title Case and Sentence Case for headings and buttons (e.g., "Level up your prompt management" vs. "Run Prompt"). Sentence case is more scalable for localization and provides a calmer reading experience.

Navigation & Hero Buttons

• Current Text: "Start for free" | "Schedule a demo"
• Proposed Text: "Start for free" | "Schedule a demo" (Note: Keep as is, but ensure all other buttons match).
• Severity: LOW
• Rationale: Establishing a baseline. Some site elements use sentence case correctly while others do not.

API Tabs

• Current Text: "Run Prompt", "Return Prompt", "Return All Prompts"
• Proposed Text: "Run prompt", "Return prompt", "Return all prompts"
• Severity: LOW
• Rationale: Violates the capitalization policy. Mixed casing across buttons ("Start for free" vs "Run Prompt") reads as sloppiness.

---

2. Say "You", Never "The User"

The copy occasionally slips into "we" phrasing or speaks about the platform in a way that creates friction.

Documentation Links

• Current Text: "See how you can automatically evaluate prompts"
• Proposed Text: "Evaluate prompts automatically"
• Severity: LOW
• Rationale: Focus on the action rather than the meta-description of what "you can" do.

API Description

• Current Text: "Retrieve prompts from any branch, inject variables with your app data, and pass along any metadata."
• Proposed Text: "Retrieve prompts from any branch, inject variables with your data, and include metadata."
• Severity: LOW
• Rationale: "Your app data" is redundant; "your data" or just "data" is leaner.

---

3. Plain Words Over Clever Ones

Several areas contain "placeholder" text that was left in the production environment.

Prompt Library (Trending)

• Current Text: "Prompt Generator. 7 prompt framework description placeholder"
• Proposed Text: "A flexible framework for generating complex multi-step prompts." (Or representative description)
• Severity: HIGH
• Rationale: Displaying "placeholder" to a user signals an unfinished product and breaks trust.

---

4. Links Describe Their Destination

Generic "Learn more" style links or links with repetitive lead-ins make navigation difficult for screen readers.

Feature Links

• Current Text: "See how versioning works", "AI tools for prompt engineering", "How to chain prompts"
• Proposed Text: "Read about prompt versioning", "Explore AI prompt tools", "Read the prompt chaining guide"
• Severity: MEDIUM
• Rationale: Links should make sense out of context. "How to chain prompts" is good, but "See how versioning works" is slightly passive. Suffixing them ensures uniqueness.

---

5. Verb-First Buttons

Most buttons are well-actioned, but the ProductHunt banner is a social invitation rather than a clear action.

ProductHunt Banner

• Current Text: "We're live on ProductHunt, come say hi!"
• Proposed Text: "View PromptHub on ProductHunt"
• Severity: LOW
• Rationale: "Come say hi" is slightly colloquial/clever; name the specific destination.

---

Verification Checklist

• Core Principles Check: Verified against all 11 principles including "You" over "User" and Verb-first buttons.
• Capitalization: Checked headings against buttons; found significant inconsistency.
• Variable Interpolation: Checked "Prompt Generator" module; found a "placeholder" string error.
• Device Verbs: Confirmed no pointer-specific ("click") language is used in the main body.
• Empty States: Not applicable (Landing page content present).
• Error Messages: Not applicable (No form errors triggered in the source text).

---

Verdict

VERDICT: Needs changes

Reasoning: While the marketing copy is effective, the presence of the word "placeholder" in the Trending Prompts section is a High Severity finding that must be addressed. Additionally, the inconsistent capitalization across the API documentation tabs and primary buttons needs to be unified to meet a professional standard.

Needs changes