Mailing List Archive

On 9/18/06, Martijn Faassen <faassen@infrae.com> wrote:
> Hi there,
>
> I started doing some work on transforming the restructured text content
> + templates into HTML pages, but I didn't get very far, and I figured
> instead I ask a volunteer.
>
> So, the task:
>
> Write code (such as a Python script) that takes the restructured text
> files (that I will send you) and wraps the layout (that I will also send
> you) around it, making the menus and such work. The result should be a
> bunch of HTML pages that can be served by Apache.
>
> If you're interested, drop me a mail.
>

I think there is already python code for doing this:

http://www.zope.org/Members/k_vertigo/Products/CMFDeployment

--
Justizin, Independent Interactivity Architect
ACM SIGGRAPH SysMgr, Reporter
http://www.siggraph.org/

"The opposite of a fact is falsehood, but the opposite of one profound
truth may very well be another profound truth."
- Niels Bohr

Am I helpful? http://rate.affero.net/justizin
_______________________________________________
Zope-web maillist - Zope-web@zope.org
http://mail.zope.org/mailman/listinfo/zope-web

> >
> > I think there is already python code for doing this:
> >
> > http://www.zope.org/Members/k_vertigo/Products/CMFDeployment
>
> Thanks. This is assuming the data is already in Zope and specifically a
> CMF site, though. I'm trying to avoid the whole technology equation for
> the time being. I don't know how long I can keep this up. :)
>

Sorry for being out of the loop, as I just joined the list yesterday.
Could you elaborate on what content you're talking about? Would it be
easier to write custom code outside of Zope to do this work than to
import some ReST content into a CMF site of sorts, i.e. Zope.org?

;)

--
Justizin, Independent Interactivity Architect
ACM SIGGRAPH SysMgr, Reporter
http://www.siggraph.org/

"The opposite of a fact is falsehood, but the opposite of one profound
truth may very well be another profound truth."
- Niels Bohr

Am I helpful? http://rate.affero.net/justizin
_______________________________________________
Zope-web maillist - Zope-web@zope.org
http://mail.zope.org/mailman/listinfo/zope-web

Justizin wrote:
> On 9/18/06, Martijn Faassen <faassen@infrae.com> wrote:
>> Hi there,
>>
>> I started doing some work on transforming the restructured text content
>> + templates into HTML pages, but I didn't get very far, and I figured
>> instead I ask a volunteer.
>>
>> So, the task:
>>
>> Write code (such as a Python script) that takes the restructured text
>> files (that I will send you) and wraps the layout (that I will also send
>> you) around it, making the menus and such work. The result should be a
>> bunch of HTML pages that can be served by Apache.
>>
>> If you're interested, drop me a mail.
>>
>
> I think there is already python code for doing this:
>
> http://www.zope.org/Members/k_vertigo/Products/CMFDeployment

Thanks. This is assuming the data is already in Zope and specifically a
CMF site, though. I'm trying to avoid the whole technology equation for
the time being. I don't know how long I can keep this up. :)

Regards,

Martijn


_______________________________________________
Zope-web maillist - Zope-web@zope.org
http://mail.zope.org/mailman/listinfo/zope-web

Hi Martijn,

I'm using ZopePagetTemplates with mod_python and apache to serve rest
files as html pages in a template wrapper. It would be little problem to
adapt the code to do the task as you have requested.

I'm volunteering.

Best regards,
Darryl

On Mon, 2006-09-18 at 15:00 +0200, Martijn Faassen wrote:
> Hi there,
>
> I started doing some work on transforming the restructured text content
> + templates into HTML pages, but I didn't get very far, and I figured
> instead I ask a volunteer.
>
> So, the task:
>
> Write code (such as a Python script) that takes the restructured text
> files (that I will send you) and wraps the layout (that I will also send
> you) around it, making the menus and such work. The result should be a
> bunch of HTML pages that can be served by Apache.
>
> If you're interested, drop me a mail.
>
> Regards,
>
> Martijn
> _______________________________________________
> Zope-web maillist - Zope-web@zope.org
> http://mail.zope.org/mailman/listinfo/zope-web

_______________________________________________
Zope-web maillist - Zope-web@zope.org
http://mail.zope.org/mailman/listinfo/zope-web

On Tue, Sep 19, 2006 at 08:31:28AM +1200, Darryl Cousins wrote:
| Hi Martijn,
|
| I'm using ZopePagetTemplates with mod_python and apache to serve rest
| files as html pages in a template wrapper. It would be little problem to
| adapt the code to do the task as you have requested.

And don't forget rest2web.
http://www.voidspace.org.uk/python/rest2web/

--
Sidnei da Silva
Enfold Systems http://enfoldsystems.com
Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214
_______________________________________________
Zope-web maillist - Zope-web@zope.org
http://mail.zope.org/mailman/listinfo/zope-web

Justizin wrote:
>> >
>> > I think there is already python code for doing this:
>> >
>> > http://www.zope.org/Members/k_vertigo/Products/CMFDeployment
>>
>> Thanks. This is assuming the data is already in Zope and specifically a
>> CMF site, though. I'm trying to avoid the whole technology equation for
>> the time being. I don't know how long I can keep this up. :)
>>
>
> Sorry for being out of the loop, as I just joined the list yesterday.
> Could you elaborate on what content you're talking about? Would it be
> easier to write custom code outside of Zope to do this work than to
> import some ReST content into a CMF site of sorts, i.e. Zope.org?

I just have restructured text files which need to be wrapped into a
template with navigation, turning them into HTML pages, which then need
to be published, somehow, on zope.org.

Regards,

Martijn

_______________________________________________
Zope-web maillist - Zope-web@zope.org
http://mail.zope.org/mailman/listinfo/zope-web

Darryl Cousins wrote:
> I'm using ZopePagetTemplates with mod_python and apache to serve rest
> files as html pages in a template wrapper. It would be little problem to
> adapt the code to do the task as you have requested.
>
> I'm volunteering.

Great! I had Michael Haubenwaller also express interest, so I'll cc him.
I'll be assuming you two work out who does what. It think Michael
wouldn't mind if you just took on the job yourself anyway - just let me
know.

I'll be sending you a mail with the stuff I have right now. The text
isn't done yet, but you should get an idea. I'd be happy to indicate
navigation structure by directory structure for the time being, but you
may have better ideas.

Regards,

Martijn
_______________________________________________
Zope-web maillist - Zope-web@zope.org
http://mail.zope.org/mailman/listinfo/zope-web

Cheers Martijn,

I've put everything you gave me `as is` into my little zpt/mod_python
application and this comes out:

http://zf.tfws.org.nz/

I've only just now updated dns for the subdomain (you may need the
nameservers I use if its not showing up for you yet):

nameserver 66.199.228.130
nameserver 206.123.113.132

All the doc pages you sent me are available as

http://zf.tfws.org.nz/ is homepage.txt
http://zf.tfws.org.nz/structure.html
http://zf.tfws.org.nz/about.html
http://zf.tfws.org.nz/documents.html
http://zf.tfws.org.nz/join.html
http://zf.tfws.org.nz/projects.html
http://zf.tfws.org.nz/membership.html

Notes:

Background logo image isn't lining up on firefox
rest error on structure.html

The code is on svn:

svn co svn://treefernwebservices.co.nz/var/svn/zopefoundation/trunk/www

Please email me privately for write access.

I'm not clear on a couple of points:

1. Directory and navigation structure for the site.
2. How does 'upload to zope.org' work?

Sincere regards,
Darryl

On NZT so I'm off to bed.

On Tue, 2006-09-19 at 12:34 +0200, Martijn Faassen wrote:
> Darryl Cousins wrote:
> > I'm using ZopePagetTemplates with mod_python and apache to serve rest
> > files as html pages in a template wrapper. It would be little problem to
> > adapt the code to do the task as you have requested.
> >
> > I'm volunteering.
>
> Great! I had Michael Haubenwaller also express interest, so I'll cc him.
> I'll be assuming you two work out who does what. It think Michael
> wouldn't mind if you just took on the job yourself anyway - just let me
> know.
>
> I'll be sending you a mail with the stuff I have right now. The text
> isn't done yet, but you should get an idea. I'd be happy to indicate
> navigation structure by directory structure for the time being, but you
> may have better ideas.
>
> Regards,
>
> Martijn
> _______________________________________________
> Zope-web maillist - Zope-web@zope.org
> http://mail.zope.org/mailman/listinfo/zope-web

_______________________________________________
Zope-web maillist - Zope-web@zope.org
http://mail.zope.org/mailman/listinfo/zope-web

Hey Darryl,

Darryl Cousins wrote:

> I've put everything you gave me `as is` into my little zpt/mod_python
> application and this comes out:
>
> http://zf.tfws.org.nz/

Great! Thank you very much!

> Notes:
>
> Background logo image isn't lining up on firefox

cc-ing Tom Von Lahndorff. Darryl, which page does this occur on under
what circumstances? Which platform are you on?

> rest error on structure.html

Right, that should be easily fixed.

> 1. Directory and navigation structure for the site.

This needs to be generated; the toughest part of generating the layout.
I was hoping you'd take a look at it. :) We need to start generating
that based on our current structure, and instead of query (?foo=bar)
based links, just make them normal links. Base it on a structure of
nested directories, I'd say. Of course we don't have titles that way -
either we need a hack that lifts the title from the individual ReST
documents, or we need to provide the system with a list of titles for
the individual files somehow.

> 2. How does 'upload to zope.org' work?

As to the ReST, I want to start maintaining that in the svn.zope.org
repository.

I'm trying to figure this out. On the near term, we may just upload all
of this into a plain zope on zope.org every time we make changes.

I'm also investigating the use of Apache and just scp-ing it into an
Apache directory, but it appears the zope.org infrastructure needs work
to get there.

Finally, eventually this should be converted into CMS content for one
CMS or another. That'll take a lot of hosting infrastructure work to get
done first, though.

Regards,

Martijn
_______________________________________________
Zope-web maillist - Zope-web@zope.org
http://mail.zope.org/mailman/listinfo/zope-web

Hi All,

On Wed, 2006-09-20 at 11:47 +0200, Martijn Faassen wrote:
> Hey Darryl,
>
> Darryl Cousins wrote:
>
> > I've put everything you gave me `as is` into my little zpt/mod_python
> > application and this comes out:
> >
> > http://zf.tfws.org.nz/
>
> Great! Thank you very much!
>
> > Notes:
> >
> > Background logo image isn't lining up on firefox
>
> cc-ing Tom Von Lahndorff. Darryl, which page does this occur on under
> what circumstances? Which platform are you on?

Rain-check. I ran your template through `tidy`. Firefox1.5/Debian/Linux.

> > rest error on structure.html
>
> Right, that should be easily fixed.
>
> > 1. Directory and navigation structure for the site.
>
> This needs to be generated; the toughest part of generating the layout.
> I was hoping you'd take a look at it. :) We need to start generating
> that based on our current structure, and instead of query (?foo=bar)
> based links, just make them normal links. Base it on a structure of
> nested directories, I'd say. Of course we don't have titles that way -
> either we need a hack that lifts the title from the individual ReST
> documents, or we need to provide the system with a list of titles for
> the individual files somehow.

Yup,

index.html
- docs/
----index.html
----other-docs.html
- foo/
----index.html
----other-foo-docs.html
- other-home-directory-docs.html

Thats the structure we are aiming at?

I agree, titles we can lift from the rest text file.

>
> > 2. How does 'upload to zope.org' work?
>
> As to the ReST, I want to start maintaining that in the svn.zope.org
> repository.

Yup. Some script could be run to synchronize the different components:

rest.svn.zope.org -> zf.www.rest --> zf.tfws.org.nz --> [wget?] -->
zope.org

Worst of the worse, we keep in touch and I syncronise it manually. Not a
big job.

And later, do it all with zope3 :-D

> I'm trying to figure this out. On the near term, we may just upload all
> of this into a plain zope on zope.org every time we make changes.

Unsure of meaning: `a plain zope`. ??

> I'm also investigating the use of Apache and just scp-ing it into an
> Apache directory, but it appears the zope.org infrastructure needs work
> to get there.

Keep me posted.

> Finally, eventually this should be converted into CMS content for one
> CMS or another. That'll take a lot of hosting infrastructure work to get
> done first, though.

Keep core/source data in directory/restfile then anything is possible.
Keep it simple. I think that any reasonable cms will be able to import
the structured data and generate a site using a given template.

Regards,
Darryl

> Regards,
>
> Martijn

_______________________________________________
Zope-web maillist - Zope-web@zope.org
http://mail.zope.org/mailman/listinfo/zope-web

Darryl Cousins wrote:
[snip]
>
> index.html
> - docs/
> ----index.html
> ----other-docs.html
> - foo/
> ----index.html
> ----other-foo-docs.html
> - other-home-directory-docs.html
>
> Thats the structure we are aiming at?

That's the generated structure. Something like:

foo.txt
bar.txt
baz
index.txt
qux.txt
hoi
index.txt
dag.txt

would become:

foo.html
bar.html
baz
index.html
qux.html
hoi
index.html
dag.html

Possibly ripping off the .html everywhere to turn it into:

foo
bar
baz
index
qux
hoi
index
dag

>>> 2. How does 'upload to zope.org' work?
>> As to the ReST, I want to start maintaining that in the svn.zope.org
>> repository.
>
> Yup. Some script could be run to synchronize the different components:
>
> rest.svn.zope.org -> zf.www.rest --> zf.tfws.org.nz --> [wget?] -->
> zope.org
>
> Worst of the worse, we keep in touch and I syncronise it manually. Not a
> big job.

not sure what these components all do, but some script that checkso ut
the rest from svn.zope.org, runs it through your generator, and uploads
the HTML and images up onto zope.org.

> And later, do it all with zope3 :-D

Yeah, Zope 3 or whatever. I'm trying to avoid us from geeking out on the
tech and focusing on the immediate tasks. :)

>> I'm trying to figure this out. On the near term, we may just upload all
>> of this into a plain zope on zope.org every time we make changes.
>
> Unsure of meaning: `a plain zope`. ??

Oh, zope.org has some odd variety of Plone, but normal Zope 2 stuff
still works in areas, including the /foundation part. So we could simply
upload them as page templates into the zope. I'd prefer it if it were
something simpler, but that might be easiest given the infrastructure.

[snip]
>> Finally, eventually this should be converted into CMS content for one
>> CMS or another. That'll take a lot of hosting infrastructure work to get
>> done first, though.
>
> Keep core/source data in directory/restfile then anything is possible.
> Keep it simple. I think that any reasonable cms will be able to import
> the structured data and generate a site using a given template.

Yes, keeping it simple and in ReST for now is my goal. Eventually we may
need some forms though: "join the foundation!" but we can make do with
email addresses for now.

Regards,

Martijn

_______________________________________________
Zope-web maillist - Zope-web@zope.org
http://mail.zope.org/mailman/listinfo/zope-web