plank/contentable

Create Dynamic pages using Polymorphic relationships and special Module classes

contentable's Issues

Basic Page model must be implemented

Description

This package should ship with the functionality to build arbitrary pages. Create a Page model that will act in this way. It should be able to have modules / content related to it and then display them in order.

This serves 2 functions,

1. to make the package feature complete and useable out of the box
2. to serve as an example as to how one might add modules to their own model

Main Contentable model needs to be implemented

Description

There should be a main Polymorphic relation model that allows for any arbitrary model to be related to any other special "module" class / model.

This could also start as only being able to be related to a specific Page model, and then expanded to be relatable to all models.

Renderables should allow for templates

Description

When a user calls a particular contentable to be rendered, each renderable type should be able to have a specific template defined and chosed for it. ie: the same module may render in 2 different ways but use the same content

Some basic modules should exist natively

Description

There should be some basic modules available to the package from the get-go. Some examples might include:

1. A Text Module - A module that can display a title, subtitle and some body text
2. An Image module - A module that can show a single image, either full width or a smaller inline image

Module models should be initialized by a command

Description

Making new modules should be straight forward. Add a command that can initialize a new module based off a stub included in the package.