The studio lukacapital.co is run from: click a sentence on the real page, rewrite it in both languages, and it is live on the next request.
Luka Capital's site is run from here. I built the studio at Authect so the firm's own team can change what a visitor reads, in Spanish and English, without a developer and without a deploy.
It lives in the same application as the public site, behind a sign-in. Thirteen screens cover every sentence on the site, the search metadata of each page, the property catalogue, the team, testimonials and partners, the firm's contact details, the accounts, and a history of who changed what.
- 1,051editable strings in each language
- 13screens behind the sign-in
- 20server actions
- 2languages, edited side by side
The live editor
Click the sentence
The studio loads the real page in a frame. In edit mode every editable sentence is outlined, and a click on one selects it.
Both languages at once
Spanish and English open side by side, with a reset that restores the original wording.
Live on save
A save writes one row and drops the cached wording. The next request renders the new sentence. Nothing is rebuilt and nothing is deployed.
The frame is not trusted
The page reports a selection to the studio by message, and the studio checks where that message came from before it acts on it.
The content layer
Overrides over the shipped copy
The site's wording ships in the code as two dictionaries. An edit is stored as an override against the same key and merged over them when a page is rendered.
The database is optional
If it cannot be reached, visitors get the wording that shipped. A fault in the studio cannot take the site down.
All of it, searchable
The Copy screen lists every string in 37 groups, searchable by wording or by key. Strings that carry variables are flagged so the placeholders survive an edit.
Search metadata is copy too
Each page's search title and description are strings like any other, edited in both languages. The site-wide defaults have a screen of their own.
Orphans are surfaced
When a developer renames or removes a key, the edits saved against it are listed so they can be cleared.
Catalogue and collections
Curation over a live feed
Listings arrive read-only from the firm's property-management system. The studio decides what the site does with each one: feature it on the home page, mark it off-market, hide it, or set its place in the order.
A voice per listing
Each property can carry its own subtitle, location label and description in both languages. An empty field falls back to the feed.
Optimistic toggles
A toggle changes on screen at once and is rolled back if the server refuses it.
Team, testimonials and partners
Three collections share one manager: add, edit, drag to reorder, publish or hide, and upload an image.
Access
Two roles
Administrators manage accounts. Editors change content and nothing else, and the screens they cannot use are not shown to them.
Checked on the server, every time
The sign-in is the first gate, not the only one. Every action that writes checks the session and the role again before it touches the database.
A record of every change
Edits to copy, curation and settings are stamped with who made them and when. The history screen lists the latest.
Luka Capital brand identity by Twineich Branding Studio.
