Frequently Asked Questions

Nexus is a modern Astro website template with composable components, built-in i18n support, and a documented dark-mode foundation. Verify the assembled site for your project's accessibility and performance needs.

Nexus is designed for developers, freelancers, agencies, and teams who want to ship professional websites quickly. Whether you're building a SaaS landing page, a portfolio, a blog, or a corporate site, Nexus provides the building blocks.

Nexus is template software — the licensing page describes the current usage terms.

Nexus is built with Astro, Tailwind CSS v4, and TypeScript. It uses CSS custom properties for theming, supports MDX for content, and generates static pages by default for maximum performance.

Yes! The Starter plan is completely free and includes all 183 components, dark mode support, i18n for 5 languages, and community support. It's perfect for personal projects and experiments.

Absolutely. You can upgrade or downgrade your plan at any time. When upgrading, you'll be charged the prorated difference. When downgrading, the credit will be applied to future invoices.

Yes. We offer a 30-day money-back guarantee on all paid plans. If you're not satisfied, contact our support team for a full refund — no questions asked.

The template ships no payment processing. Which payment methods you offer depends on the billing provider you connect.

All design tokens are defined as CSS custom properties in the global stylesheet. You can override colors, spacing, typography, shadows, and more by editing the token values to match your brand. Dark mode is built in and toggles via a class on the <html> element.

Yes. The default build is hybrid: pages are prerendered as static HTML, and the routes that need a server (sign-in, forms, APIs) render on demand through the Astro Node adapter. Run `pnpm build --static` for a fully static site when you don't need those.

Nexus includes built-in internationalization for 5 languages (English, German, French, Spanish, Bulgarian). Translations are stored in JSON files, and routing automatically handles locale prefixes. You can add new languages by creating a new translation file.

Components use semantic HTML and documented keyboard and ARIA patterns. Validate the components and combinations you ship against your accessibility requirements.

Absolutely. Each component is self-contained and can be imported independently. Mix and match only what you need — no forced imports or unused code in your bundle.

Start with the documentation in the repository, then open an issue for anything it doesn't answer. For help with your own project, get in touch through the contact page.

Yes. The repository documentation covers installation, components, theming, i18n, authentication, forms and deployment.

Yes, our Enterprise plan includes custom component development. For one-off customizations, you can also reach out to our team for a quote on specific projects.