Lyle is on the rampage again..............
Welp, the idea was a good one about the split layout for CVS. I'd been
thinking more and more
about splitting the site but hadn't come up with a good way to get the
put in place, so your mail was great.
So great, in fact, that I implemented it tonight. The directory
structure, or basics of it is there.
This will allow all of us to move things here and there into the new
scheme at our leasure.
But here's what we need at the moment, and your the best man for the
We need the current page build system to be migrated to the new layout, lest
we end up having to maintain headers on ever single file. Anything related
to the look of the site needs to be "ported" over so we can move pages.
If you can't
do it, I will, but you'd be much faster than I would. Besides that,
you'll need to start
considering any changes that need to happen to your scripts to update
the site from CVS.
I figure it's gonna take us acouple weeks to get the new split site
setup, so this'll give us
some room to play alittle bit without f'ing up the main site.
Lyle Kempler wrote:
>Like Tim, I've been sick the last few days, and I'm still not all the
>way well. So I'm a little more behind on this than I would normally be.
>* Ben Rockwood (benr@...) wrote:
>>- Get the "old" people off the team page. This is something I'd prefer
>>if term did, since I think he'd get less flack for any removals.
>Are there any other people we haven't already removed that need
>>- Rehash the "Features Page", which is currently for DR16. It's a
>>boring page... needs to be alittle more "peppy"
>>- Possibly rehash the Screenshots page..... needs more variety and DR16
>>vs DR17 shots need better seperation, logically.
>>- Partly to solve the two above problems, create a new navbar heading
>>for DR16. Then seperate all DR16 info to one place and DR17 to another.
>> Possibly have duplicate pages running for, say, Doc's, Screenshots,
>>Features, etc..... This way its more clear to visitors what they are
>>looking at. This will also make things alittle cleaner. Downside is
>>you have a basically "split" page, but I think it would work.
>>- Add a URL icon (i don't know what their called, the icons that apper
>>next to the URL in the URL bar). I've shrunk the SunnyE icon before to
>>do this but it lost definition at 16x16pixels.
>>- Add the themes page for DR16..... mostlikely just screen shots and
>>links to other places to get 'em, to reduce management on our end.
>>- I've gotta redo the Ebony windowshot image... since the interface has
>A few comments :) (some directed at later posts):
>- I'd like to split much of the content by enlightenment version, e.g.
> A little explaining..
> a) When I don't have the page name at the end of the URL, I'm implying
> there's an index.html page there.
> b) We're really spanning multiple releases here, and separating (as
> suggested by several people) is a good idea. I'm separating really into
> 4 groups right now:
> 1) Obsolete - stuff we're mostly keeping around for fun. DR13 stuff,
> for example.
> 2) dr16 - this really should be where users are directed at since E17
> is *not* for end-users.
> 3) dr17 - right now what a lot of effort is aimed at (and arguably,
> the fun stuff :)
> 4) libraries - things we write that make a lot of sense for other
> projects to use.
> The rule of thumb as to whether something we right now a "E17
> component" and a "library" is how it's really designed. imlib2 is
> clearly not focused on E17, and it's a library, so it goes under
> libraries. Edb, though, isn't terribly useful to other projects so
> much as it just gives E17 a particular db interface. Essense aims at
> being a tight fit with E17, and is an application anyway. Etc.
> c) Anyone that's talked to me about web stuff on irc knows how I think
> content is really important, and this layout shows that. We have
> some guides floating around for both E16 and E17, and I think we need
> to have some other guides, like for E16's eesh (which is great to
> have around, but most people are confused by).
> d) Most of the non-project-specific stuff stays at the top level.
> e) I'm not sure what to do with the team page. We could divide the names a
> dozen different ways, by project (www, e16, e17, libraries, component),
> or not at all.
> f) This would make translation a little simpler, since it can be more
> easily compartmentalized.
> To preserve the histories, I'd have to ask the sourceforge people to
> move some of the pages around. Not many.. just a few, I think.
> I really want feedback about this.. comments?
>- Please ignore the front page, guys. Concentrate on what's behind it. Most
> people read the front page one time, and what to put there becomes
> clear when the rest of the site is there.
>- Please stop making wholesale copies and making multiple page changes
> that are hard to notice. Instead, please make changes one page (or one
> set of pages if the changes are all very, very similiar), and then
> post a diff of the changes, either as an attachment, or at a URL. It's
> really tough to notice some of the more subtle changes without loading
> the original and the new up and looking at it line by line sometimes.
> It will help us track what is going on and we won't end up with 5 new
> versions of the same page, none of which are in CVS.
>- You'll probably save a bit of time (and maybe some frustration) if you
> suggest a stylistic change to the list before making any actual
> changes to a local copy or CVS. We have a style laid out, and I'm sure
> there's room for improvement, but (and this goes to the multiple local
> copies thing), don't feel compelled to make some changes unless
> someone asks to see what the changes would look like. Of course, if
> making those changes helps you formulate what you want to change, go
> right ahead.. but we had this problem with the first group, where
> we nearly had a finished style, and people were still going off and
> making successive changes and not waiting for feedback, an okay from
> the rest of the people, etc. It doesn't work; don't do it. ;)
>- I actually wrote out an assignments page (which is where the original
> team page came from) for the web page. At one time there were ~20
> people on it, 3-4 of which did anything web-related. If you want to
> work on something, start on it, and when you make progress, let us
> know. But make sure you let us know when you have something to show --
> anything reasonable -- don't try to redo a whole section before
> presenting any of it, because someone else might be working in there,
> and we'd all be better off if you coordinated with them. You know?
> This is actually informally how things have been working the last 2
> weeks. It's great. Let's keep it up.
>- This happened before, so.. this is not a competition. We shouldn't be
> territorial except to ensure things are consistant and
> professional-looking. We're all here for the same purpose, and so
> _please_ do not get offended if something you suggest doesn't make it
> to the site. It's not personal! Just keep working, and try to
> understand why it was rejected, so your next piece of work will
> definately make it in. :)
>>- The download page needs new seperaters. Some kind of section
>>seperator needs to be used other than hardrules... the page just feels
>Yeah, I'd like to follow what we have above.. basically the download
>page should be laid out like we'd lay out our ftp archive, basically..
>== old ==
>dr13, eplus, etc.
>== libraries ==
>imlib2, efsd, etc
>== e16 ==
>libraries (imlib1, fnlib, etc)
>== e17 ==
>Since we're going to use sf's download stuff, we should follow their
>convention for the individual parts, e.g.
>imlib2 (release, v1.0.4) [Source]
> Linux [i386 tar] [i386 deb] [i386 rpm]
> [alpha tar] [alpha deb] [alpha rpm]
> FreeBSD [i386 tar]
> Solaris [x86 pkg] [sparc64 pkg]
> IRIX [mips tar]
>etc. The "release" part would either be "release" or "snapshot".
>Something like that..
>>- I'd like to remove the direct download links from the nav bar, and the
>>debian link.... debian shouldn't be any more important than FreeBSD or
>>Solaris, it doesn't need its own link. (this is political, thus I
>>haven't done the 2 second change)
>I agree. Let's move all of that to the download page (I just noticed
>that being there, when did that arrive? :)
>>- The front page isn't really very cozzy.... it needs better
>>organization and should draw the user into the site to explore more. My
>>previous attempts to fix this failed, so I'm probly not the person to do
>>this...... screenshots on the frontpage would probly be good.
>Like I say above, I'd really like to avoid playing with this right now.
>It's a really big distraction and we're only going to have to change it
>again later. :)
>>And of course, I'm leaving all the big doc efforts (tutorials, manuals
>>and faqs) off the list..... this is all the "little" stuff.
>Ironically, given the track record for this stuff getting done, I
>consider it the most important work right now. This stuff has been
>sorely missing for a long time.. we need to give this attention.
>Thanks to everyone that's helping out. We're just getting started, so
>let's keep the momentum. :)
>Enlightenment-web mailing list