Grav understands that any integer value followed by a period will be solely for ordering, and is removed internally in the system. For example, if you have a folder named 01.home, Grav will treat this folder as home, but will ensure that with default ordering, it comes before 02.blog.

/user └── /pages ├── /01.home │ ├── /_header │ ├── /_features │ ├── /_body ├── /02.blog │ ├── /blog-item-1 │ ├── /blog-item-2 │ ├── /blog-item-3 │ ├── /blog-item-4 │ └── /blog-item-5 ├── /03.about-us └── /error Your site must have an entry-point so that it knows where to go when you point your browser to the root of your site. For example if you were to enter http://yoursite.com in your browser, by default Grav expects an alias home/, but you can override the home-location by changing the home.alias option in the Grav configuration file.

Modules are identified by an underscore (_) before the folder name. This is a special folder type that is intended to be used only with modular content. These are not routable and not visible in the navigation. An example of a modular page setup would be a folder such as user/pages/01.home. Home is configured as a modular page that would contain a collection of modules, and would be constructed from the _header, _features, and _body folders within the home folder.

The textual name of each folder defaults to the slug that the system uses as part of the URL. For example if you have a folder such as /user/pages/02.blog, the slug for this page would default to blog, and the full URL would be http://yoursite.com/blog. A blog item page, located in /user/pages/02.blog/blog-item-5 would be accessible via http://yoursite.com/blog/blog-item-5.

If no number is provided as a prefix of the folder name, the page is considered to be invisible, and will not show up in the navigation. An example of this would be the error page in the above folder-structure.

This can actually be overridden in the page itself by setting the visible parameter in the he