Content Pages - Content Element Paragraphs (contentPages.xml) (MGNLSTK-55)

[MGNLSTK-83] Header Area - Teamplate for Holding all Header Area Paragraphs Created: 22/Oct/08  Updated: 23/Jan/13  Resolved: 04/Nov/08

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Sub-task Priority: Major
Reporter: Christian Ringele Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: concept1, mme_sprint3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:

 Description   

All paragraphs of Header Area need a Template including them.
This template should manage, which Header Area Paragraph is chooseable for which Content Page.



 Comments   
Comment by Christian Ringele [ 22/Oct/08 ]

I asked per mail about the structure of Header Area and Content Area.

— Question Header vs. Content Area —
Wouldn't it make more sense to talk about header area in madder of only using it max. once per content page?
Like everything in header defines the content page before adding repetitively content (like TextImage paragraph)?
Like this i would see the two areas:
Header Are:

  • Breadcrumb
  • Nav Content
  • Headline
  • Subline
  • Source/Author (Date?/Author)
  • Depending on the Content Page: Map (HeaderMap) / Info Block News / Info Block Events / Info Block JobOffer / TOC
  • Text Features
  • Abstract

Content Area:

  • Rich Text
  • Subheading
  • ImageText
  • ImageText Large
  • Audio Player
  • Flash Video
  • Flash Element
  • Map (ContentMap)

What do you think? It's just that the Abstract is for me more a header part than content (just max. once makes sense anywhere).
Like this we could separate the content pages into their different headers variations (all singly used paragraphs), and their content (multiple usable paragraphs (collections)).

— TOC Question —
Another thing that surprises me is, that the TOC paragraph is only used on the TOC Content Page.
Doesn't the TOC paragraph make sense on all content pages which are able to hold more than one subheading?
It could be implemented that it can be added to every header of the content page, but just optional (except on the TOC Page, ther mandatory).

Comment by Christian Ringele [ 22/Oct/08 ]

The answer to my mail:

  • NavContent: Yes, you are right. I forgot this one, since it's a part of the navigation (like main or seconcary level navi) - but of course it's an (optional) part of all content pages.
  • Text features: Right again, obligatory on all Content Pages
  • TOC: In this case, we cut an option to prevent the editor from building ugly article pages. about 90% of all article pages are short and sweet and they won't need a TOC. With a TOC (and some editors will use it, if available) theses pages are still short ... but the sweetness has gone. A TOC is a special feature, and to make this clear to the editor, it has its own very special template.
  • Header vs. Content Area: of course you're right.
Comment by Christian Ringele [ 04/Nov/08 ]

Template structure of content pages is now devided into thiese definitions.

The content page templates definitions are now configurable for including dynamically these two content areas.

Generated at Mon Feb 12 07:23:34 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.