orchardcms - Orchard 'Layers' seem an odd concept when compared to other Asp.net based CMSs -


we're busy investigating orchard cms alternative existing asp.net based cms systems use. came across orchard, installed , started on tutorials.

the 1 part confuses me layers. don't have in other cmss seem compare this.

what we're used to, having couple of master pages (or templates) create new page , choose template page , add widgets various container areas.

here seem create multiple layers , apply them based on url rules (or perhaps others too).

questions:

  1. assuming these layers, in photoshop layers, seem you're adding widgets layers bottom of stack means widget added bottom layer appear in top layer. correct? or can 1 use rules omit layer?
  2. has documented obvious pitfalls approach?

it seems odd way go things, perhaps because we're not used it.

thanks,

the name can confusing because sound there sort of z-index ordering or something. however, layers' job determine whether or not shape gets rendered. if layer rule returns true, shapes in layer visible. if layer rule returns false, shapes in layer not rendered. that's there it.

this useful authenticated/non-authenticated scenarios. also, since layer rules extensible, can add own complex scenarios. example, want have widgets on site during work hours only. build own layer rule extension , create layer widgets called "office-hours-only".


Comments

Popular posts from this blog

android - Get AccessToken using signpost OAuth without opening a browser (Two legged Oauth) -

org.mockito.exceptions.misusing.InvalidUseOfMatchersException: mockito -

google shop client API returns 400 bad request error while adding an item -