How to use Cursor to build a marketing page editor
A job-board team tried Cursor with content creators, then used it to build a focused browser editor with chat-driven pages, style and tracking guardrails, and underlying Git versioning.
Prompt to try
Editorial adaptation, not the source author’s exact prompt. Replace bracketed inputs and review tool permissions first.
Build a browser-based page editor for [content team] using [repository]. Provide chat-driven page creation constrained by [style guide] and [tracking requirements]. Store and version pages in Git so engineers can use [test and deployment workflow] without exposing IDE or Git complexity to creators.
Reach people exploring AI agents
See placements →What happened
The team reports building the sitebuilder in days, with chat-based page creation, style-guide matching, tracking-pixel integration and Git-based storage and versioning.
Reported by ManuelKiessling on Hacker NewsHow the agent did it
- Introduced Webflow so marketing could create its own content pages.
- Tried giving content creators Cursor and encountered IDE and Git complexity.
- Used Cursor to build a focused browser-based sitebuilder.
Where a person stepped in
The author describes engineers supporting, testing and deploying through Git workflows but does not detail code-review steps.
A person approved each step before the agent continued.
ManuelKiessling's company runs a job board and already builds software as a core activity. Creating marketing landing pages competed with feature development, so the team introduced Webflow to let marketing produce its own content. The author describes inconsistent style matching and technical quality, along with engineering work to fix pages.
As engineers became more productive with Cursor, the team tried giving it directly to content creators. That approach remained brittle: an unfamiliar IDE exposed far more functionality than the task required, and users also needed to learn Git. The team then built its own browser-based sitebuilder with Cursor, reporting that the work took days rather than months.
The resulting application let content creators make pages through chat while embedding guardrails in the product. The author says tracking-pixel integration and matching the style guide worked automatically. Underneath the interface, a Git-based storage and versioning workflow allowed engineers to support, test and deploy the pages using their usual tools and methods. The content creators did not have to deal with that complexity.
The author presents the application as software the team intends to support and improve long-term, rather than a disposable prototype.
Who it's for: Software teams that want marketing staff to create pages within established styling and deployment practices.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Hacker News · ManuelKiessling
Frequently asked questions
Why was giving content creators Cursor insufficient?
The author says the IDE was overwhelming for people unfamiliar with IDEs, offered too many functions for this use case, and required explaining Git.
How could engineers support the resulting pages?
The sitebuilder used Git-based storage and versioning underneath, allowing engineers to support, test and deploy results with their preferred tools and methods.
More details
Remaining steps
- Embedded style and tracking guardrails above Git-based storage and versioning.
About this account
Cursor helped the engineering team build the browser application; content creators then used its focused chat interface.
Platform: Hacker News. Attribution: https://news.ycombinator.com/item?id=46896806. Prompt: Suggested (written by Agents In Use, not the author's). Sourced by the Agents In Use pipeline.
Credit: ManuelKiessling on Hacker News
Source published 5 Feb 2026
Source checked 14 Oct 2026
Tools and topics
Cursor · Webflow · Git · sitebuilder-webapp
Landing pages · Internal tooling · Git workflows
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.