Generate
Start from the admin dashboard and turn a prompt into a structured article draft.
Content operations · Forgewise.tech
Turn a content brief into a site you can run.
AstroGarden connects AI-assisted article generation to a real editorial decision, a reader-ready Astro site, and the controls that keep a client site maintainable after launch.
For technical founders, indie builders, small product teams, and operators running content sites for clients.
AI content operations
draft → review
Astro output
operator control
At a glance
The product is split between the work of publishing and the work of operating the site.
A content system with a visible handoff at every stage.
Decide
Use auto, review, or timed mode to set how much editorial control the site needs.
Publish
Ship static Astro pages with article metadata, archives, and discovery surfaces.
Operate
Manage tenant settings, domains, lifecycle state, requests, and safe fleet changes.
Editorial modes
AI can move quickly without deciding everything for you.
AstroGarden keeps the publishing decision explicit. The mode is a tenant setting, so the same product can support a hands-off stream, a careful approval queue, or a defined waiting period. Draft and edit articles, choose whether to publish immediately or prepare a post for review, and schedule posts for release. Create or upload cover images to go with your content.
Publish immediately
Use auto mode when a generated post should go live as soon as the generation flow completes.
Hands-off publishingHold for approval
Keep generated work in the pending review queue until an admin inspects it and chooses to publish.
Human decision requiredOpen a release window
Set a hold window in minutes. A post can be rejected during the window; otherwise the configured timed flow can publish it.
Configurable delayReader-facing publishing
The draft becomes a complete article, not a text blob.
Generation returns the pieces a publishable post needs: title, excerpt, Markdown body, tags, reading time, and an optional AI-generated cover image. Slug deduplication is built into the post flow. Choose immediate publishing, review, or scheduled releases while preserving editorial-mode behavior.
See the public blog surfacepublished-post.astro
contentMarkdown article body
discoverycategories · tags · sitemap
sharingOpen Graph · Twitter cards
mediaoptional Imagen cover
deliverystatic Astro HTML
Discoverable structure
Posts are organized through category and tag archives, with sitemap generation and social metadata in the published output.
Useful post context
Give readers the title, excerpt, cover image, reading time, category, and tags alongside a concise answer, review date, author details, and any source links you supply.
More than the blog
The public site can also expose contact, booking, newsletter, and other configured lead-routing surfaces alongside its articles.
Tenant administration
Keep the site’s identity and publishing rules in one console.
After launch, administrators can work on the content itself and the site around it. Settings are stored per tenant, while protected operations stay behind the admin session.
Shape the customer-facing site
Update database-backed branding, copy, layout, blog categories, and lead-routing settings for contact and booking submissions.
- Brand and copy controls
- Layout and category settings
- Contact and booking recipients
Move work from draft to live
Draft and edit articles in the admin console, create or upload a cover image, and choose immediate publishing, review, or a scheduled release. Inspect pending posts and manage publishing from the same surface.
- AI generation from the dashboard
- Pending review queue
- Manual publish and delete actions
- Immediate, review, and scheduled publishing
- Cover image creation and upload
See the audience signals
Add contact, booking, and newsletter forms to give readers a clear next step. Review responses in the admin console for follow-up, send lead alerts to your selected recipient, and forward subscribers who opt in to your configured mailing-list service.
- Contacts
- Bookings
- Newsletter subscribers
- Lead notifications to selected recipient
- Opted-in subscriber forwarding
From setup to publishing
A launch path with a clear operational handoff.
AstroGarden’s public checkout collects the site inputs, the billing confirmation, and the database path before the control plane starts provisioning.
- 01
Describe the site
Provide the business name, admin email, site slug, optional custom domain, notes, and launch details.
- 02
Choose database setup
Use an existing MongoDB URI, or choose managed Atlas provisioning so the control plane can create the database user and resolve the connection during provisioning.
- 03
Confirm the subscription
Checkout uses Stripe. After payment confirmation, AstroGarden verifies the billing session before creating the client site record and provisioning job.
- 04
Hand over the admin surface
The queued provisioning flow prepares the client site and its initial admin handoff. Site identity, release metadata, and database mode travel with the record.
Important: a confirmed payment and a live site are separate states. If provisioning fails after payment, the billing session is marked failed rather than presented as complete.
Operations after launch
Give operators the controls that a growing site needs.
These are authenticated control-plane actions, not promises of self-service magic. The admin console keeps state, instructions, and review points visible.
Domain readiness
Track custom-domain status, DNS instructions, routing notes, SSL status, and verification without confusing DNS propagation with a failed site.
Lifecycle state
Move a client site into suspended, cancelled, or archived states. Billing status changes are explicit operator choices rather than automatic side effects.
Retention and teardown
Review export and purge timestamps. Cancellation or archival can lead to infrastructure teardown and deletion of client-owned and control-plane collections after retention handling.
Site and domain administration
Manage site settings, custom domains, and export site information for client handoff or archival.
Safe fleet updates
Share improvements without overwriting customer work.
Preview shared updates across customized client sites before preparing changes for review. Check changed files against each site's protected custom-work paths; invalid paths are refused and overlapping custom areas require manual review.
Request approved developer accessPreviewchanged paths
Guardprotected paths
ProposeGitHub pull request
Customer request flows
When the next step needs a person, use a defined request.
The public request page accepts structured submissions without exposing the admin token. Each path validates its inputs and stores a normalized record for follow-up.
Paid work request
Capture the site slug, requester, subject, budget, priority, and details for a scoped piece of work.
Developer access request
Request repository handoff or a Replit invite for approved custom work, with access type, repository context, and reason.
The system behind the page
Three surfaces, one publishing loop.
AstroGarden keeps public delivery, authenticated administration, and operator provisioning distinct so each surface can have the right permissions and failure states.
Public Astro site
Reader-facing pages, blog archives, categories, tags, metadata, forms, and optional lead capture.
Admin console
Post generation and review, tenant settings, inboxes, billing sessions, domains, requests, and lifecycle controls.
Control plane
Subscription verification, provisioning jobs, managed Atlas setup, deployment state, retention, and guarded fleet releases.
Ready to grow the site?
Start with the workflow. Keep the controls.
Launch AstroGarden when you want AI-assisted publishing connected to review rules, static delivery, and an operator surface that remains useful after day one.