Forums / Setup & design / The best approach and normal approach to build new site?

The best approach and normal approach to build new site?

Author Message

Wei Dai

Friday 11 July 2008 3:47:54 am

Hi,
I have an interesting questions as a new user/developer of the eZ Publish.

I have already read certain material on eZ Publish. There are many information on how to customize the eZ Publish with the Webinterface to build a new site. However, my question is this: is the web interface suit for any kind of the CMS (assume we don't require an ezflow site)?

I knew the basic steps to build a new site: 1. Content modeling (define contend classes and create content objects) and site structuring (construct the shape of the node tree). 2. Design the site's look and feel. 3. Tire the design and the content together use the template language (integration).

Of course, above steps are not necessary following a restrict order; design and content modeling can be doing simultaneously. However, my dilemma is:

If I based on the webinterface, there are already have a set of template, and have content classes I may can take advantage of (e.g. the frontpage class), and there are seem more tutors and guide on this. But, I need to based on the exist CSS and html structure, firebug is good, but there are so many CSS ids and classes, some CSS classes maybe involve with the content class. Is the webinface design can be changed to anything only through alter the two css files and images of the site style?

If I start from scratch, the obvious disadvantage is that I need build very template and override rules/template from sratch, and know a new language, the template language. And advantage is that I have the flexibility and freedom to create the template markup.

What you guys usually do when start to build a new site?

P.S. I am actually a PHP dev, and use the template language seems odd to me. Are you all PHP devs? Are designer use the template language?(I always think that the designer should know the content structure when s/he start to design, am I right?).

Certified eZ Publish 4 developer looking for develop information & collaboration.

Piotrek Karaƛ

Saturday 12 July 2008 2:15:07 am

Hello Wei,

We hardly ever use complete website interface, and build our interfaces from scratch or some sort of general-use design/config base. Some of the reasons:
- website interface is indeed an interface - includes lots of logic and dedicated solutions, which do not match our needs or preferences in most cases (that includes fetches, caching layer, organization of templates).
- website interface is complex enough (as you noticed) to take some time to learn, which make sense only if you're keen to learn or find ezwebin useful for your purposes.
- website interface's design, because it is highly repeatable, is not acceptable for our customers.
- website interface's partial adaptation for a project makes future development of the project more expensive than with dedicated interface.

However, website interface is a good place to look for patterns, examples, generally learning for implementing your customized solutions, a good source of practices and conventions to follow.

--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu

eZ debug

Timing: Jan 19 2025 09:45:03
Script start
Timing: Jan 19 2025 09:45:03
Module start 'content'
Timing: Jan 19 2025 09:45:04
Module end 'content'
Timing: Jan 19 2025 09:45:04
Script end

Main resources:

Total runtime0.1643 sec
Peak memory usage2,048.0000 KB
Database Queries141

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0065 590.3281180.8125
Module start 'content' 0.00650.0063 771.140693.9766
Module end 'content' 0.01280.1515 865.1172523.9219
Script end 0.1643  1,389.0391 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.00372.2672200.0002
Check MTime0.00140.8710200.0001
Mysql Total
Database connection0.00070.436310.0007
Mysqli_queries0.117271.34181410.0008
Looping result0.00140.83281390.0000
Template Total0.151091.910.1510
Template load0.00090.575110.0009
Template processing0.150191.321410.1501
Override
Cache load0.00060.387110.0006
Sytem overhead
Fetch class attribute can translate value0.00080.482610.0008
XML
Image XML parsing0.00030.172210.0003
General
dbfile0.00241.4367200.0001
String conversion0.00000.003630.0000
Note: percentages do not add up to 100% because some accumulators overlap

CSS/JS files loaded with "ezjscPacker" during request:

CacheTypePacklevelSourceFiles
CSS0extension/community/design/community/stylesheets/ext/jquery.autocomplete.css
extension/community_design/design/suncana/stylesheets/scrollbars.css
extension/community_design/design/suncana/stylesheets/tabs.css
extension/community_design/design/suncana/stylesheets/roadmap.css
extension/community_design/design/suncana/stylesheets/content.css
extension/community_design/design/suncana/stylesheets/star-rating.css
extension/community_design/design/suncana/stylesheets/syntax_and_custom_tags.css
extension/community_design/design/suncana/stylesheets/buttons.css
extension/community_design/design/suncana/stylesheets/tweetbox.css
extension/community_design/design/suncana/stylesheets/jquery.fancybox-1.3.4.css
extension/bcsmoothgallery/design/standard/stylesheets/magnific-popup.css
extension/sevenx/design/simple/stylesheets/star_rating.css
extension/sevenx/design/simple/stylesheets/libs/fontawesome/css/all.min.css
extension/sevenx/design/simple/stylesheets/main.v02.css
extension/sevenx/design/simple/stylesheets/main.v02.res.css
JS0extension/ezjscore/design/standard/lib/yui/3.17.2/build/yui/yui-min.js
extension/ezjscore/design/standard/javascript/jquery-3.7.0.min.js
extension/community_design/design/suncana/javascript/jquery.ui.core.min.js
extension/community_design/design/suncana/javascript/jquery.ui.widget.min.js
extension/community_design/design/suncana/javascript/jquery.easing.1.3.js
extension/community_design/design/suncana/javascript/jquery.ui.tabs.js
extension/community_design/design/suncana/javascript/jquery.hoverIntent.min.js
extension/community_design/design/suncana/javascript/jquery.popmenu.js
extension/community_design/design/suncana/javascript/jScrollPane.js
extension/community_design/design/suncana/javascript/jquery.mousewheel.js
extension/community_design/design/suncana/javascript/jquery.cycle.all.js
extension/sevenx/design/simple/javascript/jquery.scrollTo.js
extension/community_design/design/suncana/javascript/jquery.cookie.js
extension/community_design/design/suncana/javascript/ezstarrating_jquery.js
extension/community_design/design/suncana/javascript/jquery.initboxes.js
extension/community_design/design/suncana/javascript/app.js
extension/community_design/design/suncana/javascript/twitterwidget.js
extension/community_design/design/suncana/javascript/community.js
extension/community_design/design/suncana/javascript/roadmap.js
extension/community_design/design/suncana/javascript/ez.js
extension/community_design/design/suncana/javascript/ezshareevents.js
extension/sevenx/design/simple/javascript/main.js

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1pagelayout.tpl<No override>extension/sevenx/design/simple/templates/pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs