Re: [zeta-dev] Website
On Thu, 2010-07-29 at 23:09 +0200, Christian Grobmeier wrote: [..] > Here is some more information on a good podling sitep: > http://incubator.apache.org/guides/sites.html Thanks for the pointer. I incorporated the suggested and required changes from there. > It also describes the location the zeta site. I have prepared the > folder for it already. > > I also would like to mention, that Zeta Components is currently not a > full Apache project, its in incubation phase. I think its worth > mentioning this state on the website. Usually podlings write something > like:"Apache Zeta Components is currently underunning incubation..." > or similar. This makes clear that things change and some things like > copyright or licensing stuff need to be sorted out. > > Additionally some podlings (or those I know) add the Incubation logo > somewhere: > http://incubator.apache.org/images/apache-incubator-logo.png Added both to the start (news) page. :) (Will be online soonish) One open question left to me is the "incubation status file", which is intended to be available at http://incubator.apache.org/projects/podlingname.html - will you take care of that? > Just out of curiosity - what tool did you use for generating the site? http://web-content-viewer.org - it is the software some of us are also using for our blogs. But in this case I wrapped it in a make file to make it transparent to the users. The software never reached something one would want to call "alpha" - it is not at all ready for "users" :) Kind regards, Kore -- Kore Nordmann(GPG 0xDDC70BBB) - What I do: http://kore-nordmann.de/portfolio.html - Motivate me: http://wishlist.kore-nordmann.de/ signature.asc Description: This is a digitally signed message part
Re: [zeta-dev] Website
Hi Manuel, On Thu, 2010-07-29 at 20:36 +0200, Manuel Pichler wrote: > Hi Kore, > > the website looks really nice and shiny, but I have found one little > content issue. The main headline and most of the paragraphs on > "Documentation > Installation"[1] still still contain the text "eZ > Components" instead of "Zeta Components". Thanks for the pointer. I replaced in the title and added a note to the document. Especially this document still requires quite a bit refactoring, since it metions "eZ Components" and "eZ Systems" quite often… Kind regards, Kore -- Kore Nordmann(GPG 0xDDC70BBB) - What I do: http://kore-nordmann.de/portfolio.html - Motivate me: http://wishlist.kore-nordmann.de/ signature.asc Description: This is a digitally signed message part
Re: [zeta-dev] Website
Good job ! Is there a thing we can do about the copy paste that occurred on PHP code ? When you select the code and past it, each line are prefixed by # or number. It could be an improvement. Else, I ve looked to Sphynx, is it only for Python ?
Re: [zeta-dev] Website
Hello, > The website is available for preview here: > http://zeta:z...@zeta-components.org/news.html wow, it looks fantastic! > Afaik it considered best practice to commit the HTML to the project > repository and the website will then be deployed to the Apache HTTP > mirrors. > I would prefer to commit the whole repository contents to "/website", so > that everybody can easily regenerate the website. (Makefile and docs are > included). Do you second this? Thats true. The complete generated website needs to be checked in. In case of an error, a simple svn co should be able to restore it. The logging project called their folder "/site", but your proposal is fine anyway. Here is some more information on a good podling sitep: http://incubator.apache.org/guides/sites.html It also describes the location the zeta site. I have prepared the folder for it already. I also would like to mention, that Zeta Components is currently not a full Apache project, its in incubation phase. I think its worth mentioning this state on the website. Usually podlings write something like:"Apache Zeta Components is currently underunning incubation..." or similar. This makes clear that things change and some things like copyright or licensing stuff need to be sorted out. Additionally some podlings (or those I know) add the Incubation logo somewhere: http://incubator.apache.org/images/apache-incubator-logo.png I don't think its necessary, but I like it because of mentioned reasons. Also its a good ad for the Incubator project of course :-) Just out of curiosity - what tool did you use for generating the site? Best regards, Christian
Re: [zeta-dev] Website
Hi Kore, the website looks really nice and shiny, but I have found one little content issue. The main headline and most of the paragraphs on "Documentation > Installation"[1] still still contain the text "eZ Components" instead of "Zeta Components". Greetings Manuel [1] http://zeta-components.org/documentation/install.html On Thu, 2010-07-29 at 13:06 +0200, Kore Nordmann wrote: > Hi, > > As you know I was working on the new website for the zeta components. I > just regenerated it - the API documentation now contains proper links to > the fisheye source code browser. > > The website is available for preview here: > http://zeta:z...@zeta-components.org/news.html > > The repository containing the website and the generation scripts is > available at: > svn://svn.qafoo.com/zeta-website > > The full Checkout is about 256MB and contains about 26k files - the API > documentation generates quite some HTML files (and for now it is only > generated for trunk/). > > Afaik it considered best practice to commit the HTML to the project > repository and the website will then be deployed to the Apache HTTP > mirrors. > > I would prefer to commit the whole repository contents to "/website", so > that everybody can easily regenerate the website. (Makefile and docs are > included). Do you second this? > > This would mean, that "/website/htdocs" would then be mirrored to the > Apache web servers (which is, without the .svn dirs, around 50MB). > > Kind regards, > Kore >
Re: [zeta-dev] Website
Kore, On Thu, Jul 29, 2010 at 1:29 PM, Kore Nordmann wrote: > On Thu, 2010-07-29 at 13:20 +0200, Jerome Renard wrote: > > - Is that normal that some methods do not point to the API doc ? For > example > > if you take this page : > > > http://zeta-components.org/documentation/trunk/Base/tutorial.html#file-operationsthe > > string "ezcBaseFile::findRecursive()" from "This example shows how to > > use the ezcBaseFile::findRecursive() method:" does not point anywhere, is > > that normal ? > > Yes, for now. There are no links and source code highlighting in the > tutorial. It is "comlicated" to setup natively with python-docutils and > the post-processing of the generated HTML files is just not implemented > yet. I will add that at some point. > > Do you think that migrating to Sphinx [1] would be relevant ? Just asking. > > - Do you think you can add some syntax coloring to the PHP code so it is > > easier to read ? > > The source highlighting in the API docs is just a matter of some CSS > rules - should be easy to add. :) > Cool :) > > For the tutorials: See above. > > > Other than that, the website looks good, I especially love the new logo, > who > > created it ? > > That would be me. Thanks. :-) > Kudos to you then :) 1. http://sphinx.pocoo.org/ -- Jérôme Renard http://39web.fr | http://jrenard.info
Re: [zeta-dev] Website
On Thu, 2010-07-29 at 13:20 +0200, Jerome Renard wrote: > - Is that normal that some methods do not point to the API doc ? For example > if you take this page : > http://zeta-components.org/documentation/trunk/Base/tutorial.html#file-operations > the > string "ezcBaseFile::findRecursive()" from "This example shows how to > use the ezcBaseFile::findRecursive() method:" does not point anywhere, is > that normal ? Yes, for now. There are no links and source code highlighting in the tutorial. It is "comlicated" to setup natively with python-docutils and the post-processing of the generated HTML files is just not implemented yet. I will add that at some point. > - Do you think you can add some syntax coloring to the PHP code so it is > easier to read ? The source highlighting in the API docs is just a matter of some CSS rules - should be easy to add. :) For the tutorials: See above. > Other than that, the website looks good, I especially love the new logo, who > created it ? That would be me. Thanks. :-) Kind regards, Kore -- Kore Nordmann(GPG 0xDDC70BBB) - What I do: http://kore-nordmann.de/portfolio.html - Motivate me: http://wishlist.kore-nordmann.de/ signature.asc Description: This is a digitally signed message part
Re: [zeta-dev] Website
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On 07/29/2010 01:06 PM, Kore Nordmann wrote: > The website is available for preview here: > http://zeta:z...@zeta-components.org/news.html I love the new design. The website looks really cool. I think all essentials are in place, so that we can go online with a first version and migrate the website source to Zeta SVN soonish. All minor adjustments (e.g. CSS, code links in tutorials and stuff) can then be performed there, so everyone can take part in it. Nice work! Cheers, Toby - -- Tobias Schlitthttp://schlitt.infoGPG Key: 0xC462BC14 Want to hire me? Need quality assurance?http://qafoo.com eZ Components are Zeta Components now! http://bit.ly/9S7zbn -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxRZZcACgkQ5bO3TcRivBRH6wCfQP6LfyH/UO6MT+ioBHynOzqe L+IAniP2cUZkp9MGQ9Yfv8TYJ7jy8Dp6 =AZhb -END PGP SIGNATURE-
Re: [zeta-dev] Website
Hi Kore, On Thu, Jul 29, 2010 at 1:06 PM, Kore Nordmann wrote: > Hi, > > As you know I was working on the new website for the zeta components. I > just regenerated it - the API documentation now contains proper links to > the fisheye source code browser. > > The website is available for preview here: >http://zeta:z...@zeta-components.org/news.html > > The repository containing the website and the generation scripts is > available at: >svn://svn.qafoo.com/zeta-website > > The full Checkout is about 256MB and contains about 26k files - the API > documentation generates quite some HTML files (and for now it is only > generated for trunk/). > > I just had a look and I have 2 questions : - Is that normal that some methods do not point to the API doc ? For example if you take this page : http://zeta-components.org/documentation/trunk/Base/tutorial.html#file-operationsthe string "ezcBaseFile::findRecursive()" from "This example shows how to use the ezcBaseFile::findRecursive() method:" does not point anywhere, is that normal ? - Do you think you can add some syntax coloring to the PHP code so it is easier to read ? Other than that, the website looks good, I especially love the new logo, who created it ? Cheers :) -- Jérôme Renard http://39web.fr | http://jrenard.info
Re: [zeta-dev] Proposal: ezcWorkflow CouchDB Backend
On Tue, 2010-07-27 at 09:52 +0200, Benjamin Eberlei wrote: > Hey Paul, > > i already have a buggy and untested prototype of the CouchDB backend > that is as small as 300 loc. I think an additional abstraction of the > document > layer may only complicate the implementation or just lead to all API > methods being delegated to yet another backend. Its probably easier to > just have an additional ezcWorkflowMongoTiein that is equally thin. I second this - especially because of the quite fundamental differences between CouchDB and MongoDB it sounds more feasible to write another driver / tiein for that. I like the idea of storing the workflows in CouchDB very much - as you know I might have a usecase for that in the near future, too :). I can't gauge your design decisions regarding the implementation, though - since I just don't know enough about the Workflow component. Kind regards, Kore -- Kore Nordmann(GPG 0xDDC70BBB) - What I do: http://kore-nordmann.de/portfolio.html - Motivate me: http://wishlist.kore-nordmann.de/ signature.asc Description: This is a digitally signed message part
[zeta-dev] Website
Hi, As you know I was working on the new website for the zeta components. I just regenerated it - the API documentation now contains proper links to the fisheye source code browser. The website is available for preview here: http://zeta:z...@zeta-components.org/news.html The repository containing the website and the generation scripts is available at: svn://svn.qafoo.com/zeta-website The full Checkout is about 256MB and contains about 26k files - the API documentation generates quite some HTML files (and for now it is only generated for trunk/). Afaik it considered best practice to commit the HTML to the project repository and the website will then be deployed to the Apache HTTP mirrors. I would prefer to commit the whole repository contents to "/website", so that everybody can easily regenerate the website. (Makefile and docs are included). Do you second this? This would mean, that "/website/htdocs" would then be mirrored to the Apache web servers (which is, without the .svn dirs, around 50MB). Kind regards, Kore -- Kore Nordmann(GPG 0xDDC70BBB) - What I do: http://kore-nordmann.de/portfolio.html - Motivate me: http://wishlist.kore-nordmann.de/ signature.asc Description: This is a digitally signed message part
