GostraxGet Early Access →
HOW GOSTRAX WORKS

From the first request.
To a considered update.

A shared workflow for your Astro client sites. Your client has a place to ask and prepare content. Your agency sets the permissions, reviews the work and controls the next step.

Get Early AccessWalk through the steps
ONE UPDATE / SIX CONNECTED STEPSInteractive illustration
AGENCY

Start with your Astro site.
Give it a workspace.

Atelier imports its existing Astro website from GitHub.

Explore this step
ATELIER / ASTRO WEBSITE
↗Client requestUpdate the homepage introduction
▤Content draftPrepared within client permissions
✓Agency reviewApproval before publication
CURRENT STEP / 01 · CONNECT
YOUR SITES. YOUR RULES.MADE FOR ASTRO
HOW A CLIENT UPDATE MOVES THROUGH GOSTRAX

One real-world request.
A clearer way to handle it.

Follow an illustrative homepage copy update for Atelier. The workflow below separates project setup, client collaboration, content review and publication, so you can see who does what.

01 / AGENCY

Start with your Astro site.
Give it a workspace.

Connect the Gostrax GitHub App, choose a repository and branch, and import your Astro project. Its preview, source, media and client access belong to the same project.

  • Select the repositories available to the GitHub App.
  • Open the project’s Overview, Build, Files and Library.
  • Review the project before configuring client access.
THE ATELIER EXAMPLEAtelier imports its existing Astro website from GitHub.
ILLUSTRATIVE WORKFLOW / CONNECT
02 / AGENCY

A dedicated client space.
With boundaries you choose.

In Clients, configure access using the client’s verified account email. Set dashboard, preview, requests, statistics and content permissions separately. Enable text editing only for pages you approve.

  • Client access is separate from agency team membership.
  • Choose approved pages when enabling text editing.
  • Preview the client dashboard before handing it over.
THE ATELIER EXAMPLEThe client can request changes and edit the homepage text. Publication stays with the agency.
Understand client permissions ↗
ILLUSTRATIVE WORKFLOW / SET ACCESS
03 / CLIENT + AGENCY

Keep the conversation
close to the website.

The client uses a project conversation to explain what needs changing. Their space can also include the site preview, statistics and content drafts, depending on the permissions you grant.

  • Requests stay connected to their project.
  • Clients can discuss design changes with the agency.
  • Design and source editing remain agency tools.
THE ATELIER EXAMPLE“Can we update the introduction for our new collection?”
ILLUSTRATIVE WORKFLOW / COLLABORATE
04 / CLIENT + AGENCY

Make the next update.
Stay within the scope.

Clients with content permissions can prepare text or article drafts. Your agency can work with AI, select elements in the preview or use expert mode to edit the Astro source directly.

  • A saved draft is not a published change.
  • Text drafts target approved pages.
  • Article creation and media uploads have separate permissions.
THE ATELIER EXAMPLEThe client saves a proposed homepage introduction, then submits it for agency review.
ILLUSTRATIVE WORKFLOW / PREPARE
05 / AGENCY

Take a closer look.
Then make the call.

Review submitted content in the client workspace’s agency preview. Approve it or return it with a review note. The Build workspace lets your agency inspect the site and refine work in context.

  • Agency review is a distinct step in the draft lifecycle.
  • Approval and publication are separate actions.
  • Use the live preview and source for your agency’s own edits.
THE ATELIER EXAMPLEThe agency checks the wording and approves the content draft.
ILLUSTRATIVE WORKFLOW / REVIEW
06 / AUTHORIZED PUBLISHER

Approved content.
A configured path to live.

With publication configured, an authorized user can queue an approved content change. The project needs GitHub and Vercel connections; article publishing also needs a configured template.

  • Publish access is independent from drafting access.
  • Publication setup is checked for each project.
  • Review the publication status; a queued job is not yet a live update.
THE ATELIER EXAMPLEThe approved introduction enters the publication workflow for the configured Astro project.
ILLUSTRATIVE WORKFLOW / PUBLISH
BEFORE THE FIRST PUBLICATION

A little setup.
A clear responsibility.

An Astro project

Import a supported Astro repository and choose the branch you want to work with.

A verified client account

Configure access for the client’s existing verified account, then choose the permissions appropriate to that project.

Publication connections

Connect GitHub and Vercel for the project. Articles also need an article template. Early access is available by invitation.

A FEW CLEAR ANSWERS

The workflow,
without the guesswork.

What is the Gostrax workflow?

An agency imports an Astro project, configures client access and collaborates on requests. Permitted content can become a draft for agency review. Approved content can enter the publication workflow when the project is configured for it.

Does every client message automatically change the website?

No. A project conversation is a way to discuss requests with the agency. Content drafting, agency review and publication are distinct actions, controlled by permissions and project setup.

Does approving a draft publish it?

No. Approval marks content as reviewed. Publication is a separate action, requiring publication access and a configured GitHub and Vercel workflow.

Can I bring a WordPress website?

Gostrax currently supports Astro projects. GitHub import is for an Astro repository; it is not a WordPress migration service.

THE BOUNDARIESClient permissions ↗THE BIGGER PICTUREGostrax for agencies ↗THE TOOLKITExplore the features ↗
YOUR NEXT CHAPTER

Your client sites.
Managed by you.

One workspace for your agency. A dedicated space for your clients.
Built for Astro. Controlled by you.

Get Early Access →Free to join. We’re onboarding a small number of agencies at a time.