#133 ✓resolved

cms: multiple content areas

Reported by deizel | February 5th, 2010 @ 03:49 AM | in 0.8 alpha

It could be useful to allow more than a single editable area (wysiwyg editor) per page.

The current 'preview'+'content' is really just a single (concatenated) editable area, as it appears on the page where $content_for_layout is.

<div class="content"><?php echo $content_for_layout; ?></div>

There is no ability for someone to go "this exact page should have some content over there too", without them having to do the following:

  1. save the content
  2. go to modules
  3. make a new module
  4. edit the new module
  5. assign it to a rout.. oh wait there isn't one
  6. go to routes
  7. make a new route
  8. map the route to that single page and save it
  9. go edit the module again, assigning it to that route
  10. create their content without the aid of a wysiwyg editor

If, instead, the user could add another, named, wysiwyg editor to the content item they are editing, they could simply type the other content there.

<div class="images"><?php if ($this->hasContent('images')) echo $this->content('images'); ?></div>
<div class="content"><?php echo $this->content(); ?></div>
<div class="sidebar"><?php if ($this->hasContent('sidebar')) echo $this->content('sidebar'); ?></div>
<div class="testimonial"><?php if ($this->hasContent('testimonial')) echo $this->content('testimonial'); ?></div>

Image a page that needs content split over two clear design areas. For example, this page might have a white area in the top half, and a blue area in the bottom half. Without storing the table/divs/css-classes in the editable area (leaving potential for the editor to accidentally delete the blue area, and causing repetition if this needs repeated for other pages), the only option currently is to create a module that is stored somewhere in the system completely alien to the other content and somehow link them together.

These extra content areas would not negate the need for modules, since there would still be the need for blocks of functionality/content that could span multiple pages. It would however allow content editors to easily updating two separate blocks of content unique to a page.

I haven't thought about it much but this may need a custom View class, able to render multiple views with different content before rendering the layout page. Also, there may be opportunity to somehow blend the idea of extra content areas with modules (eg. the ability to use wysiwyg editors inside modules and/or the ability to add/edit modules from an "edit content" page)

Simple demonstration of concept here: http://demo.opensourcecms.com/frog/admin/ (admin/demo123) [edit a page, then find the little green plus icon on the right hand side of page]

Comments and changes to this ticket

  • dogmatic69

    dogmatic69 November 14th, 2010 @ 12:19 AM

    • State changed from “pending” to “resolved”
    • Milestone changed from Feature Requests to 0.8 alpha
    • Assigned user set to “dogmatic69”
    • Milestone order changed from “0” to “0”

    Using the new core content stuff with the layouts this is now possible. you can create "mini layouts" for any model and then render your content over that layout with mustache. mostly doable, now will need to find a way to render modules with mustache

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Please use this for the current version of Infinitas only, if you are using a older version of the Infinitas report bugs in that project.

Please submit bugs only as pending, and if its a feature request submit the ticket with the milestone "Feature Requests".

Shared Ticket Bins

People watching this ticket