eZ Community » Forums » eZ Publish 5 Platform » EZ Publish - content structure and...
expandshrink

EZ Publish - content structure and block level elements

EZ Publish - content structure and block level elements

Monday 04 March 2013 4:04:50 pm - 10 replies

Hi,

I'm trying to best determine how to implement EZ Publish. I need to manage blocks of content, rather than published articles. What I am not sure is how is it recommended to use multiple blocks of content? For example the following home page would have four block elements as in this mock uup.

http://i.imgur.com/WHPAwo0.png

Would I have to create a custom content type to manage blocks of content? How can I access multiple blocks to render a particular page.

I also need to be able to have multiple brands or customisations of content, as such what is recommended to implement.

If someone can point me in the right direction that would be much appreciated.

Thanks

Andy

Modified on Monday 04 March 2013 4:05:46 pm by Andrew Johnstone

Monday 04 March 2013 4:54:19 pm

Hi Andrew !

I think eZFlow exactly fit your need, you should take a look. http://doc.ez.no/Extensions/eZ-Publish-extensions/eZ-Flow/eZ-Flow-2.5

Arthur.

Monday 04 March 2013 5:14:54 pm

Quote from Arthur Guigand :

Hi Andrew !

I think eZFlow exactly fit your need, you should take a look. http://doc.ez.no/Extensions/eZ-Publish-extensions/eZ-Flow/eZ-Flow-2.5

Arthur.

Does this work with EZ Publish 5?

Much of the content is based on content blocks not article based, so would this be suitable for creating an entire website in this manner?

Monday 04 March 2013 5:56:51 pm

I didn't tried eZ publish 5 yet but there's no reasons eZflow is not maintained.

In my opinion, eZflow is flexible enough to create whatever you want. It does not need to be article based, you can use custom content classes to hydrate your blocks. Since you can add the ezflow layout datatype on every classes, this solution is suitable for creating an entire website if you correctly override the associated views.

Monday 04 March 2013 6:09:55 pm

Quote from Arthur Guigand :

I didn't tried eZ publish 5 yet but there's no reasons eZflow is not maintained.

Actually, it will be fully part of the core as the main field type (new name for datatypes) will be fully implemented in read only mode for 5.1 (work is currently in progress, see https://jira.ez.no/browse/EZP-20424).

And if you want to monitor the work in progress, check the corresponding PR.

Modified on Tuesday 05 March 2013 1:37:10 pm by Jérôme Vieilledent

Tuesday 05 March 2013 1:35:26 pm

Note that an unfinished pull request is given in the issue's comments: https://github.com/ezsystems/ezpublish-kernel/pull/251.

This PR will be merged in the next weeks (no official ETA), and will therefore be available in a further Community Project build.

Feel free to provide feedback either on the issue, or in the PR. Remember that you can watch pull requests and jira tickets.

Wednesday 06 March 2013 1:18:01 pm

The best approach to this depends on what you want to do on the page. 

If the page will need to be updated regularly, content will be scheduled to appear/disappear at certain times, or you need to have the flexibility to allow editors to change the layout, then eZ Flow would be the best approach. 

If you just need to provide this structure, but don't need a scheduling component and adjustable layout, you could simply create a content type and use embeds in eZOE to include your blocks of content.

Wednesday 06 March 2013 1:29:36 pm

Quote from Joe Kepley :

you could simply create a content type and use embeds in eZOE to include your blocks of content.

Using eZOE for this is a bit overkill, isn't it ? You should use Object Relations (aka ezobjectrelationlist) instead blunk.gif Emoticon.

Wednesday 06 March 2013 1:30:48 pm

Quote from Joe Kepley :

The best approach to this depends on what you want to do on the page. 

If the page will need to be updated regularly, content will be scheduled to appear/disappear at certain times, or you need to have the flexibility to allow editors to change the layout, then eZ Flow would be the best approach. 

If you just need to provide this structure, but don't need a scheduling component and adjustable layout, you could simply create a content type and use embeds in eZOE to include your blocks of content.

Thanks, that's great. Initially the content will be largely static and simply translated into different content. Would you mind clarifying how to do this or point me in the right direction?

I'm slowly getting my head around the ez publish 5.

Wednesday 06 March 2013 2:35:52 pm

I would indeed also go for a set of object relation list attributes. XmlText for this is a bit overkill.

The multiple Ui possibilities it offers for relations makes it quite efficient for this.

Wednesday 06 March 2013 2:54:22 pm

Quote from Bertrand Dunogier :

I would indeed also go for a set of object relation list attributes. XmlText for this is a bit overkill.

The multiple Ui possibilities it offers for relations makes it quite efficient for this.

Depends on if he has needs for letting the editor control the layout or not, if he does; either ezxmltext or ezflow, if not; relation lists.

expandshrink

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from