Logspot is an open-source changelog template built with Nuxt, Vue, and Tailwind CSS. Every Markdown file in its content/posts folder becomes a changelog entry through Nuxt Content, with frontmatter for the date, authors, and version, syntax highlighting for code blocks, icons, and an alert component you can use inside posts.
How does the integration work?
Appwrite Sites includes Logspot in its template library. When you create a site from the template, Appwrite runs nuxt generate on the template from the appwrite/templates-for-sites repository and serves the generated pages as a static site on an Appwrite domain. If you connect a repository, every entry you push to the production branch is built and published.
Appwrite applies these build settings to the template:
| Setting | Value |
|---|---|
| Framework | Nuxt |
| Install command | npm install |
| Build command | npm run generate |
| Output directory | ./dist |
| Rendering | Static |
The template builds on the node-22 runtime, which _APP_SITES_RUNTIMES enables by default. To create a repository from the template, configure version control for your instance first. Connect later deploys the template straight from its public GitHub source.
How to implement
To deploy Logspot with Appwrite Sites, there are several steps you must complete:
Step 1: Create a site from the template
For this step, you must create an account on Appwrite Cloud or self-host Appwrite if you haven't already. In your Appwrite project, go to Sites and click Create site. Search the templates for Logspot and select it.
Enter a Site name and a Site ID, then choose how to manage the code:
- Connect your repository creates a new repository from the template with your Git provider, such as GitHub, or connects one you already have, and redeploys on every push to the production branch. Choose this to publish your own changelog.
- Connect later deploys the template as it is. You can connect a repository afterwards from the site's Settings > Git repository.
Pick a subdomain under Domain and click Deploy. You can follow the build logs in the Console, and the site goes live on that domain when the build succeeds.
Step 2: Write your changelog
Clone the repository and replace the sample content:
content/posts/: one Markdown file per changelog entry. The sample posts show the frontmatter and the components you can use.components/Hero.vue: the heading, logo, and introduction at the top of the page. The logo ispublic/logo.png.pages/index.vue: remove the<github />component, which the template marks for removal after you clone it.seoConfig/index.js: the page title, description, and Open Graph tags.
A changelog entry starts with frontmatter like this:
---title: Dark mode is heredate: November 06, 2026authors: - { name: Jane Doe, avatar: https://example.com/jane.png }version: "1.04"---Commit and push to the production branch. Appwrite generates the pages again and activates the new deployment.
Step 3: Add a custom domain
Open your site's Domains tab to serve your changelog from your own domain, such as a changelog subdomain. Follow Add a custom domain for the DNS records to create.
Read more about Logspot and Appwrite Sites
If you would like to learn more about Logspot and Appwrite Sites, we have some resources that you should visit:
