Repo Pages

Purpose and Concept

The Repo Pages module is a solution to avoid putting Basic Pages (i.e. "About Us" or "Privacy Policy" types of pages) in the database - but rather store them in the file-system, where they can be tracked under a version-control system.

This concept works by you choosing a directory within the Drupal application, say sites/all/pages/, and declaring that all *.page.php files shall be perceived as a page to be used on the site.
For example:

• Lets say you create a file located at sites/all/pages/about-us.page.php
  The contents of that file will be displayed for the page located at http://your-website.com/about-us
• Lets say you create a file located at sites/all/pages/about/our-partners.page.php
  The contents of that file will be displayed for the page located at http://your-website.com/about/our-partners

Advantages

This gives developers many advantages such as:

• easier migration/deployments - Since these pages live on the file-system and not stored in nodes, they can be migrated into another environment (i.e. deployed to your production environment) easily - through a tarball for example (or however else you deploy your application-code)
• version control - Since these pages are stored in the file-system, they can easily be placed under version-control, which allows developers to push/pull these pages to each other through Git/SVN/etc.
• better organization - @TODO
• grep - It's much easier to find code in a file versus finding code in a database.

How it works

@TODO

Functional Support

Unlike the 'Basic Page' content-type, which this module intends to depreciate, the page-files contain many real-world fields necessary for pages of websites. And again, because these files are in your repository, the values for these fields all get stored under version control.

• breadcrumbs - @TODO
• role restrictions (access rights) - @TODO
• css/javascript organization - @TODO