Hi,
How to run a webstie using these ReST files ?
http://codespeak.net/svn/z3/zopeweb/trunk/
I think worldcookery.com and tiks.org are running using ReST and Zope 3.
Are we planning to use any of these?
Thanks,
Baiju M
___
Zope-web maillist -
baiju m wrote:
Hi,
How to run a webstie using these ReST files ?
http://codespeak.net/svn/z3/zopeweb/trunk/
I think worldcookery.com and tiks.org are running using ReST and Zope 3.
Are we planning to use any of these?
Some thoughts on what you could do localy with the SVN checkout ::
Tonico Strasser wrote:
IMHO, the most important change for reducing visual design complexity,
is to get rid of the /Members section, including log in/log out, and the
whole TTW content management system.
I think it's much easier to add and update content with SVN. (This would
also
Chris Withers wrote:
Tonico Strasser wrote:
IMHO, the most important change for reducing visual design
complexity, is to get rid of the /Members section, including log
in/log out, and the whole TTW content management system.
I think it's much easier to add and update content with SVN.
On 2/9/06, Martijn Faassen [EMAIL PROTECTED] wrote:
I'm still hopeful we can at least swap out zope.org's frontpage and
initial pages with something better that describes both Zope 2, Zope 3,
and its relationship. Quite a bit of text is already written that
attempts that which is in codespeak
On 2/9/06, Andrew Sawyers [EMAIL PROTECTED] wrote:
On Thu, 2006-02-09 at 14:28 +0100, Lennart Regebro wrote:
But other than that, I think we should
focus on having a zope3.org.
A zope.org and zope3.org?
Yup.
--
Lennart Regebro, Nuxeo http://www.nuxeo.com/
CPS Content Management
On Thu, 09 Feb 2006 13:00:43 -, Chris Withers [EMAIL PROTECTED]
wrote:
Tonico Strasser wrote:
IMHO, the most important change for reducing visual design complexity,
is to get rid of the /Members section, including log in/log out, and
the whole TTW content management system.
I think
