> For the complete documentation index, see [llms.txt](https://docs.stylemixthemes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stylemixthemes.com/healthcoach-theme-documentation/getting-started/system-recommendations.md). # System Recommendations Since we develop only premium themes to meet the high standards and expectations of our customers, our HealthCoach theme is a bit more demanding on the resources than your average basic theme. The HealthCoach WordPress Theme is designed and developed for use with WordPress 5.2 or higher. The code was written to be backward compatible where possible, however, we recommend you use the current WP version when possible. If you are not using WordPress 4.8 or higher and can upgrade your site we recommend you do this before installation. We recommend the following system configuration for the best experience with the theme. * PHP version 7 or higher * MySQL version 5.6 or higher * WordPress version 5.2 or higher * HTTPS support * PHP Memory limit at least 256M * Upload max filesize at least 32M * Maximum Post Size at least 32M * Maximum Execution time 600 {% hint style="info" %} #### **To see how to view your System Status** [**click here**](https://docs.stylemixthemes.com/f-a-q/how-to-view-system-status)**.** {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.stylemixthemes.com/healthcoach-theme-documentation/getting-started/system-recommendations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.