Static websites

Understand the files you publish and the process that keeps them current.

A static publishing workflow benefits from a clear distinction between authoring tools and the website delivered to visitors. The article below follows that handoff, including folders, relative resources, clean page paths, and the review that belongs before a release.

• Keep a complete copy of each published release.
• Test directory pages and their shared assets together.

Choose a guide from this collection and use its questions to examine a project you can describe in concrete terms. Write down the decision you need to make, the result you will inspect, and the person who will maintain the work. For a wider view of this subject, continue with the static websites page. You can return to the Lab’s category collections when you want to follow the next part of the workflow.

Explore static websites or browse all Low Code Studio Lab articles.