eZ Community » Blogs » eZ Publish Next UI » Redefining eZ Publish User...

By

Redefining eZ Publish User Interface, story 3

Saturday 16 March 2013 7:41:52 pm

  • Currently 3 out of 5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Hello all,

Time for the third story of our initial UX concept for eZ Publish next User Interface. Read on!

It is about landing page and building forms.

Landing page management was formerly managed through eZ Flow extension. The goal is to have this feature built-in, so it will not be an extension. More details on landing page management will be provided in story 4, where we will work on a more conventional front page, with many blocks. This case here focus on a simple landing page for a marketing campaign, a classic.

We also touch the topic of user forms and form builder. The way it is introduced is slightly different. It is not anymore connected to the content model via information collector attributes. Forms are not content objects. We have in stock a story that will show how forms can be reused (using reusable set of fields), this will also be shared later. And finally a story on how accessing and managing the captured data -- this is cleary not the focus here.

The focus is on how a marketer can quickly create a form for a lead capture campaign and hide behind it for instance a whitepaper for download. A very classic use case when eZ Publish is used for B2B marketing purposes.

Hope you will enjoy, remember, this is the first wave where we go through a wide range of features, laying the foundations. Your feedback is important to us now! The next wave we will go in more specific details on the features we introduced. Please keep commenting!

Note: the "eZ Flow" landing page block we use is 'embed object'. This signal we would like to somehow unify the concept of eZ Flow blocks and the one of embeds in the online editor (such as objects or other custom tags). To a certain point, any embed in the online editor could be something we might want to expose as a landing page block. The rationale behind this is to have a single consistent way to do similar things. This is still a topic we are thinking of and any input will be much appreciated.

Proudly Developed with from