MakeSite combines a content editor with static website publishing. Text, images, and supported sections are edited through the browser. MakeSite prepares the pages for publication and handles hosting and HTTPS.
The standard editing, review, and publishing workflow does not require writing HTML, CSS, or JavaScript. Connecting a custom domain still requires access to its domain settings.
How static publishing works
A static website delivers pages prepared before a visitor requests them. The published pages do not need a content management system or database to assemble each response.
Static publishing still permits changes. The editor manages the content; publication updates the files served to visitors. This separates draft work from the live website and removes the need to maintain a separate CMS installation or its plugins.
From editor to published website
- Create a site. Sign in through DutchBSD Workspace and select an available starting design.
- Edit the content. Enter business details, replace text and images, and configure the sections supported by the design.
- Review the result. Check the private preview, including navigation, contact details, and the layout on desktop and mobile. MakeSite prepares the website during review.
- Arrange publication. Select a paid plan and a MakeSite address. A custom domain can also be connected by adding the DNS records shown in the publishing screen.
- Publish the reviewed version. Use the publication controls to put the reviewed site online. MakeSite handles the hosting and HTTPS setup.
Later edits follow the same review and publication process. Draft changes do not alter the live website. The previous version remains online until an update is published successfully.
Suitable uses
Static publishing suits websites whose main purpose is to present information: services, business details, professional profiles, opening hours, and contact information. A small business or independent practice can maintain this content through the editor.
The available design determines the page structure and supported sections. Check that structure against the required content before committing to a site. Editing supplied content fields does not provide unrestricted control over every layout detail.
What requires additional functionality
A static website alone does not process shopping carts, manage appointment availability, or provide customer accounts. Those requirements need an appropriate service or application. A link to an external booking service is different from an integrated booking system.
Similarly, a browser editor for an existing design does not replace custom development for arbitrary layouts or application behavior. Confirm any essential integration or feature before selecting a website builder.
For a broader set of built-in business tools, the MakeSite and Wix comparison explains the differences in scope.
Hosting, domains, and cost
MakeSite costs €6 per month, including VAT, per published website. Hosting and HTTPS are included. A paid plan is required for publication and custom-domain use.
Domain registration and renewal are separate. An existing domain remains with its provider. Connecting it requires changes to DNS records in that provider's settings; MakeSite displays the required values. DNS verification and HTTPS preparation can take time.
Performance and search visibility
Static output reduces the work required to deliver each page. Loading performance also depends on images, fonts, scripts, and the content added to the site. Static publishing alone does not guarantee a particular speed score or search ranking.
Use clear page titles, useful content, descriptive links, and images sized for their purpose. Review the published result after an update. The MakeSite overview describes the included editing and publishing features.
