Hi Christoph, 

You may have seen the two existing Bootstrap-based attempts : 

• The eZ one : https://github.com/ezsystems/ezdemo
• The Community-based one : http://projects.ez.no/hwboot 

?

Is that what you had in mind ?

Cheers !

I would suggest to start from scratch with some boilerplate. The old ezwebin's HTML is not suitable for new features like responsiveness. I am not saying it is not possible just think that you will do better job in shorter time if you use some new HTML & CSS rather than changing the 4 years old "divitis"

Or wait for the new ezdemo to hit the streets, it should be much more suitable for your issue

Hey! 

thank you very much for your reply. I will answer separately: 

@Nicolas: Yes there are some nice implementations, but if i'm right they are not longer necessary after the etna release. But my problem is I have to upgrade a eZ 4.2 eZwebin template to some kind of mobile version (responsive version)

Thats the reason why I'll probably will use your first recommended attempt, the eZ one. 

Isn't the eZ one the same implementation which will be released within Etna? 

I guess that I have to start from scratch with basic layout elements and will merge the complete template-base from the source layout to the new layout. 

Thank you very much for kicking me into the right direction!! 

Best

Chris

Quote from Christoph Stollwerk :

@Nicolas: Yes there are some nice implementations, but if i'm right they are not longer necessary after the etna release. But my problem is I have to upgrade a eZ 4.2 eZwebin template to some kind of mobile version (responsive version)

mobile and responsive are quite different things which do you need exactly?

Hey Ivo,

thank you very much for your reply! Please clarify me..

Isn't mobile a subset of responsive? So that you could proclaim reaching a mobile version of a website is solved best with responsive webdesign? In my opinion responsive webdesign is a component to add the fluous functionality to a layout with media-queries to solve the multichannel issue.
The embeded layout changes responds a mobile version for the actual device. So, the mobile version is just one of many layouts implemented through responsive webdesign.

But to be honest, todays scope is not only mobile or tablet (or tv or maybe googles project glass   ).
Responsiveness is mandatory for all latest releases.
I'd appreciate any verification or falsification on that.

So does it make sense to implement any mobile version of running website and avoid responsiveness?

Have a nive weekend !

Best Chris

Hi Christoph,

I'll try to make a long story short. I am not exactly an expert on the matter, but here is how I see it: mobile and responsive are conceptually and technically different although they overlap:

- responsive tries to solve the problem of many screen sizes (which emerged lately) like on mobile phones, tablets, laptops, desktop, etc. The concept it so show the same content but in adaptive way (re-positioning boxes,...). In technical terms it is the same HTML on the same domain using different CSS with media queries.

- mobile tries to solve the small screen problem with touch features (particularly phones ). The concept is to show reduced content with some extra features which make sense only while user is on the move. Technically it is a special HTML on different domain (m.*.*) with geo-targeting enabled.

- you can, of course, build a responsive layout which can cover the mobile concept completely (the overlap)

Thus, choice depends on the situation you have:

1. For bigger projects where you need to revamp the design anyway, where you have a great team to create a good responsive design (this is really not an easy thing), where the site is content oriented (like media vertical), where tablets need to be covered too -> responsive

2. For projects where the main site will not be changed, where there is some "geo" content or content interesting for people in the move, or you just have smaller budget -> mobile (e.g.we are just releasing a mobile telecom web which will have reduced content and some special features like: searching for nearest hotspot, nearest store, requesting a call back, system health monitor, etc)

Hope this helps

Hi Ivo, 

thanks a lot for your very complete feedback! 

The description you posted sounds very well to me. They fit my understanding of the concepts. It'll be interesting how gesture input could be resolved in the near future with the reponsive-concept, because in my opinion that should really be included. I know,input is not really a responsive webdesign topic. 

It's good that you put numbers before these paragraphs about mobile and responsive. I will understand it as a workflow  

You helped me a lot, thank you
What mobile telecom web did you release? 

The ideal way would be to provide different user experiences (through different call-to-actions's/reduced content and device related funcitonality). But the main problem is that most ordinary customers have small doubts on blowing up their webpages and this is not only related to their budget.  

Best Regards

Chris

Quote from Christoph Stollwerk :

What mobile telecom web did you release? 

It is not released publicly yet so I'll send you the link via email....

Quote from Christoph Stollwerk :

The description you posted sounds very well to me. They fit my understanding of the concepts. It'll be interesting how gesture input could be resolved in the near future with the reponsive-concept, because in my opinion that should really be included. I know,input is not really a responsive webdesign topic.

I completely forgot that my colleague wrote a blog post on the matter

http://www.netgen.hr/eng/Blog/Going-mobile-with-eZ-Publish

Hey Ivo, 

thank you very much for that links you've posted. Now i get your strict distinction between responsive and mobile completely. 

An approach which combines both concept would be a nice extension for the one or another. I just thought, how can we solve things like 'reduced content '  only with responsive webdesign. So to give responsiveness a template component. Not implemenet but in my opinion necessary. What do you guys think? 

The blog article was very nice to read. Well done  

Best 

Chris