-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Whoa there - let's not get carried away with "wants to". There's a need, and I'm willing - but if there's someone out there with a doc-fettish I'm more than willing to step aside. :-)
Does my theory of two sites appeal to anyone else? Being under Apache has benefits, but being restricted to static sites isn't what I'd consider one of them. Combine that with two (or more) levels of support - - the personal / consultant level, and the component / ide / product and you start wondering when someone can check the code in to modify the site. Get's kinda bogged down in the meat of the framework. Just got your response about testng... I definitely see two different beasts. As should be apparent, I'm not married to either approach - only an approach that does the most for both Tapestry (the framework) and Tapestry Support (consultants, components, powered by's, products). I'd like new users to be able to glide into working with it, and more experienced users to find what they're looking for easier. Jesse Kuhnert wrote: > Yeah, the content does need to be re-organized quite a bit. I'm glad someone > else wants to do this as well :) > > The design part of things I believe we have covered now, so if we can figure > out the content portions we should be in much better shape . > > On 3/28/06, Brian K. Wallace <[EMAIL PROTECTED]> wrote: > Jesse Kuhnert wrote: >>>> Ok I guess I'm a huge liar. >>>> >>>> I'd like to update the documentation so that tapestry is a little bit > more >>>> clear in what kind of outside support it has. I don't think having a > simple >>>> link is quite cutting it currently. >>>> >>>> Ideally I'd like to write up a short page about the really big items ( > like >>>> spindle, tapidea, tacos ? , trails, etc..). I may initially even try and > be >>>> lazy and ask the head of these various projects to provide the content > for >>>> these pages themselves, but where I don't get feedback will try my best > to >>>> fill in. >>>> >>>> Any objections to this? >>>> >>>> -- >>>> Jesse Kuhnert >>>> Tacos/Tapestry, team member/developer >>>> >>>> Open source based consulting work centered around >>>> dojo/tapestry/tacos/hivemind. http://opennotion.com >>>> > In the overall scheme of things, no - no objections. However... > > I think the Tapestry site itself needs a facelift. I've been quiet about > it, but I've got it on my back burner. Quite a few pages that are > nothing but placeholders for other pages. Stuff broken down in what used > to be a decent way, but now overloads the eye with "too much". This is > step two of 'fix documentation' (step one being docs to be shipped with > Tapestry itself - component docs, javadocs, etc). In fixing this, it > would be good to be able to point to "X" (as spring has both > springframework.com and .org I feel Tapestry should have "jakarta site" > and a "now we're cooking with gas" site. Each should point to the other, > but the "non-jakarta site" would be where I'd endorse "outside support" > details/links/praise/etc. > > I think these projects are highly important for Tapestry, but at present > (and perhaps after TLP would be a good time to analyze) it seems out of > place in the maze that is the Tapestry site. [Perhaps organize it so the > 'outside support' isn't relegated to small links on the bottom of an > overly crowded left nav] > > My .02 - YMMV > > Brian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) iD8DBQFEKhDSaCoPKRow/gARAuVnAJ9bgRI7UHS0ajmSRgmHq6rHT7uJHACgn3mW nBv9JtAjOL8sRml5hntMLDc= =hzZq -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
