fix(marketing): align /features hero count + categories with the data source - #79
Conversation
… source Closes marketing-audit row #6 (HIGH, §3 cross-cutting). Three visible numbers on /features disagreed with the actual data: Hero subtitle: "18 features across compliance, automation, security, and collaboration" (4 cats) Secondary subtitle: "18 platform features across four categories" Page metadata copy: "23 core features across ... 5 categories" Verified against the `features` array in FeaturesPageContent.tsx: **25 entries spread across 5 categories** (Compliance Core 5, Workflow & Operations 6, Identity & Security 4, Collaboration & UX 7, AI & Certification 3). Both the hero "18 features / four categories" and the metadata "23 core features" were stale. Fix: align all three strings to "25 features across five categories" with category labels matching the actual `categories` array. No DOM-arithmetic change required — the per-card counts were already computed via `features.filter(...).length` and were correct; only the prose copy disagreed. Updated text: Hero: "25 features across compliance, workflow, identity, collaboration, and AI" Secondary: "25 platform features across five categories" Metadata: "Explore 25 core features across compliance operations, workflow automation, identity & security, collaboration, and AI & certification." Verified: - tsc --noEmit -p tsconfig.typecheck.json: clean - eslint on both touched files: clean Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9ae6e3c25c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| 25 features across compliance, workflow, identity, collaboration, | ||
| and AI — built for regulated teams that need provable control over |
There was a problem hiding this comment.
When /features renders after this change, the hero and grid intro now say there are 25 features, but the same page still renders platformStats with 23 for “Platform Features” (line 675, shown through StatsSection at line 2052). Users scrolling from the hero into “The platform at a glance” will still see conflicting feature totals, so the visible count remains only partially aligned with the 25-item data source.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Pull request overview
Updates the /features marketing page copy so the displayed feature totals and category count match the actual features data source in FeaturesPageContent.tsx.
Changes:
- Updated OpenGraph/Twitter metadata descriptions from “23 core features” to “25 core features” and refreshed the category list.
- Updated the hero subtitle to reflect “25 features” and five categories (matching the in-file
featuresarray). - Updated the secondary subtitle from “18 … four categories” to “25 … five categories”.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| app/(marketing)/features/page.tsx | Aligns OG/Twitter metadata description counts/categories with the features data source. |
| app/(marketing)/features/FeaturesPageContent.tsx | Aligns on-page hero + secondary subtitle copy with the 25-feature / 5-category dataset. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
♿ Accessibility Test Results✅ PASSED - No critical accessibility issues found Tests Performed:
Artifacts: Download the accessibility reports from the "Artifacts" section for detailed results. |
…ups (#85) Cadence rollup for the Phase C HIGH batch 2 round. No code/runtime changes — audit-doc only. Updates: - Rows #4, #5, #6, #8 (§3 cross-cutting HIGHs): annotate Shipped in #81, #80, #79, #82 with the actual approach taken on each. - Row #16 (MED, JSON-LD personal twitter handle): Shipped in #78. - §20c (industry-page portal opt-out): 5 of 10 missing entries marked Resolved by #83 as intentional design call; the comment block in lib/marketing/background-media.ts is now the source of truth. - §20d (oversized portal JPEGs): record what #84 actually shipped (3 portrait recompresses) and what it didn't (4 landscapes that re-encoded larger). Lesson captured: aspirational ≤180 KB target only applies when the source is over-dimensioned. - New §19a section indexing the batch 2 PR list (#77-#84) and explicitly recording the severity-ordering self-catch where #78 (MED) shipped before §3 HIGHs, with course-correction. Co-authored-by: ejaz <ejaz@local> Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
Summary
Closes marketing-audit row #6 (HIGH, §3 cross-cutting). Three visible numbers on
/featuresdisagreed with the actual data:descriptionVerification
Counted directly against the
featuresarray inFeaturesPageContent.tsx:Both the hero "18 / four categories" and the metadata "23 core features" were stale.
What changed
Prose alignment in
FeaturesPageContent.tsx(hero + secondary subtitle) andpage.tsx(metadatadescriptionfor OG + Twitter). No DOM-arithmetic change required — the per-card category counts were already computed dynamically viafeatures.filter(...).lengthand were correct; only the surrounding copy was off.Test plan
tsc --noEmit -p tsconfig.typecheck.json— clean.eslinton both touched files — clean.🤖 Generated with Claude Code
Co-Authored-By: Claude Opus 4.7 noreply@anthropic.com