How to design a eZ publish site?

«

Previous topic

|

|

Next topic

»

Author	Message
John D	Tuesday 09 November 2010 9:54:20 am Hi, I have just started learning about eZ Publish and have installed 4.4 on a local server @ home. The front end admin and back end admin is understanable after reading the documentation. But when in comes to doing changes to the design eZ Publish is a bit harder to understand than other CMS. I have searched the internet and forum for good articles about doing changes to the design. But I can't really find a straight forward(updated) article/tutorial. So I was hoping someone here could point me in the right direction. If I change the sitestyle, that is only the colors/style? To make bigger changes to the layout, I have to start working with the templates? Is there a "empty" set of templates I can start with and upload as a design package when I am happy with the result.
Jérôme Vieilledent	Tuesday 09 November 2010 12:01:14 pm Hi John What package are did you start from ? Website interface ? Plain site ? eZ Flow ? You'll find some pieces of information in this article (pretty old though). IMHO, the best is to work with your own templates, wrapped up in a design extension (see this article about extensions). I was planning to write a tutorial about that but I'm unfortunately short on time...
John D	Tuesday 09 November 2010 12:24:08 pm Hi Jérôme, Thanks for the reply. I installed with ezwebin without demo content.
Romeo Antony	Tuesday 09 November 2010 11:21:31 pm John, you will be able to easily grasp how sites developed & designed in inezp if you go through this manual(step by step ) https://auth.ez.no/ezpublish/documentation/building_an_ez_publish_site/creating_the_tscm_site Regards Romeo
John D	Wednesday 10 November 2010 2:05:25 am Hi Romeo, Thanks for the reply. The article is last updated 2004? Is this safe to use with the 4.4 installation I got? I got a design that I would like to add to my eZ Publish installation, but with all the different articles and information I am not sure where to start.
Romeo Antony	Thursday 11 November 2010 5:07:19 am John, doesn't matter whicherver version you are using . Once you understand the basic about the ez desgn structure and organization, thing would become smotther. I think designpart like how the templates are loaded , its working is a bit hard to understand. I have followed the same article mentioned. Basic is the same . So try it

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing:	Jan 30 2025 00:58:31
Script start
Timing:	Jan 30 2025 00:58:31
Module start 'layout'
Timing:	Jan 30 2025 00:58:31
Module start 'content'
Timing:	Jan 30 2025 00:58:31
Module end 'content'
Timing:	Jan 30 2025 00:58:31
Script end

Main resources:

Total runtime	0.0141 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0044	588.1328	151.2109
Module start 'layout'	0.0044	0.0020	739.3438	36.6719
Module start 'content'	0.0064	0.0064	776.0156	94.1719
Module end 'content'	0.0128	0.0012	870.1875	37.9766
Script end	0.0140		908.1641

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0021	14.7212	14	0.0001
Check MTime	0.0010	6.9155	14	0.0001
Mysql Total
Database connection	0.0007	5.0537	1	0.0007
Mysqli_queries	0.0022	15.6740	3	0.0007
Looping result	0.0000	0.0575	1	0.0000
Template Total	0.0009	6.6	1	0.0009
Template load	0.0006	4.5088	1	0.0006
Template processing	0.0003	2.0445	1	0.0003
Override
Cache load	0.0004	3.0888	1	0.0004
General
dbfile	0.0022	15.5319	8	0.0003
String conversion	0.0000	0.0355	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs