AstroBlogSaaS

zenix — Astro Blog Template

By farrosfr

Zenix is an Astro-based SaaS theme template by Farros FR, featuring responsive landing page sections, pricing and FAQ, an MDX blog, a changelog, light and dark modes, and command palette search.

Explore the design

Compare the page layouts and mobile experience. Open any screenshot for a closer look.

3 previews
Desktop homepage1 / 3
Desktop captureTop of page

Actual screenshot captured by the server browser.

All pages & views 3

Screenshots show visual appearance; interactive behavior may differ.

Recorded 2026-10-02View source

What stands out

A quick read of the recorded project description.

01

Astro static output with Tailwind CSS for styling

02

Includes responsive SaaS landing page sections, plus pricing, FAQ, and testimonials pages

03

Blog and changelog are driven by Astro content collections; the blog supports MDX and reusable Callout components

04

Built-in light and dark modes with persisted user preference, command palette search, and Astro view transitions

05

Includes Playwright UI regression tests, runnable via npm run test:e2e

06

Site title, description, URL, and social links are configured centrally in src/config.ts

Template Details

Zenix is an Astro theme template for showcasing Micro-SaaS products, created by Farros FR and released under the MIT license. The template builds with static output, uses Tailwind CSS for styling, provides responsive SaaS landing page sections, and includes pricing, FAQ, testimonials, blog, and changelog pages. The content layer is based on Astro content collections: blog and changelog entries live in src/content/blog/ and src/content/changelog/ respectively, while author information lives in src/content/authors/. The blog supports MDX, allowing reusable components such as Callout to be used directly in the body. Site-level configuration is centralized in src/config.ts, including the site title, description, URL, and social links, which must be replaced with your own information before publishing. The template includes built-in light and dark modes with persisted user preference, provides command palette search, and uses Astro view transitions. The project includes Playwright UI regression tests, runnable via npm run test:e2e. The build output is a static site that can be deployed to static hosting platforms such as Vercel, Netlify, Cloudflare Pages, and GitHub Pages; the repository provides wrangler.toml, and for Cloudflare Pages the build command is npm run build with an output directory of dist. Statements in the README about perfect Lighthouse scores, conversion rates, and similar claims are the author's own and were not independently verified in this material; the licensing of third-party assets such as demo images, fonts, and icons must be checked separately, and external services such as domains and hosting may incur costs.

AstroBlogSaaS

Is it right for your project?

Use Cases

  • Building a showcase site for a Micro-SaaS product with a landing page, pricing, and FAQ
  • Writing product blog posts with MDX and publishing version changes via a changelog page
  • Deploying to static hosting platforms such as Vercel, Netlify, Cloudflare Pages, or GitHub Pages
  • Running Playwright tests on the template to check for page UI regressions

Suitable For

  • Developers who need an Astro static site with a SaaS landing page structure
  • Teams that want to maintain blog and changelog content with MDX
  • Sites that need basic interactions such as light and dark modes and command palette search
  • Projects planning to deploy to static hosting platforms and configure their own domain and build process

Getting started & customization

Use these recorded setup notes alongside the repository instructions for your chosen version.

  1. 1

    Create a project with npm create astro@latest -- --template farrosfr/zenix, or clone the repository and run npm install and npm run dev

  2. 2

    The local development server defaults to http://localhost:4321/

  3. 3

    Before publishing, modify SITE_TITLE, SITE_DESCRIPTION, SITE_URL, and SOCIAL_LINKS in src/config.ts

  4. 4

    For production, update site in astro.config.mjs to your own domain

  5. 5

    For Cloudflare Pages, use the Astro preset, build command npm run build, output directory dist, and Node.js version 22.12.0 or newer

Read repository instructions

License & source material

Usage conditions & limitations

Free to use · keep license notice

This entry covers the free version in the public repository under the MIT license; the free scope applies to that version's code and does not mean external services or third-party assets are free.

Must comply with when using

  • You may use, modify, commercialize, and distribute this version's code for free.
  • When distributing copies or substantial portions of the code, retain the original author's copyright notice and the full MIT license notice.
  • The code is provided as is; warranties and limitations of liability are governed by the original license and applicable law.

Additional costs & items to verify

  • Demo images, fonts, icons, and other third-party assets must be checked against their respective licenses and cannot be judged solely by the code's MIT license.
  • External services such as domains, hosting, databases, payments, or AI may incur additional charges.
View Original Text Basis

Compiled by DeepSeek based on repository license and README ·2026-10-02. Results only cover the materials read; dependencies, images, fonts, and subsequent term changes are subject to their respective original texts.

Project checks & description sources

Template Information

Source platforms
GitHub
Documentation and maintenance reference score
More documented · 92 / 100
Technologies
Astro
Website type
Blog · SaaS
How this score is calculated

Our heuristic uses license records (up to 30), a demo link (12), a preview (10), stars (15), recorded maintenance (15), description completeness (8), feature records (5) and classification data (5). It is not a code, security or performance test, or a Google score. A link does not establish tested functionality.

What to verify for this project

Repository update recorded
2026-09-13
Screenshot last checked
2026-10-02

A demo link is listed. Check it with your own content and viewport sizes; its presence does not confirm that forms, authentication or payments work.

The catalog identifies Astro as the primary stack. Check the actual dependency manifest and lockfile for versions and hosting requirements. These notes use recorded metadata, not a code audit or a deployment test.

Use a selection guide →

How this description was prepared

AI-assisted description based on catalog records and repository material. Repository authors are not automatically the reviewers of this description.

Automatically checked against source and license rules; no manual editorial review.

Inspect the recorded source material

SHA-256: ecec31025fe7593b520b7bd440967ceebafcfae1115b1c4d83ed6413f2ff1768

2026-10-02T16:53:38.927Z

Source file / repository
# Zenix

Zenix is a polished Astro SaaS theme by [Farros FR](https://farrosfr.com) with responsive landing sections, pricing, blog, changelog, dark mode, search, and MDX content support.

[Live demo](https://zenix.farrosfr.com/) · [Repository](https://github.com/farrosfr/zenix)

![alt text](readme-hero.png)
![alt text](readme-speed.png)
![alt text](readme-speed-mobile.png)

## Features

- Astro 6 with static output
- Tailwind CSS 4 styling
- Responsive SaaS landing page sections
- Pricing, FAQ, testimonials, blog, and changelog pages
- MDX content with reusable callout components
- Dark and light mode with persisted user preference
- Command palette search
- Astro view transitions
- Playwright UI regression tests

## Quick Start

Create a new Astro project from the GitHub template:

```bash
npm create astro@latest -- --template farrosfr/zenix
```

Or clone the repository directly:

```bash
git clone https://github.com/farrosfr/zenix.git my-saas-site
cd my-saas-site
npm install
npm run dev
```

Open `http://localhost:4321/` in your browser.

## Commands

```bash
npm run dev       # Start the local dev server
npm run build     # Build the production site
npm run preview   # Preview the production build
npm run test:e2e  # Run Playwright regression tests
```

## Configuration

Most site-level settings live in `src/config.ts`:

```ts
export const SITE_TITLE = 'Zenix';
export const SITE_DESCRIPTION = 'High-converting, performance-focused Astro theme for Micro-SaaS products.';
export const SITE_URL = 'https://zenix.farrosfr.com';

export const SOCIAL_LINKS = {
  twitter: 'https://twitter.com/farrosfr_',
  github: 'https://github.com/farrosfr',
  linkedin: 'https://linkedin.com/in/yourhandle',
};
```

Update these values before publishing your own site.

## Content

Blog posts and changelog entries are powered by Astro content collections.

- Blog posts: `src/content/blog/`
- Changelog entries: `src/content/changelog/`
- Authors: `src/content/authors/`

Example blog post:

```mdx
---
title: "My First Post"
description: "A short summary."
pubDate: 2026-06-01
author: farros
tags: ["update", "feature"]
---

# Hello World

<Callout type="success" title="Ready">
  MDX components can be used directly inside content.
</Callout>
```

## Deployment

Zenix builds to a static site and can be deployed to Vercel, Netlify, Cloudflare Pages, GitHub Pages, or any static hosting provider.

For production, update `site` in `astro.config.mjs` to match your domain.

### Cloudflare Pages

When importing this GitHub repository into Cloudflare Pages, use:

```text
Framework preset: Astro
Build command: npm run build
Build output directory: dist
Root directory: /
Node.js version: 22.12.0 or newer
```

The repository includes `wrangler.toml` with `pages_build_output_dir = "dist"` for Cloudflare Pages compatibility.

## Theme Submission Notes

This repository is public, uses public npm dependencies, and includes setup documentation for new users. Preview images for the Astro theme directory should be 16:9, at least 1280px wide, and less than 5MB combined.

## Contributing and Collaboration

We welcome contributions and collaboration! Whether you want to fix a bug, add a new feature, or improve documentation, your help is greatly appreciated. 

To contribute:
1. Fork the repository.
2. Create a new branch (`git checkout -b feature/amazing-feature`).
3. Commit your changes (`git commit -m 'feat: add amazing feature'`).
4. Push to the branch (`git push origin feature/amazing-feature`).
5. Open a Pull Request.

If you have an idea for a major change or a new feature, please open an issue first to discuss it with the maintainers. We are also open to collaborations on expanding Zenix for different use cases! Let's build something awesome together.

## License

MIT
Report a correction

Explore similar templates

Compare previews and descriptions within the same stack and category.