On Dec 21, 2006, at 11:12 AM, ssteiner wrote:
but I get a ton of warnings and errors.
A bunch of:
'webhelpers.markdown hides module with same name'
Yep, that's normal.
Another bunch of:
webhelpers.textile.Textiler.table:10: (ERROR/3) Undefined substitution
referenced: "a|b|c".
That's normal as well. :)
with various "Undefined substituition..."s.
Also, since I've never actually been able to build the documentation
I'm not sure what it's supposed to look like but it doesn't appear to
have been styled at all -- no CSS, no nuthin'. All very straight,
plain, unadorned HTML with no included CSS or anything else.
Right, when we build the docs and push them to the server, the server
dynamically skins them for the PylonsHQ site. I'll have to add
another pudge template for offline building so that they can have a
full layout when not being built for the PHQ site.
The code seems to have been intended to be styled as there are class
references in the HTML that, presumably, would do something if the CSS
was properly included.
You can run a local copy of the PylonsHQ site, but I'd imagine a
plain HTML version would be the desired format.
Starting index.html in the docs/html/docs/0.9.3 gives the basic front
page and all the links work except that the link to WebHelpers Module
Reference is broken.
There are a ton of other html files spewed into the same directory but
none are linked to by the main index.html. These all can be opened
and
render without decoration of any form.
I'm not sure what this is all supposed to look like but I doubt
this is
it...
It is for the most part actually, since the site is doing the
skinning. It's taking advantage of a Myghty ability called automatic
inheritance so that all the files will properly pull in the skin.
There's files that are referenced by the module docs, and the main
directory that is referenced by index. As you noticed, there's also
some docs that are in Pylons docs/ tree that are not linked to from
index, these are generally 'under development' and not ready for
prime-time. They probably need to be cleaned out if they're no longer
being worked on, thanks for noticing that. :)
I'll ping the other devs to ask if they have any 'dead' docs in there
that should be removed.
Cheers,
Ben
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---
