Also, note that a 'target container' can be the destination for a link that replaces just part of a page's content rather than the entire page. It's really just an optimisation, and has certain problems associated with it, so I'd recommend leaving target containers until a later date, when you're very comfortable with the other concepts.
On Aug 21, 12:26 am, markus giesen <[email protected]> wrote: > Hi Dave, > > A container works like an include. > You replace the part of your website where the content goes with an > container. > So the main template holds basically all your html around the content > like > javascript and CSS references, Html construct > within these you place your container. > > This container is able to include new templates which can only be a > DIV with a text element or anything else. > A container can include more than one new block/page part > You can nest this, i.e. > Page (with HTML, including JS, CSS, ...) > -ContainerA > ---Page part > ---Page part > ---Page part > ---- ContainerB > ------Another page part > ------Another page part > ---Page part > ---Page part > > A block or a page part is just another Content Class and it's up to > you what you put into it. > > Maybe Adrians superposts are helpful for you > too:http://www.reddotcmsblog.com/the-one-true-container-part > > Cheers, > Markus > > On 21 Aug., 03:53, dmackerman <[email protected]> wrote: > > > Hello everyone, > > > I am very new to RedDot, and I'm trying to understand the correct > > structure of how to setup a project. I'm trying to grasp the concept > > of Content Classes, containers, templates, etc. > > > My basic knowledge is this: > > > Every page that will have the same content, will all use the same > > Content Class. Inside of that Content Class you have placeholders for > > content (text, anchors) and structural elements that define the layout > > of the page (containers, lists). You can have several templates that > > will display that information on the page differently if you need to, > > for RSS XML files or something like that. > > > My question is this, how am I supposed to set up the templates? Say > > that I have a home page that is drastically different than the rest of > > my pages. I create the template for it. This template would have all > > of my HTML and CSS layout elements in (divs, etc) correct? > > > Inside of this template I would put place holders for the content? > > Where do containers come in? My understanding is that containers just > > hold content, but how do I put a placeholder (say, text) inside a > > container? I also don't understand the concept of Target Containers. > > > If I wanted to divide my page up into sections, such as header, > > leftNav, content, rightNav, and footer, would I make these > > containers? > > > I am definitely confusing myself, and I'm sure I am making it harder > > than it really is. Can anyone clarify the extreme basics for me? I've > > read the "Content Class" documentation, but for some reason it didn't > > really help me. It explained that "you need to break it up into > > blocks", but then didn't go on to explain how to do so inside of > > RedDot. > > > Any help is appreciated! > > Thanks, > > Dave --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en -~----------~----~----~----~------~----~------~--~---
