Frequently asked questions

What we are asked most about how a page is planned, built and maintained.

Project

Where does a project start?

With a conversation about your audience, what they need to know and what you want them to do next. The page’s sections and the metrics that tell whether it worked come out of that conversation.

Do I need the copy ready?

No. The copy is written alongside the structure and kept in data files apart from the layout — so it can be revised later without touching the components.

Technology

Why are the pages static?

Because pre-rendered HTML arrives faster, does not need JavaScript to appear and is read in full by search engines and AI tools. When a value has to be current, only that part is fetched live.

Can the page have more than one language?

Yes. Each language ships the same page tree under its own prefix, and each page tells search engines where its versions in the other languages are.

Can the content come from a system I already have?

Yes. Data can be read from an API when the site is published. If the API does not answer, publishing fails with a clear message instead of putting an empty page online.

Content

Can there be a blog next to the page?

Yes. Posts are Markdown files, one per language, validated at publish time: a post with no title, date or language is not published.

Still have a question?

Write to us and we will reply within one business day.

Talk to us