The basic requirements of content management are to persist arbitrary structured data associated with a group of urls,
allow that data to be edited through a UI, and to provide that data to be inserted into a page template.
This is done in a clean light-touch way in Lynicon by simply extending the Route class. Lynicon provides a generic
DataRoute class, which when used, manages retrieval of an arbitrarily (within certain specifications) typed data item and
provision of it to the controller's action method via model binding.
The most basic scenario of content routing would then be implemented like this:
- Create a content type TestContent
| Code Block | ||
|---|---|---|
| ||
public class TestContent : BaseContent
{
public string Title { get; set; }
} |
...
Lynicon comes with 2 standard kinds of persistence. The default, as above, serializes content types before storing them in a dedicated database table along with metadata. This is Content persistence. Another kind exists called Basic persistence which simply stores each field as a database field, this is described elsewhere.
...