Page text and headings
Wording on existing pages, including headings and body copy.
Describe the change. Review the edit. Publish with confidence.
We build your website and set up Visual Studio Code with an AI assistant in its integrated terminal. After setup and training, your team can describe routine updates in plain language, review the proposed changes and publish through the workflow configured for your site.
Delivered remotely. USD $30–$100/hr depending on the type of work. Request a free initial analysis. Often paired with WordPress and WooCommerce development or a custom web build, since we maintain the sites we build.
Change our weekday hours to 9 AM–6 PM on the contact page.
> Reviewing contact.html… − Mon–Fri: 9 AM–5 PM + Mon–Fri: 9 AM–6 PM ✓ Proposed edit ready for review
Our workflow uses Visual Studio Code with an AI coding assistant running in its integrated terminal. We set up the website project and publishing workflow, so a plain-language instruction can be turned into a proposed file change.
The assistant prepares edits to the actual project files. The changes are reviewed in the editor and checked in a website preview before publishing through the configured deployment process. This is a coding-assisted workflow, rather than a browser-based drag-and-drop editor.
We train your team to operate the AI assistant in VS Code, review its proposed edits and use the configured preview and publishing workflow. During setup, we agree who can edit and who can publish. Tool accounts, subscriptions, project access and ongoing support are scoped separately. An AI-generated edit still needs review: text, links, layout and forms should be checked before it goes live.
The animation above uses fictional opening hours and a scripted code change to explain the sequence. It does not connect to an AI model, modify files or publish a website.
Routine content, on the pages that already exist. What is editable is defined during the build and depends on how your site is put together.
Wording on existing pages, including headings and body copy.
Opening hours, phone numbers, email addresses and locations shown on the site.
Swapping images on existing pages and updating their alt text.
Details of services or products you already list — descriptions, inclusions, ordering.
Blog posts, news items and notices, where the site has somewhere to put them.
Wording and ordering of sections and menu items that already exist.
Layout and design changes, new pages or sections that do not exist yet, new features, integrations with other systems, and anything structural are development work rather than content edits. If a request turns out to be one of those, we will say so and scope it separately rather than attempting it blind.
You work in your own configured website project in VS Code. Ask the AI assistant to change text, opening hours, images or other agreed content, then inspect the changes and check the website preview. This is an editing workflow using development tools, rather than a separate browser-based CMS dashboard.
Our setup and training cover opening the project, starting the assistant, writing clear instructions, reviewing edits, previewing the site and using the agreed publishing and recovery steps. Larger changes and ongoing technical support can be scoped separately.
Our work is billed at USD $30–$100/hour depending on scope and type of work. Initial analysis is free. Hosting, domains and AI-tool subscriptions are agreed separately.
Design and build the site around your content, services and goals.
Configure VS Code, the terminal-based AI assistant, project access, preview and publishing workflow. Walk your team through an example.
Run the assistant yourself and explain what should change. Review the proposed file edits and preview the result.
Use the publishing steps configured for your site, with the review and recovery process covered during training.
After setup and training, your team runs the AI assistant itself. You do not need to send every routine content update to ZuluLab. You do need to learn the configured VS Code workflow, check the assistant’s work and verify the preview before publishing.
AI can make mistakes, including edits outside your intended scope. We show you how to review changes and use the recovery process configured for the project. New features, integrations, site structure, payments, sensitive data and troubleshooting should come back to us for an agreed scope.
Account permissions and publishing access depend on the project. A plain-language assistant does not automatically provide the role controls, audit logs or approval gates of a dedicated enterprise CMS.
After setup and training, use the AI assistant in the VS Code terminal for agreed routine content: text, headings, business hours, contact details, images, service descriptions and existing posts or announcements. The scope depends on how your website is built.
You can request routine edits in plain language rather than writing code. You still need to learn the VS Code workflow, review proposed changes and check the preview. We provide setup and training; technical changes may need our help.
Yes. We configure and explain the preview and publishing workflow for your project. Review the website and proposed file changes before you publish. The exact steps depend on the site and hosting platform.
Do not publish a change that looks wrong. Use the review and recovery steps covered during setup, such as discarding an unpublished change or restoring a previous version using the configured project workflow. Contact us if you need help; support terms are agreed separately.
We can scope setup and training for the people you nominate. Each person needs appropriate tool and project access. Permissions and publishing responsibilities are agreed during setup; separate approval gates or audit systems are not included automatically.
Hosting, domains and any AI-tool accounts, subscriptions or usage charges are agreed separately. We confirm who owns and pays for each before setup. They are not included by default in development or training fees.
Sometimes. We assess the source files, platform, hosting and available access first. A static website, custom application and WordPress site can need different editing and publishing integrations. We confirm compatibility before promising setup.
For the initial website build, workflow setup and training, and for larger changes or technical support afterward. New functionality, integrations, payment or data handling, layout changes and troubleshooting are scoped separately. Routine edits within the agreed scope can be made by your team.
Tell us what your team wants to manage. We will explain the build, VS Code setup, training and publishing workflow.