--
You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to silverstripe-d...@googlegroups.com.
To post to this group, send email to silverst...@googlegroups.com.
Visit this group at http://groups.google.com/group/silverstripe-dev.
For more options, visit https://groups.google.com/d/optout.
Brilliant idea...i think the community would really benefit from something like this.
I've been thinking that besides different block types (eg video, gallery, text etc) it would also be useful to have something that makes it easier for the end user to create columns and rows.
If you are using bootstrap of foundation that makes use of some sort of grid system it would be cool if the end user would be able to create content that allows them to make use of the grid
system without having to know css and html. I have been toying with a couple of ideas specifically for Bootstrap.
Would this be something that would be useful as part of the block editing modules?
--
This is great, it's a concenpt I've been trying to come up with a solution to for a while. I'm leary of a systen then would tie it's data-model to the presentation layer too much. In terms of concept this article on A LIst Apart is great way of thinking about content blocks http://alistapart.com/blog/post/longform-content-with-craft-matrix Though training end user not to think about desktop layout is a bit tricky.
I think the big issue from an end user perspective is how saving and versioning is handled. The big problem with current gridfield implementations is that content blocks are relations and there is no way to easily control versioning not only on the the individual blocks but the collection on the page. Users tend to think of the page a whole unit and not a bunch of seperate DataObjects. Though I worry about the chaos of crating some sort of versioned relation table on $has_many relations.
To unsubscribe from this group and stop receiving emails from it, send an email to silverstripe-dev+unsubscribe@googlegroups.com.
To post to this group, send email to silverstripe-dev@googlegroups.com.
We also have the our original widget module, http://addons.silverstripe.org/add-ons/silverstripe/widgets, and this one is a little different, closer to being able to give design control to the CMS author, as it lets them build their own grid: http://addons.silverstripe.org/add-ons/burnbright/gridstructuredcontent
You received this message because you are subscribed to a topic in the Google Groups "SilverStripe Core Development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/silverstripe-dev/3kC1-iG1nYw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to silverstripe-d...@googlegroups.com.
--
I personally like the has_many approach for content-blocks (Page
1 -> * ContentBlock). It solves some problems that are related
to versioning and I don't think re-using of the same content-block
is that important. The re-using could be solved by some of the
mechanisms that are being used for SiteTree as well, such as
"Duplicate" (duplicate the block and link it to another page)
and/or "Virtual Page" (a dataobject that only serves as a pointer
to the original object).
It also looks like this might become an upcoming feature in
SilverStripe
(http://silverstripe.uservoice.com/forums/251266-new-features/suggestions/6478313-column-or-block-content-editing),
so maybe there will be a single module to rule them all :)
Cheers - Roman
--
You received this message because you are subscribed to a topic in the Google Groups "SilverStripe Core Development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/silverstripe-dev/3kC1-iG1nYw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to silverstripe-d...@googlegroups.com.
--
You received this message because you are subscribed to a topic in the Google Groups "SilverStripe Core Development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/silverstripe-dev/3kC1-iG1nYw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to silverstripe-d...@googlegroups.com.
To post to this group, send email to silverst...@googlegroups.com.
Visit this group at http://groups.google.com/group/silverstripe-dev.
For more options, visit https://groups.google.com/d/optout.
--