Structa Cloud Structa Cloud

Content

Designing bilingual journeys without duplication

A practical way to keep Arabic and English content aligned while letting each language sound natural.

Content 5 min read ← All posts

Every interactive region on a marketing site is a trade: fetch JSON and render it client-side, or fetch HTML and let the server do the rendering. HTMX picks the second, and it is the right default for content sites.

The API contract tax

JSON APIs force you to maintain a schema, a serializer, and a client-side renderer that all agree. Add a field and you touch three files. Streaming HTML removes the decoder entirely — the response is the UI.

Where it shines

Our contact form, newsletter subscribe, and server-time demo all swap small HTML fragments into place. The Django view returns a finished fragment; HTMX does the swap. There is no frontend state to desync.

Half the frontend state we used to maintain simply no longer exists.

Comments

A useful first release beats a noisy roadmap

We start with the customer journey, launch a focused slice, and leave your team with the content and tools to keep improving it.

ready when you are · text/html