Marketing pages

Edge Kit includes a public website alongside the customer application. The landing page, pricing, blog, contact form, and legal content share a marketing layout, so you can explain your product and guide visitors into registration without maintaining a separate site.

The starting pages demonstrate a complete presentation. Adapt their copy, imagery, sections, and calls to action around the audience and offer you actually serve.

Landing page

The landing page combines an opening product message, features, testimonials, a comparison, pricing, and frequently asked questions. Each section is a component you can edit, move, or remove according to your product's story.

Start with the customer problem and the result your product delivers. Follow that with enough detail to explain the workflow, evidence that supports your claims, and the next action a visitor should take.

Use your own product screenshots and verified customer quotes. If a starting section does not yet have real content behind it, simplify the page instead of carrying template claims into production.

Pricing and checkout

The pricing interface uses the shared billing catalog. Plan names, features, intervals, and offers should describe the same product customers encounter at checkout and in billing settings.

Keep a plan's marketing description aligned with what your server actually grants. For example, a storage allowance needs a corresponding upload policy, and a paid AI feature needs the appropriate access and usage rules.

The contact-sales option can direct visitors toward a conversation when self-service checkout is not the right next step. Review that destination along with the main registration and pricing actions.

Contact

The contact page connects a validated form, Cloudflare Turnstile, and the email integration. Its recipient comes from CONTACT_EMAIL, giving you a working support or sales entry point with bot protection already connected.

Adapt the labels and message prompt around the information you need. Keep the submission short enough for the visitor's goal and make the success state clear about what happens next.

The forms guide explains the interaction and server checks. Email configuration covers the destination and sender used for delivery.

Content and language

Interface copy uses translated messages, while long-form articles and legal documents use the content collections. This keeps page controls, product messaging, and structured content in the appropriate editing workflow.

When introducing a language, review the whole public journey: landing copy, plan descriptions, contact feedback, legal links, and registration. A translated header alone does not give a visitor a complete localized experience.

Internationalization explains the language model, and blog content covers article metadata, publishing, and legal documents.

Navigation and branding

The shared header and footer connect public pages and product actions. Keep their destinations consistent, remove template links that do not belong to your product, and make contact and legal information easy to find.

Apply your branding across the website and application together. Logos, product names, social images, and email assets should feel like the same product when a visitor moves from discovery to account verification.

Check long navigation labels and pricing cards on smaller screens. A call to action should remain reachable without covering the copy it supports.

Search and sharing

Give each public page a distinct title and description, a suitable canonical URL, and a reachable social preview. Add new public destinations to the sitemap and link them from relevant content instead of relying only on search discovery.

Use descriptive links between an article and the feature or offer it explains. Keep private customer pages out of public content and navigation intended for search engines. The SEO guide covers the included metadata and crawler setup.

Customer journey

Before release, follow the site as a first-time visitor: understand the offer, inspect a plan, register, verify the account, and reach the promised feature. Then repeat from a blog article and from the contact page.

This catches inconsistencies that reviewing sections separately can miss, such as a different plan name at checkout, an outdated product name in verification email, or a primary button that leads to the wrong destination.