Re: perl.apache.org / apache.perl.org
Nathan Torkington wrote: >>cvs where? it has to stay at perl.apache.org I believe. >> > > Didn't you say that the current site is maintained with CVS? Just > make a subdirectory /new and put the new site into that. Work from > there. ok >>Also what components framework have you used, is it Mason? Is it a >>static page or dynamic? >> > > All static right now. If there's a system (e.g., Mason) being used > where it's hosted, someone else should componentize it. > > I agree the order should be: > * componentize > * colorize > * contentize > > (You can tell I'm getting comfortable with management by the way I > hold down the English language and give it some good hard back door > action with all the "-ize"s) > > >>But it'd be nice to give some good web-designer do some brushing, no >>offense Nat :) We can show it on the modperl list and ask for a better >>look and feel from those who know how. >> > > I've heard nothing back except from you and Ken. If nobody offers to > tone down the colour, it's going to stay bright and gaudy. that's why I've suggested to send this to modperl list, where you have people with time on their hands. ok, you got me, I've to setup the code for generating mod_perl 2.0 docs and I was postponing this trying to do some coding first, but I'll try to implement it now. Since I plan to move to use template toolkit, I'll create a components system for the site as well. Since we have to login and update the checked out copy of perl.apache.org anyway, I see no reason why not to run a script that will run 'cvs up' and run ttpage to update all the components. Any objections to this? Once I'm done, I'll throw a few pages in for your observation and from there on we can start working on making a nice look-n-feel. Of course I'll take the work that you've done already. Can you please send me the pages (privately) you've done already? _ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
Re: perl.apache.org / apache.perl.org
Stas Bekman writes: > Though I prefer mild colours, not shouting ones. I use the site all the > time, and I don't need to be shouted at. May be we want a splash page > just for some entrance page, which those who use the site daily don't > have to see. I like the colours at use.perl.org and even more the ones > used by http://freshmeat.net/. Splashpages are a crime against nature. I'll leave the colors to someone who can see them :-) > cvs where? it has to stay at perl.apache.org I believe. Didn't you say that the current site is maintained with CVS? Just make a subdirectory /new and put the new site into that. Work from there. > Also what components framework have you used, is it Mason? Is it a > static page or dynamic? All static right now. If there's a system (e.g., Mason) being used where it's hosted, someone else should componentize it. I agree the order should be: * componentize * colorize * contentize (You can tell I'm getting comfortable with management by the way I hold down the English language and give it some good hard back door action with all the "-ize"s) > But it'd be nice to give some good web-designer do some brushing, no > offense Nat :) We can show it on the modperl list and ask for a better > look and feel from those who know how. I've heard nothing back except from you and Ken. If nobody offers to tone down the colour, it's going to stay bright and gaudy. Nat
Re: perl.apache.org / apache.perl.org
Nathan Torkington wrote: > Ken Williams writes: > >>Not that I dislike them - the current colors let me look at the page >>for a few seconds, then shut off the monitor and read the text while >>staring at a blank white sheet of paper. >> man, that was so strong, I thought I've hit some wrong link :) > I'm impressed that you suffered such intense retinal distress and > never made the logical deduction that I'm colour-blind. (I am :-) > > In many ways the colours are the last-important part, but I like the > idea of having something bright to catch attention. if you can define them in one place, like CSS, that's true, otherwise it's pain to maintain. Though I prefer mild colours, not shouting ones. I use the site all the time, and I don't need to be shouted at. May be we want a splash page just for some entrance page, which those who use the site daily don't have to see. I like the colours at use.perl.org and even more the ones used by http://freshmeat.net/. >>In any case, I like the organizational scheme you've got. Having >>everything on a single page was a pain in the butt. > > Glad to hear it. If nobody objects to the structure, we could put it > into CVS and open it up for others to work on. If I'm the only one > working on it, it'll take far too long. Does this sound the right > time for CVS? cvs where? it has to stay at perl.apache.org I believe. Also what components framework have you used, is it Mason? Is it a static page or dynamic? Otherwise it's good to have someone to push for a change, I think I'll help with the content once we figure out the skeleton. But it'd be nice to give some good web-designer do some brushing, no offense Nat :) We can show it on the modperl list and ask for a better look and feel from those who know how. _ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
Re: perl.apache.org / apache.perl.org
Ken Williams writes: > Not that I dislike them - the current colors let me look at the page > for a few seconds, then shut off the monitor and read the text while > staring at a blank white sheet of paper. I'm impressed that you suffered such intense retinal distress and never made the logical deduction that I'm colour-blind. (I am :-) In many ways the colours are the last-important part, but I like the idea of having something bright to catch attention. > In any case, I like the organizational scheme you've got. Having > everything on a single page was a pain in the butt. Glad to hear it. If nobody objects to the structure, we could put it into CVS and open it up for others to work on. If I'm the only one working on it, it'll take far too long. Does this sound the right time for CVS? Nat
Re: perl.apache.org / apache.perl.org
Nathan Torkington <[EMAIL PROTECTED]> wrote: > There are some web design To Do items: > * ensure colors are part of the standard palette (right now they're >just easy to type in hex :-) Holy shit Nat, those colors are strong. =) You've really taken attention-getting into the twenty-first century! Not that I dislike them - the current colors let me look at the page for a few seconds, then shut off the monitor and read the text while staring at a blank white sheet of paper. In any case, I like the organizational scheme you've got. Having everything on a single page was a pain in the butt. -Ken
Re: perl.apache.org / apache.perl.org
Ask Bjoern Hansen writes: > > I'll chew on a new layout and give you something by the end of the > > week. Thanks, > > awesome! :-) I did have something by the end of last week, just not much. I'd hoped to find the time to plug the holes this week, but haven't been able to. So here it is, woefully incomplete. The URL is: http://c1853353-a.ftclns1.co.home.com/~gnat/modperl/ I've got: * Home page * About * Download done. My plan was to just go through perl.apache.org and move content into that framework (for instance, success stories and testimonials go as a page under 'About'). There are some web design To Do items: * ensure colors are part of the standard palette (right now they're just easy to type in hex :-) * contemplate CSS and enforcing standards like "all links are in bold". Nat
Re: perl.apache.org / apache.perl.org
Before I forget to say anything: Ask, haven't you set up a basic Mason framework for the *.perl.org sites that an apache.perl.org could just piggyback onto? Stas, I think that was why Nat suggested Mason - not that using Mason would necessarily make anything better itself, but that we could get some leverage from the other *.perl.org sites, and it could be ultimately less work and less maintenance and look better without much effort. Nathan Torkington <[EMAIL PROTECTED]> wrote: > Stas Bekman writes: >> Everything is under CVS, and if somebody wants to come and give a >> hand to redo the site, there is no problem to give a cvs access to >> this person. > > I'll chew on a new layout and give you something by the end of the > week. Thanks, > > Nat >
Re: perl.apache.org / apache.perl.org
Ken Williams wrote: > Before I forget to say anything: > > Ask, haven't you set up a basic Mason framework for the *.perl.org sites > that an apache.perl.org could just piggyback onto? Stas, I think that > was why Nat suggested Mason - not that using Mason would necessarily > make anything better itself, but that we could get some leverage from > the other *.perl.org sites, and it could be ultimately less work and > less maintenance and look better without much effort. Well, I don't know how the *.perl.org sites are maintained. Are they under cvs control for their source files? I have nothing against Mason, the only concerns are being able to control source files without cvs control and I'm not sure how will it work with ASF project being hosted at perl.org. > Nathan Torkington <[EMAIL PROTECTED]> wrote: > >> Stas Bekman writes: >> >>> Everything is under CVS, and if somebody wants to come and give a >>> hand to redo the site, there is no problem to give a cvs access to >>> this person. >> >> >> I'll chew on a new layout and give you something by the end of the >> week. Thanks, >> >> Nat >> > -- _ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
Re: perl.apache.org / apache.perl.org
On Mon, 8 Oct 2001, Nathan Torkington wrote: > Stas Bekman writes: > > Everything is under CVS, and if somebody wants to come and give a > > hand to redo the site, there is no problem to give a cvs access to > > this person. > > I'll chew on a new layout and give you something by the end of the > week. Thanks, awesome! :-) -- ask bjoern hansen, http://ask.netcetera.dk/ !try; do();
Re: perl.apache.org / apache.perl.org
Stas Bekman writes: > Everything is under CVS, and if somebody wants to come and give a > hand to redo the site, there is no problem to give a cvs access to > this person. I'll chew on a new layout and give you something by the end of the week. Thanks, Nat
Re: perl.apache.org / apache.perl.org
On Sun, 7 Oct 2001, Stas Bekman wrote: > We have had two new designs worked out long time ago, > but one has been picked by take23.org and the other > wasn't applied. (hi brian) :( sorry! i have this tendency to bite off more than i can chew. i have 10 projects and none of them will ever be finished. > What I want to say, is that it's not a point of where to > host the site. The point is that we need someone to do > the job of re-doing and making it easy to maintain the > site, to keep it nice. jim's design is still available if somebody wants to use it.
Re: perl.apache.org / apache.perl.org
On Sun, 7 Oct 2001, Stas Bekman wrote: > can you please post the URL again? thanks! http://thisishomemade.com/for/modperl/site/ like he said before, it's really just a reorganization of the available information, rather than a complete site architecture with fancy rollover navigation, huge menu bars, swooshes and swirls. what with mp2 and what not, it may be that this design's time has passed.
Re: perl.apache.org / apache.perl.org
brian moseley wrote: > On Sun, 7 Oct 2001, Stas Bekman wrote: > > >>We have had two new designs worked out long time ago, >>but one has been picked by take23.org and the other >>wasn't applied. (hi brian) >> > > :( > > sorry! i have this tendency to bite off more than i can > chew. i have 10 projects and none of them will ever be > finished. that's ok... we are all in the same boat :) >>What I want to say, is that it's not a point of where to >>host the site. The point is that we need someone to do >>the job of re-doing and making it easy to maintain the >>site, to keep it nice. >> > > jim's design is still available if somebody wants to use it. can you please post the URL again? thanks! _ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
Re: perl.apache.org / apache.perl.org
[CC'ing modperl-site where this discussion really belongs to] Nathan Torkington wrote: > This site is hosted on an apache.org box. Any chance we could host it > at perl.org and built a pretty-looking Mason site for the content > that's already there? Then we could open it up with CVS for others to > commit changes and updates to. > > I'm sick of the website making modperl look like the bastard stepchild > of the Apache project. Hi Nat, It's not a bastard stepchild of the Apache project. It's an ASF project. The fact that nobody handles the website has nothing to do with ASF. We have had two new designs worked out long time ago, but one has been picked by take23.org and the other wasn't applied. (hi brian) Everything is under CVS, and if somebody wants to come and give a hand to redo the site, there is no problem to give a cvs access to this person. What I want to say, is that it's not a point of where to host the site. The point is that we need someone to do the job of re-doing and making it easy to maintain the site, to keep it nice. That's said I don't see any reason to use Mason or other dynamic tools, since 99,9% of the content is static. I'd think more about Template Toolkit's ttpage tool, which produce a static version of the site, based on dynamic pages. One important point of keeping perl.apache.org under apache.org is that at some point, mirrors will work again, and that will be very handy to have the site under apache.org. _ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
