Routing in Slayte CMS
Slayte CMS uses a clean, file-based routing system that eliminates `.php` extensions and query strings from your public URLs.
📌 Clean URLs by Default
All content pages, including articles and documentation, are accessible using human-readable slugs:
/articles/my-first-post
→articles/my-first-post.php
/docs/routing
→docs/routing.php
/about
→about.php
🚫 No Query Strings or Extensions
We’ve eliminated clunky and unprofessional routes like:
/article.php?id=42
/docs/routing.html
These not only expose backend structure but also harm SEO and readability.
⚙️ How It Works (Apache Example)
Slayte CMS uses a simple .htaccess
rule to rewrite clean slugs to their `.php` equivalents:
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME}.php -f
RewriteRule ^(.+?)/?$ $1.php [L]
This means your file docs/routing.php
is reachable at /docs/routing
with or without a trailing slash.
🔒 Secure and Predictable
By keeping your routing under control and file-based, Slayte CMS gives you full visibility into how your URLs are handled. No ambiguous routing files. No broken plugin slugs. Just direct access.
Note: You can organize routes logically using folders like
← Back to Installation Guide
/docs/
, /articles/
, or /admin/
without any configuration needed.