RightWay website plan

1. Sitemap

Route	Purpose
/	Introduce RightWay and direct founders to create a profile
/about	Explain the mission and team; add approved founder details when supplied
/services	Overview of profile, feedback, investor context, and profile management services
/services/[service]	Explain the problem, process, deliverables, pricing guidance, and next step
/features	Product capability overview
/pricing	Compare the Free and Pro plans before signup
/case-studies	Publish only customer stories with explicit approval
/faq	Resolve product, pricing, review, and process objections
/blog	Publish Markdown articles for founders
/blog/[slug]	Individual article with date, category, and related reading
/newsletter	Explain the email updates and collect subscriptions through Brevo
/contact	Let visitors choose a contact topic and email the team
/docs/	Docusaurus help center, built into the Next.js deployment
/privacy, /terms	Legal information

2. Page-by-page content and layout

Home — /

• Purpose / action: Explain the shareable business-profile value proposition; primary action is Create your business profile.
• Top to bottom: Responsive grouped header menu; wide locally generated illustration hero with introductory content; four service cards; business-profile story; profile preview; three-step profile checklist with a distinct illustration; resource and Docs links; image-backed feature band; FAQ preview; signup CTA; footer.
• Copy: H1 “Make your next move count.” Subhead: “Give your business a clear, shareable home. Bring your profile, customer feedback, and the details people need together in one place.” Primary CTA “Create your business profile”; secondary “Explore services.” Microcopy: “Choose what you want to share.”
• Proof / media: Use original local illustrations that are distinct from other page and section artwork. Do not show screenshots that could imply actual users, ratings, metrics, or customer results. Do not show unverified counts, reviews, customer logos, testimonials, or app store badges.
• Links: Services, features, pricing, case studies, blog, FAQ, contact, docs.
• SEO: Title “A clear, shareable business profile | RightWay”; description “Bring your business story, important details, links, and customer feedback together in one shareable profile.” Intent: business profile and customer feedback tools.
• Responsive: Desktop side-by-side hero and four-card row; tablet stacked hero with two-column cards; mobile single-column hero/cards, accessible expandable navigation, and full-width primary CTA.

About — /about

• Purpose / action: Explain the mission and earn trust; action is to explore services or contact the team.
• Top to bottom: Mission hero; product-purpose section with its own illustration; publishing principles; shareable-profile section with a separate illustration; services CTA.
• Copy: H1 “We believe good businesses deserve to be found.” The page explains the product purpose and clearly states that founder/team biographies will be added once verified details are approved. Do not infer names, locations, credentials, or a founding date.
• Proof / media: Use locally generated illustrations that are unique to each section. Add founder story, team portraits, and credentials only after approval; never imply illustrations depict RightWay staff or customers.
• Links: Services, case studies, contact, blog.
• SEO: Title “About RightWay | Business profiles and discovery”; concise mission description; H1 above; H2s “Why RightWay exists,” “What we believe,” “Meet the team” (only with verified bios). Intent: branded company research.
• Responsive: Desktop story/image split; tablet equal split; mobile image after story copy and stacked principles.

Services and product features — /services, /services/[service], /features

• Purpose / action: Match a visitor need to a clear product workflow; action is to create a profile or view pricing.
• Overview layout: Hero; four service cards; illustrative workplace section; three-step process; current-pricing guidance; FAQ; CTA.
• Service pages: Numbered hero; challenge statement; three-step process; deliverables checklist; Free and Pro pricing guidance; service icon; next-step CTA and contact CTA.
• Services: Feedback and reviews; individual business profile; a clearer investor-facing company profile; complete profile management. Explain investor use as a shareable information page, not a funding or outcome guarantee.
• Copy: Overview H1 “A clearer way to show what your business does.” CTA “Find the right starting point.” Service CTA “Create your profile.” Avoid guarantees of traffic, rank, trust, investment, or sales.
• Proof / media: Neutral profile and feedback illustrations are explicitly labeled illustrative. No fabricated product results, screenshots, or customer quotes.
• Links: Pricing, features, docs, FAQ, contact, signup.
• SEO: One unique title, meta description, and H1 per service. H2 pattern: “The challenge,” “How it works,” “What you can do,” “Pricing guidance,” “Your next step.” Intent: business-profile management, customer feedback, investor company information.
• Responsive: Desktop alternating text/image and 3–4 service cards; tablet two cards per row; mobile stacked steps/cards and persistent, keyboard-visible CTA.

Individual service pages

All detail pages share a service-number hero, challenge statement, three process steps, deliverables checklist, Free and Pro pricing guidance, and next-step CTA. Pro is priced at $20 and includes advanced dashboard features for managing business data; billing interval is confirmed in signup. Service icons and neutral illustrations support the text but are not presented as real product screenshots. Desktop uses two-column challenge/pricing layouts and horizontal process cards; tablet wraps cards; mobile stacks sections and makes CTAs full-width.

Route and purpose	Copy, process, deliverables, and next step	SEO intent and internal links
/services/feedback-reviews — invite and manage customer feedback	H1 “Feedback & reviews.” Explain that customer feedback can be difficult to understand when spread across channels. Steps: share a profile link, invite honest feedback, respond respectfully. Deliverables: public feedback, a shareable invitation link, feedback response tools. Next: create a profile and invite customers neutrally.	Customer feedback and business reviews. Link to /ratings, /docs/manage-feedback, /faq, and /contact.
/services/business-profile — present business details together	H1 “Individual business profile.” Explain how a clear profile can bring an introduction, category, key details, contact links, and optional images together. Steps: choose a profile name/category, add approved business details, publish and share. Next: set up a profile.	Shareable business profile. Link to /features#profiles, /docs/create-profile, and /pricing.
/services/investor-trust — prepare a convenient investor-facing introduction	H1 “A clearer picture for investors.” Explain the profile as a place to review approved company information, without promising investor interest or funding. Steps: build a profile, add approved milestones/team details, share it in investor introductions. Next: create a profile for sharing with a network.	Investor-facing company profile. Link to /features#experience, /docs/share-profile, and /contact.
/services/profile-management — keep public business details current	H1 “Complete profile management.” Explain why accurate business information and consistent links matter. Steps: update details, maintain images and contact links, review feedback and profile accuracy. Next: compare Free and Pro.	Business profile management. Link to /features, /docs/create-profile, /pricing, and /contact.

Pricing — /pricing

• Purpose / action: Direct visitors to the live plan details; action is to review current options in the RightWay signup flow.
• Top to bottom: Pricing hero; Free and Pro plan cards; decision checklist; pricing FAQs; support contact; CTA.
• Copy: H1 “Start free. Upgrade when you need more.” Free is $0. Pro is $20 and includes advanced dashboard features for managing business data. Ask visitors to confirm billing terms in signup before subscribing.
• Proof / media: Display only the provided plan names, prices, and Pro dashboard capability. Do not imply a billing interval unless confirmed in signup.
• Links: Service details, FAQ, contact, signup.
• SEO: Title “Plans and pricing | RightWay”; description “Compare RightWay's Free and Pro plans. Pro costs $20 and includes advanced dashboard features for managing business data.” Intent: RightWay pricing.
• Responsive: Two plan cards on desktop, stacked cards on small screens, with full-width CTAs on mobile.

Case studies — /case-studies

• Purpose / action: Provide evidence from customer-approved work; action is to read a story or contact RightWay.
• Top to bottom: Evidence-led hero; transparent empty state until approved stories are available; explanation of publishing standards with a distinct local illustration; CTA.
• Copy: Until an approved story is available, use the honest empty state: “Customer stories will appear here when they’re approved for publication.” CTA “Talk to our team.” Do not manufacture company names, quotes, outcomes, or logos.
• Proof / media: Each future story requires written permission, a named source, and substantiation for every outcome claim.
• Links: Services, pricing, contact, relevant blog articles.
• SEO: Title “Customer stories | RightWay”; meta description must describe only published stories; H1 “Customer stories”; H2 per approved story. Intent: evaluate platform evidence.
• Responsive: Desktop editorial card grid; tablet two columns; mobile one column with quote and image content stacked.

FAQ — /faq

• Purpose / action: Resolve concerns before signup; action is to create a profile or request help.
• Top to bottom: Question-focused hero; grouped native disclosure list; support panel; signup CTA.
• Copy: H1 “Questions, meet answers.” Categories cover profiles, feedback moderation, sharing, pricing, privacy, and getting support. Answers must match actual product behavior and current terms. CTA “Ask our team.”
• Proof / media: Native <details> disclosures; optional FAQ structured data only for visible, accurate answers.
• Links: Docs, pricing, services, privacy, contact, signup.
• SEO: Title “RightWay FAQ | Profiles, feedback, and pricing”; description lists the topics answered; H1 above; H2 for FAQ groups. Intent: product questions and objections.
• Responsive: Desktop FAQ with sticky support sidebar; tablet non-sticky sidebar; mobile single column with large disclosure hit areas.

Blog — /blog, /blog/[slug]

• Purpose / action: Publish useful, maintainable founder guidance; action is to explore a topic or create a profile.
• Top to bottom: Blog hero; Markdown article cards with a unique illustration, category, publication date, and estimated reading time; individual article with title, description, date, body, author, and CTA.
• Copy: H1 “Useful ideas for your next step.” Articles use descriptive titles and practical guidance. The author field is editorial attribution, not a customer testimonial or credential.
• Proof / media: Markdown source with YAML frontmatter; generated HTML is sanitized. Do not publish unsupported performance claims or imply authorship that has not been approved.
• Links: Related articles, service pages, docs, FAQ, pricing.
• SEO: Unique title/description; one H1 per page; logical H2/H3; Article structured data generated from frontmatter. Intent varies by article keyword.
• Responsive: Desktop three-column article grid with distinct artwork for every article; tablet two columns; mobile stacked cards and a readable long-form line length.

Newsletter — /newsletter

• Purpose / action: Describe the occasional RightWay email newsletter and collect a visitor's email with explicit consent through the supplied Brevo form.
• Top to bottom: Newsletter hero; benefits and subscription form; editorial section with distinct artwork; blog CTA.
• Copy: H1 “A little more clarity in your inbox.” Updates cover business profile writing, customer feedback, and RightWay resources. Consent says subscribers can unsubscribe at any time; it does not promise a specific send schedule.
• Privacy and proof: The form submits to the provided Brevo subscription endpoint, uses Cloudflare Turnstile and a honeypot field, and requires an opt-in checkbox. Privacy Policy is linked beside consent. Do not imply this site stores subscriber details itself.
• Links: Footer and Blog index/article pages link to this page; the subscription page links to Blog and Privacy.
• SEO: Title “Business profile newsletter | RightWay”; describe practical topics without promising business results. Intent: subscribe to business profile and customer feedback guidance.
• Responsive: Desktop two-column copy and form; tablet stacked sections; mobile single-column form with a full-width submit button.

Contact — /contact

• Purpose / action: Route support, press, and partnership inquiries; action is to write to the relevant mailbox.
• Top to bottom: Contact hero; topic cards; accessible form; published email and FAQ/doc links.
• Copy: H1 “How can we help?” Form fields: name, email, business/organization (optional), topic, message, and acknowledgement. Button “Open email app to send.” State clearly that submission opens the visitor’s mail app; it is not an in-site delivery confirmation.
• Proof / media: Publish [email protected], [email protected], and [email protected] as listed on the website. Add telephone, hours, service area, and map only when verified.
• Links: FAQ, docs, services, pricing, privacy.
• SEO: Title “Contact RightWay | Get product and partnership help”; description identifies available contact topics; H1 above; H2s “Choose a topic,” “Send a message.” Intent: reach RightWay.
• Responsive: Desktop topic cards and form in two columns; tablet two-card layout; mobile stacked cards and full-width form controls.

3. Design system

• Direction: Premium / bold; bright, warm light surfaces, dark forest-green text, deep-green actions, lime highlight, restrained peach/lavender accents. Dark mode is intentionally not offered.
• Typography: Sora headings and IBM Plex Sans body text, bundled locally with Fontsource so the marketing site and Docusaurus docs share the same typography without requesting fonts from a third party.
• Spacing: 4px base scale; 8/12/16/24/32/48/64/80/96px steps. Content container max width 1200px; mobile gutters 18px, tablet 28px, desktop 32px.
• Shape: Cards 20–24px radius; images and feature panels 24–32px; pill controls fully rounded. Avoid rounded shapes on long-form copy blocks.
• Buttons: 54px minimum height, 44px compact, 48px minimum touch target; solid green primary, dark secondary, outlined tertiary. Visible focus ring; hover state changes color and lifts no more than 2px.
• Cards: White or soft-green surfaces, subtle 1px border; hover lift and shadow are supplementary, not required to understand clickability.
• Color/contrast: Verify text and controls against WCAG 2.2 AA contrast (4.5:1 body text, 3:1 large text and UI boundaries). Never use green/lime alone to signal state.
• Accessibility: Semantic landmarks, one H1 per page, logical heading order, skip link, keyboard-operable disclosures/forms, clear labels, visible focus indicators, reduced-motion support, and descriptive alt text; decorative images use empty alt text. Avoid text embedded in images. Validate WCAG AA contrast and keyboard behavior before release.
• Responsive behavior: Mobile-first CSS; test at 360, 768, and 1280px. No horizontal overflow; preserve reading order and show full keyboard focus.

4. SEO and content governance

• Use canonical, lowercase, hyphenated URLs. Generate sitemap and robots routes from live routes and published Markdown only.
• Give each indexable page a unique title, meta description, canonical URL, and descriptive Open Graph data.
• Use Organization, WebSite, Article, and FAQ schema only where accurate and represented by visible page content. Never emit aggregate ratings without a real public data source.
• Do not publish placeholder customer names, company logos, testimonials, counts, review scores, credentials, founder identities, or outcome claims. Keep case studies empty until approval evidence is recorded.
• Review plan amounts and feature availability against the actual billing product before each release.