Deployment and Backend Services
Prepare your website for upload, understand which features need backend services, and learn how to update your deployed files safely.
Upload the finished website
Section titled “Upload the finished website”Build the source if you use that workflow, then upload only the contents of dist/ to your static web host. Keep HTML pages and their asset folders together. Do not upload Source/, node_modules/ or your development configuration.
The finished website does not need WordPress, PHP, Nunjucks, Tailwind or Node.js installed on the production host. It is served as HTML, CSS, JavaScript and local assets.
If you publish under a subdirectory, preserve relative paths and check internal navigation and asset URLs on the deployed site. Configure your host to serve 404-page-not-found.html for missing pages with an HTTP 404 status; uploading the file alone does not configure error handling.
Connect backend services
Section titled “Connect backend services”The template does not include an email server, payment processor, order system, user authentication, password reset or comments backend. Forms, checkout and account screens are front-end examples. Contact, newsletter and comment forms provide local validation without sending or saving submissions. The demo cart stores quantities and totals in browser session storage; it is not an order system. A fresh session starts with one sample product. To reset it, remove naturalife-template-cart-v1 from session storage in your browser’s developer tools, or open a new browser session. Blog search, pagination, product sorting and filtering use the included demo data; they do not query a database.
Before accepting real submissions, payments or account registrations, integrate the appropriate backend or service and replace the sample handlers and endpoints. Validate submissions on the server as well: client-side validation alone is not a backend. Product troubleshooting support does not include building custom backend integrations.
Update an existing website
Section titled “Update an existing website”- Back up your deployed site and customized source.
- Compare the new release with your customized source and merge its changes instead of overwriting your files.
- Run
npm ciinSource/with the supplied lockfile. Keep the package version and its lockfile together. - Run
npm run build, thennpm run preview. - Check your pages, images, navigation, forms, connected services and mobile layouts.
- Upload the contents of
dist/.
Get help
Section titled “Get help”See Troubleshooting for common setup issues. For account, download or eligible product support, open your RT-Themes dashboard.
Get all RT-Themes designs, updates and support with a single Club license.
Join the Club