Pages
Cofoundry has content management features that let you create and manage your website pages dynamically. Pages use a flexible templating system that augments standard asp.net razor view files with modular content regions to provide you with fine grained control over your code and content.
To learn more about creating templates see the page templates documentation.
Pages and directories are created and managed admin panel in the pages/directories sections.
All pages need to be parented to a directory and for most pages this will be the root directory. Directories aren't navigable and you'll need a page at the directory root if you want to display anything at the directory root.
Pages are pretty self explanatory. Each page uses a template which defines the sections of content that users can edit. Guidance on editing content is in the next section of this document.
Pages are great for creating content represented by a single page (e.g a home page, about page or contact page), but for data used in multiple pages or as listable content (e.g. blog posts, products or store locations) you're better off creating a Custom Entity.
A special Custom Entity Details page type can be used to display a page for each custom entity type using a configurable routing rule. Check out the documentation for more information.
While pages and directories can be managed in their sections of the admin panel, editing the content of the page is done inline while browsing the page. We refer to this inline editor as the Visual Editor. To show the visual editor simply browse to the page you want to edit while logged in and click on the Edit Draft button to start editing.
You build up page content by using Sections and Modules. Your template will define areas of the page that can contain managed content, these are Sections and each section can contain 0 or more Modules.
When you define section in your template you can specify whether the section allows multiple modules or not and you can restrict the types of modules that a user can place within a section. We have some built-in module types, but you can easily create your own - a module is just a razor view file and a .Net class.
For more detail on this see the documentation for Page Templates and Page Module Types.
Note that there is an issue with using Visual Studio's Browser Link feature while using the visual editor. See issue 62
Cofoundry supports for a wide range of content management styles. If you want to give content editors more flexibility you can create more generic templates that allow a wide range of building-block style modules, or if you have a very specific design you can restrict module choice so content editors can't break the design of the site. If you trust your content editors and you want to allow total freedom you can also just place a single section that allows the raw html module.