Suggestions

[al...@aspbrasil.net]

Hi

A list of few suggestions

1 - Kaliko NUget Package ready for different databases
Ex: Oracle

2 - 1 - Kaliko NUget Package with some commom use site components
- Menu
- Breadcrumb
- Site Map
- Image Gallery
- Simple site structure like folder and file (a pagetype, controller, view, viewmodel for each of these with a title, image, text field and all the parameters necessary to use then in a simple site(Name, Id, Create date, pagetype, url, visible in menus etc), so morons like me could start a site almost without progamming, just calling @Model.parameter and even copy those to create some new

3 - Possibility to organize the editor page. Today there are:
Standard information
Content
Information
Would be interesting to create new sections. Ex: Site Top, Section 1, 2, 3 etc

[Fredrik Schultz]

Thanks for the feedback! Good input, much appreciated.

1) A new Oracle package will be added to the pending 1.2.4 release to help set up new projects in the same way as previous SQLite and SqlServer packages have.

2) Although there's a demo project (https://github.com/KalikoCMS/DemoSite.Mvc) that cover some of this ground I agree that it would be nice to package some of this type of common functionality to be included as optional components. I've begun working a little on theme-able starter-kits that should lay the foundation for most common types of websites so that the developers can get up to speed quickly with the basics and instead focus on the details unique for the implementation.

There's a few helpers today already for breadcrumbs and menu trees, but more should be added.

3) There's a way to group properties by tabs. By default all properties is placed under "Content", but it's possible to add own custom tabs to group the properties under just by adding TabGroup to the property attribute, like:

    [Property("Sponsor", TabGroup = "Extras")]

    public virtual CollectionProperty<SponsorProperty> Sponsors { get; set; }

It would however be nice to able to add softer sections as well (that for instance could be used as a second level under a tab) and I've registered an issue to add this in a future version.