u/tffarhad

Hey everyone,
Just wanted to share a quick update on Astroplate (our Astro free starter template with 1.1k+ Github stars and 400+ forks).

We just bumped the template to Astro v7 along with the framework update, we added native AI agent skills directly into the codebase.

If you use tools like claude code, cursor, or any agentic workflows, those agents can now work with Astroplate without hallucinating or guessing.

These added configurations give the agents explicit boundaries and exact instructions on how the project architecture works, saving you from broken code and context-shifting errors.

what’s inside now:

• full Astro v7 compatibility
• bundled agent skill definitions for context preservation
• strict pnpm workspace setup
• clean tailwindcss and typescript configurations

If you are planning to work on a new Astro project, you can start with Astroplate and modify it based on your needs instead of starting from scratch. It provides the foundation that will save you hours of time (and a lot of tokens) when building with coding agents.

Check out the repository here: https://github.com/zeon-studio/astroplate

Hey everyone,

I wanted to share a quick update. We just added native AI agent skills to all 47 of our Astro templates.

If you use Claude Code, Cursor, or Antigravity, you know they tend to hallucinate or guess when they lack codebase context. You end up wasting tokens correcting the AI.

To fix this, we integrated skill files directly into the themes. These are instruction packages that give coding agents exact context for:

• Routing: Adding new pages, routes, and sections.
• Components: Using and modifying built-in UI components.
• Content Management: Creating and editing Markdown and MDX files.
• Configuration: Updating site settings, navigation, and SEO.
• Architecture: Understanding codebase structure and data flow.
• Styling: Customizing Tailwind CSS and the theme engine.
• External Skills: Finding and using third-party agent skills from the web if your project needs extra capabilities.

This forces the agent to follow the actual conventions of the template instead of making things up.

We also added these AI agent skills to our open-source Astro starter template, Astroplate. You can try it completely free to see how it works.

Try Astroplate - https://github.com/zeon-studio/astroplate (Updated to Astro 7.0)

Explore Themefisher's Astro themes - https://astro.build/themes/author/946

Feel free to share any feedback.

Here's a Summary of What's New in Astro 7.0

• Performance is the headline. The .astro compiler was rewritten in Rust. Markdown and MDX now run through a Rust-powered pipeline called Sätteri (built by Erika from the core team). The rendering engine was replaced with a queue-based approach. Combine that with Vite 8 and its new Rolldown bundler, and builds are 15-61% faster across the board. The Cloudflare docs site (8,400+ pages) went from 387s to 262s. The Astro Website site went from 63s to 24s.
• The new Rust compiler has one breaking change worth knowing. No more silent HTML correction. The old Go compiler would reorder elements and auto-close tags. The new one treats your markup as-is and throws errors on unclosed tags. Also, whitespace between inline elements now follows JSX rules, so <span>Hello</span><span>World</span> renders as "HelloWorld" with no space.
• Route caching is now stable. It was experimental in v6. You get a single platform-agnostic API and new experimental CDN providers for Netlify, Vercel, and Cloudflare.
• Advanced routing is interesting. You can now add a src/fetch.ts file and take full control over the request pipeline. Hono is supported, so you can compose middleware in any order.
• AI tooling is genuinely useful. astro dev --background starts the dev server as a managed background process. Astro can detect when it's running inside an agent and enable this automatically. JSON logging is also in, which was the most upvoted roadmap request.

Upgrade via

npx @astrojs/upgrade

What's everyone's take on the Rust compiler change?

I noticed the blog comment section is the 2nd most upvoted feature request on the GHL ideas board. it has been planned since 2022 but still hasn't shipped.

We originally built an open-source comment system called OpenRemark for static sites like Astro, Hugo and Next.js. after seeing how many people struggle with this missing feature in GoHighLevel, we made sure it works here too.

It drops into any GHL blog or website page via a custom html block. it includes threaded replies, google sign-in, and a full moderation dashboard.

Pricing options:

• Self-host: 100% free for unlimited websites.
• Cloud version: free for a single site, with a paid plan for unlimited sites.

Setup takes less than 5 minutes. i wrote a step-by-step guide showing exactly where to paste the code block in your GHL blog template.

You build a fast, clean static site using Astro, Hugo, or Next.js. Everything is secure and highly optimized. Then a client or reader asks for a comment section. Suddenly you face bad choices.

Third-party scripts bloat your page.
They track your readers and inject ads.
Premium SaaS tools cost too much for simple text.

You are forced to choose between user privacy, high monthly costs, or a terrible user experience.

We hit this exact wall constantly. We wanted a lightweight, self-hosted option that respected privacy. So we built OpenRemark.

OpenRemark is a free, privacy-first, self-hosted comment system for static websites. It embeds into any static site with two lines of code. You keep complete ownership and control your data.

Here is what it offers:

• Absolute privacy: Zero tracking scripts, zero ads, and zero data sharing.
• Full control: A dedicated moderation dashboard, spam protection, and domain allowlisting.
• Frictionless UX: Built-in Google sign-in for one-click login and clean threaded replies.
• Free and MIT licensed: Your data stays entirely yours.

Stop compromising your static architecture just to let readers speak.

Btw, we are live on Product Hunt today.

👉 Please support our launch on Product Hunt.

https://shop.astro.build/

If you’ve ever tried using the official n8n integration for GoHighLevel, you already know:

• It's too limited: only gives you 17 basic actions.
• Zero native triggers: there are no built-in triggers, forcing you into annoying workaround setups just to catch events.
• Annoying setup: your users or clients have to create a "personal app" on their end. it’s a friction-heavy process for non-technical people.

That's why we created the n8n GHL Bridge.

We wanted a plug-and-play setup with actual depth. we handled all the app-side architecture on our end so your users don't have to touch it.

What the n8n GHL bridge does differently:

• Zero technical friction: just install the app directly to a sub-account. no personal app creation required.
• 40+ actions & 30+ triggers: massive upgrade to functionality (handles appointments, contacts, conversations, etc.).
• 100% free.

Our integration just got officially approved by the GoHighLevel team and is live on the marketplace.

Let me know if you run into any issues or have feedback on features we should add next.

Just saw the latest issue of Astro Weekly hit #132. Nathan has been running this newsletter consistently since 2023.

Definitely worth a follow if you want a clean weekly roundup of what's happening in the ecosystem.

https://newsletter.astroweekly.dev/

Just created this one using the Gohighlevel AI Studio…

One of the fastest static site generators out there keeps growing.
Congrats to the Hugo community and everyone who's built something with it.

I have been seeing a lot of talk about adding llms.txt to GHL sites for AI search visibility. thought i'd share what i actually found after looking into it.

first, the honest take from Google itself.

Google’s Search Advocate John Mueller addressed this directly on Bluesky recently. SEO expert Lily Ray asked him about the irony of Google publishing llms.txt files for its own developer docs while also saying the format is not needed for search performance. Mueller’s response was:

>for non-developer sites, i don't think this makes much sense, even with more agentic traffic in the future... making a markdown version of a shoe's specs is not going to get you more sales.

>your site has much more important things to do for SEO than to prepare for a potential future situation that may or may not come. prioritize needs before dreams.

so no, this is not a rankings tactic. if you're adding it expecting a traffic boost, you'll be disappointed.

So where it does make sense?

If you have a documentation-heavy site, serve tech clients, or want your site readable by AI agents and coding tools it's still worth having. that use case is real.

But the problem is, GHL doesn't let you upload .txt files to the root of a domain at all. so /llms.txt just doesn't work natively. there's a feature request on the ideas board with 50+ votes but no movement yet.

The workaround most people use currently:

- generate the llms.txt file manually.
- host the txt file on github gist or s3,
- then set up a 301 redirect in sites > settings > url redirects pointing /llms.txt to that external raw URL.

it works, but it's annoying to generate and maintain every time your site changes.

To solve this, here is a GHL marketplace app called LLMS.txt Generator that automates the whole thing. It crawls your active pages, generates a standards compliant txt file, uploads it to your Media Storage and creates the /llms.txt redirect automatically.

if you think it's worth adding for your use case, here's the full breakdown on How to Add llms.txt to a GoHighLevel Website (until GHL ships this natively)