{"id":18854,"date":"2026-04-24T19:24:10","date_gmt":"2026-04-24T19:24:10","guid":{"rendered":"https:\/\/truehost.com\/support\/?post_type=docs&#038;p=18854"},"modified":"2026-04-24T19:25:31","modified_gmt":"2026-04-24T19:25:31","password":"","slug":"how-to-identify-a-website-framework-by-looking-at-its-file-structure","status":"publish","type":"docs","link":"https:\/\/truehost.com\/support\/knowledge-base\/how-to-identify-a-website-framework-by-looking-at-its-file-structure\/","title":{"rendered":"How to Identify a Website Framework by Looking at Its File Structure"},"content":{"rendered":"\n<p>When you gain access to a website\u2019s source code\u2014whether via cPanel, SSH, FTP, GitHub, or a server directory\u2014the file structure alone can often tell you what framework or stack the application is built on.<\/p>\n\n\n\n<p>This guide provides a practical, sysadmin-oriented breakdown of how to recognize common web frameworks simply by inspecting directory layout and key files.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How to Identify a Node.js Application<\/h2>\n\n\n\n<p>A Node.js backend application has several unmistakable indicators.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Key Files to Look<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>package.json\n\npackage-lock.json or yarn.lock\n\nnode_modules\/\n\nserver.js, app.js, or index.js<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Typical Structure<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>project-root\/\n\u2502\n\u251c\u2500\u2500 node_modules\/\n\u251c\u2500\u2500 package.json\n\u251c\u2500\u2500 package-lock.json\n\u251c\u2500\u2500 app.js \/ server.js \/ index.js\n\u251c\u2500\u2500 routes\/\n\u251c\u2500\u2500 controllers\/\n\u2514\u2500\u2500 public\/<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">How to Confirm<\/h3>\n\n\n\n<p>The presence of package.json is the strongest indicator.<\/p>\n\n\n\n<p>Open package.json and check:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>\"dependencies\": {\n    \"express\": \"^4.18.0\"\n}<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Identifying a <strong>React<\/strong> Application<\/h2>\n\n\n\n<p>React is primarily a frontend framework. It can exist standalone or inside a full-stack app.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Key Files<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>package.json<\/code><\/li>\n\n\n\n<li><code>src\/<\/code><\/li>\n\n\n\n<li><code>public\/<\/code><\/li>\n\n\n\n<li><code>node_modules\/<\/code><\/li>\n\n\n\n<li><code>vite.config.js<\/code> or <code>webpack.config.js<\/code><\/li>\n\n\n\n<li><code>next.config.js<\/code> (if using Next.js)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Typical React (Vite or CRA) Structure<\/h3>\n\n\n\n<p>project-root\/<br>\u2502<br>\u251c\u2500\u2500 node_modules\/<br>\u251c\u2500\u2500 public\/<br>\u251c\u2500\u2500 src\/<br>\u2502 \u251c\u2500\u2500 App.jsx<br>\u2502 \u251c\u2500\u2500 main.jsx<br>\u2502 \u2514\u2500\u2500 components\/<br>\u251c\u2500\u2500 package.json<br>\u2514\u2500\u2500 vite.config.js<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How to Confirm<\/h3>\n\n\n\n<p>Open <code>package.json<\/code>:<\/p>\n\n\n\n<p>&#8220;dependencies&#8221;: {<br>&#8220;react&#8221;: &#8220;^18.0.0&#8221;,<br>&#8220;react-dom&#8221;: &#8220;^18.0.0&#8221;<br>}<\/p>\n\n\n\n<p>If you see:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>next.config.js<\/code> \u2192 it\u2019s likely a Next.js React framework.<\/li>\n\n\n\n<li><code>.jsx<\/code> or <code>.tsx<\/code> files \u2192 React-based frontend.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Identifying a <strong>Django<\/strong> Application (Python)<\/h2>\n\n\n\n<p>Django has a very distinctive structure.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Key Files<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>manage.py<\/code><\/li>\n\n\n\n<li><code>settings.py<\/code><\/li>\n\n\n\n<li><code>urls.py<\/code><\/li>\n\n\n\n<li><code>wsgi.py<\/code> or <code>asgi.py<\/code><\/li>\n\n\n\n<li><code>requirements.txt<\/code><\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Typical Structure<\/h3>\n\n\n\n<p>project-root\/<br>\u2502<br>\u251c\u2500\u2500 manage.py<br>\u251c\u2500\u2500 requirements.txt<br>\u251c\u2500\u2500 projectname\/<br>\u2502 \u251c\u2500\u2500 <strong>init<\/strong>.py<br>\u2502 \u251c\u2500\u2500 settings.py<br>\u2502 \u251c\u2500\u2500 urls.py<br>\u2502 \u251c\u2500\u2500 wsgi.py<br>\u2502 \u2514\u2500\u2500 asgi.py<br>\u2514\u2500\u2500 appname\/<br>\u251c\u2500\u2500 models.py<br>\u251c\u2500\u2500 views.py<br>\u2514\u2500\u2500 admin.py<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How to Confirm<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>manage.py<\/code> is the strongest giveaway.<\/li>\n\n\n\n<li><code>settings.py<\/code> and <code>urls.py<\/code> confirm Django.<\/li>\n\n\n\n<li>Python virtual environment folder like <code>venv\/<\/code> may also exist.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Identifying a <strong>Flask<\/strong> Application (Python)<\/h2>\n\n\n\n<p>Flask is lightweight and less opinionated than Django.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Key Files<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>app.py<\/code> or <code>main.py<\/code><\/li>\n\n\n\n<li><code>requirements.txt<\/code><\/li>\n\n\n\n<li><code>venv\/<\/code><\/li>\n\n\n\n<li><code>templates\/<\/code><\/li>\n\n\n\n<li><code>static\/<\/code><\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Typical Structure<\/h3>\n\n\n\n<p>project-root\/<br>\u2502<br>\u251c\u2500\u2500 app.py<br>\u251c\u2500\u2500 requirements.txt<br>\u251c\u2500\u2500 venv\/<br>\u251c\u2500\u2500 templates\/<br>\u2514\u2500\u2500 static\/<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How to Confirm<\/h3>\n\n\n\n<p>Open <code>app.py<\/code>:<\/p>\n\n\n\n<p>from flask import Flask<br>app = Flask(<strong>name<\/strong>)<\/p>\n\n\n\n<p>Flask apps are usually simpler than Django\u2014no <code>manage.py<\/code>, no project-level settings folder.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Identifying a <strong>WordPress<\/strong> Website<\/h2>\n\n\n\n<p>WordPress has one of the most recognizable structures.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Key Folders<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>wp-admin\/<\/code><\/li>\n\n\n\n<li><code>wp-content\/<\/code><\/li>\n\n\n\n<li><code>wp-includes\/<\/code><\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Key Files<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>wp-config.php<\/code><\/li>\n\n\n\n<li><code>wp-load.php<\/code><\/li>\n\n\n\n<li><code>index.php<\/code><\/li>\n\n\n\n<li><code>.htaccess<\/code><\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Typical Structure<\/h3>\n\n\n\n<p>public_html\/<br>\u2502<br>\u251c\u2500\u2500 wp-admin\/<br>\u251c\u2500\u2500 wp-content\/<br>\u2502 \u251c\u2500\u2500 themes\/<br>\u2502 \u251c\u2500\u2500 plugins\/<br>\u251c\u2500\u2500 wp-includes\/<br>\u251c\u2500\u2500 wp-config.php<br>\u2514\u2500\u2500 index.php<\/p>\n\n\n\n<p>If these folders exist, it is 100% WordPress.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Identifying a Plain <strong>PHP Website<\/strong><\/h2>\n\n\n\n<p>A basic PHP site without frameworks looks different.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Indicators<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Multiple <code>.php<\/code> files in root<\/li>\n\n\n\n<li>No <code>vendor\/<\/code> folder<\/li>\n\n\n\n<li>No <code>composer.json<\/code><\/li>\n\n\n\n<li>No structured MVC folders<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Example Structure<\/h3>\n\n\n\n<p>public_html\/<br>\u2502<br>\u251c\u2500\u2500 index.php<br>\u251c\u2500\u2500 about.php<br>\u251c\u2500\u2500 contact.php<br>\u251c\u2500\u2500 header.php<br>\u2514\u2500\u2500 footer.php<\/p>\n\n\n\n<p>This indicates procedural or custom PHP.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Identifying a <strong>Laravel<\/strong> Application (PHP Framework)<\/h2>\n\n\n\n<p>Laravel has a very distinctive structure.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Key Files &amp; Folders<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>artisan<\/code><\/li>\n\n\n\n<li><code>composer.json<\/code><\/li>\n\n\n\n<li><code>vendor\/<\/code><\/li>\n\n\n\n<li><code>app\/<\/code><\/li>\n\n\n\n<li><code>routes\/<\/code><\/li>\n\n\n\n<li><code>storage\/<\/code><\/li>\n\n\n\n<li><code>bootstrap\/<\/code><\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Typical Structure<\/h3>\n\n\n\n<p>project-root\/<br>\u2502<br>\u251c\u2500\u2500 app\/<br>\u251c\u2500\u2500 bootstrap\/<br>\u251c\u2500\u2500 config\/<br>\u251c\u2500\u2500 database\/<br>\u251c\u2500\u2500 public\/<br>\u251c\u2500\u2500 resources\/<br>\u251c\u2500\u2500 routes\/<br>\u251c\u2500\u2500 storage\/<br>\u251c\u2500\u2500 vendor\/<br>\u251c\u2500\u2500 artisan<br>\u2514\u2500\u2500 composer.json<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How to Confirm<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Presence of <code>artisan<\/code> file is decisive.<\/li>\n\n\n\n<li><code>composer.json<\/code> contains:<\/li>\n<\/ul>\n\n\n\n<p>&#8220;laravel\/framework&#8221;: &#8220;^10.0&#8221;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>routes\/web.php<\/code> exists.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Identifying Framework via <code>composer.json<\/code> (PHP Ecosystem)<\/h2>\n\n\n\n<p>If you see:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>composer.json<\/code><\/li>\n\n\n\n<li><code>vendor\/<\/code><\/li>\n<\/ul>\n\n\n\n<p>Open <code>composer.json<\/code>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Examples:<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>\"laravel\/framework\"<\/code> \u2192 Laravel<\/li>\n\n\n\n<li><code>\"symfony\/symfony\"<\/code> \u2192 Symfony<\/li>\n\n\n\n<li><code>\"codeigniter\/framework\"<\/code> \u2192 CodeIgniter<\/li>\n<\/ul>\n\n\n\n<p>Composer-managed PHP projects always include <code>vendor\/<\/code>.<\/p>\n\n\n\n<p>Sometimes framework clues appear in:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>.htaccess<\/code><\/li>\n\n\n\n<li><code>nginx.conf<\/code><\/li>\n\n\n\n<li><code>web.config<\/code><\/li>\n<\/ul>\n\n\n\n<p>For example:<\/p>\n\n\n\n<p>Laravel <code>.htaccess<\/code> typically routes all requests to <code>public\/index.php<\/code>.<\/p>\n\n\n\n<p>Node.js deployments may have:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>ecosystem.config.js<\/code> (PM2)<\/li>\n\n\n\n<li><code>server.js<\/code><\/li>\n<\/ul>\n\n\n\n<p>Django deployments may have:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>gunicorn.conf.py<\/code><\/li>\n\n\n\n<li><code>uwsgi.ini<\/code><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">In Conclusion<\/h2>\n\n\n\n<p>As a technical support professional, understanding the framework a website is built on can significantly reduce troubleshooting time. It helps you quickly locate relevant error logs, identify database connections, recognize critical system files, and apply framework-specific fixes with confidence. Instead of relying on trial and error, you can diagnose issues faster, resolve incidents more efficiently, and provide more accurate support to clients.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When you gain access to a website\u2019s source code\u2014whether via cPanel, SSH, FTP, GitHub, or a server directory\u2014the file structure alone can often tell you what framework or stack the application is built on. This guide provides a practical, sysadmin-oriented breakdown of how to recognize common web frameworks simply by inspecting directory layout and key [&hellip;]<\/p>\n","protected":false},"author":28,"featured_media":0,"comment_status":"open","ping_status":"closed","template":"","meta":{"_eb_attr":"","_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"footnotes":""},"doc_category":[1830],"doc_tag":[],"class_list":["post-18854","docs","type-docs","status-publish","hentry","doc_category-hosting"],"year_month":"2026-07","word_count":650,"total_views":0,"reactions":{"happy":0,"normal":0,"sad":0},"author_info":{"name":"Francis O.","author_nicename":"francis","author_url":"https:\/\/truehost.com\/support\/author\/francis\/"},"doc_category_info":[{"term_name":"Hosting","term_url":"https:\/\/truehost.com\/support\/docs-category\/hosting\/"}],"doc_tag_info":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.0 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>How to Identify a Website Framework by Looking at Its File Structure -<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/truehost.com\/support\/knowledge-base\/how-to-identify-a-website-framework-by-looking-at-its-file-structure\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to Identify a Website Framework by Looking at Its File Structure -\" \/>\n<meta property=\"og:description\" content=\"When you gain access to a website\u2019s source code\u2014whether via cPanel, SSH, FTP, GitHub, or a server directory\u2014the file structure alone can often tell you what framework or stack the application is built on. This guide provides a practical, sysadmin-oriented breakdown of how to recognize common web frameworks simply by inspecting directory layout and key [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/truehost.com\/support\/knowledge-base\/how-to-identify-a-website-framework-by-looking-at-its-file-structure\/\" \/>\n<meta property=\"article:modified_time\" content=\"2026-04-24T19:25:31+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/truehost.com\\\/support\\\/knowledge-base\\\/how-to-identify-a-website-framework-by-looking-at-its-file-structure\\\/\",\"url\":\"https:\\\/\\\/truehost.com\\\/support\\\/knowledge-base\\\/how-to-identify-a-website-framework-by-looking-at-its-file-structure\\\/\",\"name\":\"How to Identify a Website Framework by Looking at Its File Structure -\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/truehost.com\\\/support\\\/#website\"},\"datePublished\":\"2026-04-24T19:24:10+00:00\",\"dateModified\":\"2026-04-24T19:25:31+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/truehost.com\\\/support\\\/knowledge-base\\\/how-to-identify-a-website-framework-by-looking-at-its-file-structure\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/truehost.com\\\/support\\\/knowledge-base\\\/how-to-identify-a-website-framework-by-looking-at-its-file-structure\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/truehost.com\\\/support\\\/knowledge-base\\\/how-to-identify-a-website-framework-by-looking-at-its-file-structure\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/truehost.com\\\/support\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Identify a Website Framework by Looking at Its File Structure\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/truehost.com\\\/support\\\/#website\",\"url\":\"https:\\\/\\\/truehost.com\\\/support\\\/\",\"name\":\"\",\"description\":\"Help In a Click\",\"publisher\":{\"@id\":\"https:\\\/\\\/truehost.com\\\/support\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/truehost.com\\\/support\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/truehost.com\\\/support\\\/#organization\",\"name\":\"Truehost Kenya\",\"url\":\"https:\\\/\\\/truehost.com\\\/support\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/truehost.com\\\/support\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/truehost.com\\\/support\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/cropped-image_2026-04-16_174808866.png\",\"contentUrl\":\"https:\\\/\\\/truehost.com\\\/support\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/cropped-image_2026-04-16_174808866.png\",\"width\":240,\"height\":48,\"caption\":\"Truehost Kenya\"},\"image\":{\"@id\":\"https:\\\/\\\/truehost.com\\\/support\\\/#\\\/schema\\\/logo\\\/image\\\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"How to Identify a Website Framework by Looking at Its File Structure -","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/truehost.com\/support\/knowledge-base\/how-to-identify-a-website-framework-by-looking-at-its-file-structure\/","og_locale":"en_US","og_type":"article","og_title":"How to Identify a Website Framework by Looking at Its File Structure -","og_description":"When you gain access to a website\u2019s source code\u2014whether via cPanel, SSH, FTP, GitHub, or a server directory\u2014the file structure alone can often tell you what framework or stack the application is built on. This guide provides a practical, sysadmin-oriented breakdown of how to recognize common web frameworks simply by inspecting directory layout and key [&hellip;]","og_url":"https:\/\/truehost.com\/support\/knowledge-base\/how-to-identify-a-website-framework-by-looking-at-its-file-structure\/","article_modified_time":"2026-04-24T19:25:31+00:00","twitter_card":"summary_large_image","twitter_misc":{"Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/truehost.com\/support\/knowledge-base\/how-to-identify-a-website-framework-by-looking-at-its-file-structure\/","url":"https:\/\/truehost.com\/support\/knowledge-base\/how-to-identify-a-website-framework-by-looking-at-its-file-structure\/","name":"How to Identify a Website Framework by Looking at Its File Structure -","isPartOf":{"@id":"https:\/\/truehost.com\/support\/#website"},"datePublished":"2026-04-24T19:24:10+00:00","dateModified":"2026-04-24T19:25:31+00:00","breadcrumb":{"@id":"https:\/\/truehost.com\/support\/knowledge-base\/how-to-identify-a-website-framework-by-looking-at-its-file-structure\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/truehost.com\/support\/knowledge-base\/how-to-identify-a-website-framework-by-looking-at-its-file-structure\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/truehost.com\/support\/knowledge-base\/how-to-identify-a-website-framework-by-looking-at-its-file-structure\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/truehost.com\/support\/"},{"@type":"ListItem","position":2,"name":"How to Identify a Website Framework by Looking at Its File Structure"}]},{"@type":"WebSite","@id":"https:\/\/truehost.com\/support\/#website","url":"https:\/\/truehost.com\/support\/","name":"","description":"Help In a Click","publisher":{"@id":"https:\/\/truehost.com\/support\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/truehost.com\/support\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/truehost.com\/support\/#organization","name":"Truehost Kenya","url":"https:\/\/truehost.com\/support\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/truehost.com\/support\/#\/schema\/logo\/image\/","url":"https:\/\/truehost.com\/support\/wp-content\/uploads\/2026\/04\/cropped-image_2026-04-16_174808866.png","contentUrl":"https:\/\/truehost.com\/support\/wp-content\/uploads\/2026\/04\/cropped-image_2026-04-16_174808866.png","width":240,"height":48,"caption":"Truehost Kenya"},"image":{"@id":"https:\/\/truehost.com\/support\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/truehost.com\/support\/wp-json\/wp\/v2\/docs\/18854","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/truehost.com\/support\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/truehost.com\/support\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/truehost.com\/support\/wp-json\/wp\/v2\/users\/28"}],"replies":[{"embeddable":true,"href":"https:\/\/truehost.com\/support\/wp-json\/wp\/v2\/comments?post=18854"}],"version-history":[{"count":6,"href":"https:\/\/truehost.com\/support\/wp-json\/wp\/v2\/docs\/18854\/revisions"}],"predecessor-version":[{"id":19026,"href":"https:\/\/truehost.com\/support\/wp-json\/wp\/v2\/docs\/18854\/revisions\/19026"}],"wp:attachment":[{"href":"https:\/\/truehost.com\/support\/wp-json\/wp\/v2\/media?parent=18854"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/truehost.com\/support\/wp-json\/wp\/v2\/doc_category?post=18854"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/truehost.com\/support\/wp-json\/wp\/v2\/doc_tag?post=18854"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}