Zurück zum Blog
Jan Jansen

Zukunftskörper - Jans Hybrid Training & Longevity Blog

Introducing Zenix

A closer look at the structure, content system, and design choices behind the Zenix Astro theme.

release astro architecture

Auf einen Blick zusammengefasst

A closer look at the structure, content system, and design choices behind the Zenix Astro theme.

Inhaltsverzeichnis

A Practical Astro Theme for SaaS Websites

Building a SaaS product is hard enough. A good starter should give you a useful structure, sensible defaults, and room to adapt the details to your product.

Zenix is designed as a focused foundation for product websites: landing sections, pricing, blog content, changelog entries, and common UI patterns are all included.

The Zenix Philosophy

We believe that speed and beautiful design are not mutually exclusive. A theme should provide a rock-solid foundation, but get out of your way when you want to customize it.

Architectural Decisions

Zenix keeps the implementation close to Astro’s strengths: static output, content collections, MDX support, and small amounts of client-side JavaScript where interaction is needed.

1. View Transitions API

Astro’s View Transitions give this static site the feeling of a Single Page Application (SPA). When you navigate between pages, there is no hard refresh. The browser paints the new DOM instantly.

Zero Configuration

View transitions are enabled by default in Zenix. You don’t need to write a single line of JavaScript to get SPA-like routing.

2. The Dark Mode Engine

The theme includes a dedicated dark-mode color palette using Tailwind’s dark: variants. Backgrounds, borders, and text colors are tuned independently for light and dark mode.

/* Example of our complex utility layering */
@layer utilities {
  .glass-panel {
    @apply bg-white/70 dark:bg-slate-900/70 backdrop-blur-xl border border-slate-200/50 dark:border-slate-800/50 shadow-xl;
  }
}

3. The “Bento Box” Grid

The Features section uses a responsive bento-style grid. It keeps the layout expressive on larger screens while falling back to simpler stacked cards on smaller devices.

MDX Integration

This very blog post is written in MDX! That means we can interleave standard Markdown with complex Astro or React components.

Content Tip

Keep reusable components simple and focused. They should make content easier to read, not harder to maintain.

Supported Components

Currently, we ship with the highly versatile <Callout> component. You can pass type="info" | "warning" | "danger" | "success" to instantly change its appearance.

Customization Note

Replace the sample content, links, and metadata before publishing your own site.

Conclusion

Zenix is meant to be a starting point. Use the structure, adjust the copy, and shape the visual details around your own product.