If you've purchased a Webflow template that includes CMS functionality and you wish to remove the CMS and use basic hosting instead, I'm afraid it's not possible to directly remove the CMS from a template. The CMS functionality is built into the template design and structure.
Deleting the collections alone will not disable the CMS functionality because the CMS requires a specific structure and framework that is woven into the template. Removing the collections may cause errors or broken links throughout the site.
However, if you don't wish to use the CMS features and would like to use basic hosting instead, there are a few workarounds you can consider:
1. Remove the dynamic content: If you don't want to use CMS collections, you can delete or modify the dynamic content elements used for displaying CMS data, like dynamic lists, dynamic templates, or dynamic embeds. You can replace them with static elements or manually update the content.
2. Disconnect the CMS collections: If the template is using CMS collections that are linked to dynamic templates or pages, you can disconnect those dynamic elements from the collections. To do this, select the dynamic element and navigate to the settings panel on the right-hand side. In the "Collection" dropdown, select "None".
3. Modify the template structure: If you have a good understanding of HTML, CSS, and Webflow's template structure, you can manually remove or modify the CMS-related code snippets from the template's code. This includes removing collection fields, collection lists, and any other dynamic elements that rely on the CMS.
Keep in mind that modifying the template structure or removing CMS-related code snippets requires advanced technical skills. If you're not comfortable with these changes, it's always recommended to consult with a developer or reach out to Webflow's support for further assistance.
Additionally, it's worth mentioning that using the CMS can offer great benefits for managing and updating content on your website efficiently. If you find that you may need the CMS functionality in the future, it might be worth exploring how it can benefit your site rather than completely removing it.