Skip to content

Nuxt Studio (Visual Editor) ​

Nuxt Studio is a web-based editor for the website's content. It lets you write and update investigations, pages, and translations in your browser, with a live preview, without touching Git, the command line, or a code editor. When you save, Studio commits your changes to GitHub for you, and Vercel deploys them automatically.

Use this when you want to edit content but don't want to set up a local environment (see Getting Started for the full developer setup).

Where to Find It ​

WhatURL
Studio editor (production)https://www.ongehoord.nl/_studio
Live websitehttps://www.ongehoord.nl
This documentationhttps://docs.ongehoord.nl

The editor lives at the /_studio path on the main site. There is no separate app to install.

How It Works ​

Studio is connected to the project's GitHub repository (Ongehoord/website) on the main branch. The flow is:

  1. You open the editor and sign in.
  2. You edit content in a visual interface (or raw Markdown).
  3. You save / publish your changes.
  4. Studio commits those changes to the main branch on GitHub.
  5. Vercel detects the commit and redeploys the live website automatically.

Because it writes to main directly, anything you publish goes live after the deploy finishes (usually a minute or two). There is no pull-request review step in this path, so double-check before publishing.

Signing In ​

  1. Go to https://www.ongehoord.nl/_studio.
  2. Authenticate with the GitHub account that has access to the private Ongehoord/website repository.
  3. If you don't have access, ask a developer on the team to add your GitHub account as a collaborator.

WARNING

The repository is private. Only invited GitHub collaborators can open and use Studio. If the page asks for access you don't have, you need to be added to the repo first.

The "Edit this page" Button ​

Once you're signed in to Studio, a blue "Edit this page" button appears in the bottom-right corner of every page on the live website. Click it to jump straight into the editor in a new tab.

This button is the fastest way in: browse the live site normally, and when you land on a page you want to change, click Edit this page.

  • It only appears when you are signed in to Studio. Normal visitors never see it.
  • It opens the full Studio editor in a new tab, so you keep the page you were reading.
  • If you don't see it, you're not signed in yet — open /_studio once to sign in, then the button appears across the site.

Editing Content ​

Inside Studio you can:

  • Browse the content tree (the same content/nl/ and content/en/ folders described in Content Structure).
  • Edit an existing page in a rich visual editor or as raw Markdown.
  • Edit frontmatter (title, description, images, dates) through a form, so you don't have to remember the field names. See Frontmatter Reference for what each field means.
  • Upload and insert images from the media library.
  • Switch between Dutch (nl) and English (en) versions. The default locale is Dutch. See Translations & i18n.

The preview pane shows how the page will look on the live site before you publish.

Publishing Your Changes ​

When you're happy with an edit:

  1. Click Save / Publish in Studio.
  2. Studio commits to main on GitHub.
  3. Wait for the Vercel deploy to finish (a minute or two).
  4. Refresh the live page at https://www.ongehoord.nl to confirm.

TIP

If your change doesn't appear after a couple of minutes, it's almost always the deploy still running, not a lost edit. Git keeps every version, so nothing is deleted.

Studio vs. the Git Workflow ​

Both routes end up in the same place (main → Vercel deploy). Pick based on what you're comfortable with:

Nuxt StudioGit workflow
Setup neededJust a browser + GitHub accessGit, Node, pnpm, editor
Best forQuick content edits, non-developersNew investigations, bulk changes, automation scripts
Review stepPublishes straight to mainCan use pull requests
PreviewBuilt-in live previewLocal pnpm dev

For larger work (a whole new investigation, running the automation scripts, or anything that needs a pull request), use the Publishing Workflow instead.

Troubleshooting ​

  • Can't open /_studio — you're probably not signed in, or your GitHub account isn't a collaborator on the private repo. Ask a developer to add you.
  • Changes not live — the Vercel deploy is still running. Wait a minute and refresh.
  • Something looks broken — don't panic. Every save is a Git commit, so any change can be undone by a developer.