SiteCake is an editing layer for suitable HTML websites. This guide helps you check hosting compatibility, choose an appropriate installation method and verify the first usable site. The application, its extensions and any commercial license remain separate from the hosting account.
IN THIS ARTICLE
01 Check SiteCake and hosting requirements
Confirm the current supported SiteCake package and the compatibility of the HTML site you want to edit. Back up the existing website before adding an editing layer to its files.
Use the project's current supported release information and the requirements shown for the package you select. If Softaculous offers an older or unsuitable build, follow the current vendor installation process or ask us to confirm a suitable environment. Do not enable an unsupported PHP runtime simply to reproduce an old tutorial.
02 Prepare the existing website for Sitecake
- Make a complete copy of the existing HTML site and work in an isolated test location. Check the current PHP requirements and licensing for the intended deployment.
- Mark only the HTML regions that should be editable with the documented
sc-contentclass. Do not nest editable regions. - Obtain the current package from Sitecake and upload its editor files beside the website according to the vendor instructions. No separate database is required.
- Open the supplied editor entry point over HTTPS and replace the default password before allowing public access to the management interface.
- Edit and publish one text block and one image, then compare the saved page with the original template. Keep scripts, navigation and application code outside the editable region unless explicitly supported.
Example: a small editable HTML region
<div class="sc-content">
<h2>Our services</h2>
<p>Website maintenance and technical support.</p>
</div>
The class marks this block for editing. It does not make the entire website an application or guarantee that an arbitrary PHP template is safe to modify.
03 Configure SiteCake for first use
Follow the publisher's integration instructions for the selected release, set administrator access and identify the intended editable areas. Keep changes in a copy until the editing behavior is verified.
Confirm the expected result
Edit a small text block and image, then inspect the saved HTML and public page. Confirm that scripts, styles and non-editable portions of the website remain intact.
04 Maintain and troubleshoot SiteCake
A successful installation does not make every arbitrary HTML template safely editable. Test the actual template and keep a copy of the original files before allowing routine content changes.
Keep files and data together in your recovery plan, test application updates in a copy when practical, and review logs after deployment. If installation fails, record the exact error, selected application/PHP versions and destination path before retrying.
A common question
Does a successful installation mean the whole application is ready for customers?
No. Verify the public content, permissions, forms or notifications and the features you actually use. An installer success message confirms provisioning, not your complete business workflow.