Forums / Suggestions / ez.no blogs

ez.no blogs

Author Message

Paul Forsyth

Wednesday 28 January 2004 6:47:11 am

Why not have a blog for ez.no site plans/updates/features etc? News items are formal pieces of information which may mean some news will not ever be published, but blogs cover that ground perfectly.

I read a few blogs through rss feeds throughout the day and like the fact some sites blog about the official site:

http://www.fastmail.fm/
http://blog.fastmail.fm/log/index.php

Could be a way to showcase the blog stuff and have an rss feed at the same time.

paul

Alex Jones

Wednesday 28 January 2004 6:55:59 am

This would be very helpful. Perhaps the person who will be dedicated to community relations could consider a blog as a tool for the job.

Alex

Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]

<i>When in doubt, clear the cache.</i>

Bård Farstad

Wednesday 28 January 2004 7:22:53 am

I think this is a good idèa. We've discussed using blogs where the community guy can at the end of every week come with a small report on what's been going on in the community for the past week. Link to important threads etc.

Do you have more suggestions on how we could do this? ( What kind of things should be in this blog etc. )

--bård

Alex Jones

Wednesday 28 January 2004 7:45:18 am

It might be nice to have the blogger(s) provide updates on other eZ-related projects. It would be nice to see a contribution highlighted and perhaps explained. It wouldn't have to be much. It might also be nice to have more than one blogger, and not necessarily from eZ systems. There are probably some of us in the community who could commit to some regular updates on different areas. While some, like Paul F., Paul B. and others could provide insights to the community concerning the back-end and extension development for example, others could talk about other topics including template tips and tricks, or even how to adapt CSS example code for new sites. I would be happy to commit my time and knowledge to discussing front-end issues like CSS/XHTML.

The key would be expanding knowledge beyond answering a forum post on the boards. A larger view of development and presentation could prove beneficial to the community, and that view is hard to get when so much of the knowledge is pulled from different posts and documentation.

Oh, I don't mean to speak for either of the Pauls, or anyone else when suggesting multiple authors.

Alex

Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]

<i>When in doubt, clear the cache.</i>

Paul Forsyth

Wednesday 28 January 2004 7:59:49 am

I agree with Alex, but not sure about guest bloggers ;) Comments to blog entries would be fine for me ;)

Expanding some topics, and giving supplementary reports, would be ideal for the blog. It would be the mouthpiece of people from eZ about topical matters. I mean, im quite worried about the price of norwegian beer :) But that may chase off conference attendees. Ahem.

Topical information may include the status of particular features, work, new functions and bug fixes. Plans may be mentioned, sneek peeks, etc. Maybe a nod that people should look at pubsvn for something important and so on.

In fact, this would an incarnation of the announcment forum i've wanted to see for a while :) But because it is less formal, more 'blog news' should be easy to write.

paul

Tony Wood

Wednesday 28 January 2004 8:14:14 am

Its an interesting question as Article, blogs and comments share much of the same structure.

*Articles have comments
*Blogs have comments
*comments have comments in the case of forums.

As articles, blogs and comments are essionally the same i.e. authenticated and dated text storage mechanisms we need a way of seperating their usage. Personally I see articles as a way of storing information that has a long versioned life cycle. Blogs are a method of storing news like information or information that does not need to be versioned.
For example: An article would be used for a published coding standard, the blog would then be used as a starting point for a discussion about new learning that has been gain subsiquent to the article being published. This information would then be added to the next version of the document should it be deemed fit.
The blogs are perfect as they could be used as containers for all types of information including a transcript of a conversation had on a jabber server etc. People can then comment on this blog anonymously if they so wish as they can do with the article.

I think their should be guidelines to help people when choosing the object. The choice will always be thiers but by having a best practice we can help the formalisation of infromation in sites.

--Tony

Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development

Power to the Editor!

Free eZ Training : http://www.VisionWT.com/training
eZ Future Podcast : http://www.VisionWT.com/eZ-Future

eZ debug

Timing: Jan 18 2025 10:33:43
Script start
Timing: Jan 18 2025 10:33:43
Module start 'content'
Timing: Jan 18 2025 10:33:43
Module end 'content'
Timing: Jan 18 2025 10:33:44
Script end

Main resources:

Total runtime0.6714 sec
Peak memory usage4,096.0000 KB
Database Queries207

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0066 587.5391180.8516
Module start 'content' 0.00660.5008 768.3906658.2344
Module end 'content' 0.50740.1639 1,426.6250342.8906
Script end 0.6713  1,769.5156 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.00440.6555210.0002
Check MTime0.00170.2534210.0001
Mysql Total
Database connection0.00070.111110.0007
Mysqli_queries0.581686.62422070.0028
Looping result0.00230.33642050.0000
Template Total0.633194.320.3166
Template load0.00250.370420.0012
Template processing0.630693.921420.3153
Template load and register function0.00020.030710.0002
states
state_id_array0.00110.168310.0011
state_identifier_array0.00150.222420.0007
Override
Cache load0.00200.2963400.0000
Sytem overhead
Fetch class attribute can translate value0.00210.319250.0004
Fetch class attribute name0.00110.158480.0001
XML
Image XML parsing0.00150.224350.0003
class_abstraction
Instantiating content class attribute0.00000.002990.0000
General
dbfile0.00620.9281330.0002
String conversion0.00000.000930.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
1node/view/full.tplfull/forum_topic.tplextension/sevenx/design/simple/override/templates/full/forum_topic.tplEdit templateOverride template
6content/datatype/view/ezxmltext.tpl<No override>extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tplEdit templateOverride template
9content/datatype/view/ezxmltags/paragraph.tpl<No override>extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tplEdit templateOverride template
3content/datatype/view/ezxmltags/line.tpl<No override>design/standard/templates/content/datatype/view/ezxmltags/line.tplEdit templateOverride template
3content/datatype/view/ezimage.tpl<No override>extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tplEdit templateOverride template
1pagelayout.tpl<No override>extension/sevenx/design/simple/templates/pagelayout.tplEdit templateOverride template
 Number of times templates used: 23
 Number of unique templates used: 6

Time used to render debug report: 0.0002 secs