dan sinclair wrote:
> On 25-Apr-07, at 3:05 PM, Luchezar Petkov wrote:
>> As you may noticed, I've putted some content. I need your opinion on it
>> - is it nice, are the images nice - are they too big or too small or are
>> they nice at all.
> I think their a bit on the big side. A few images are fine but I don't
> think we want to go off and add images for every single section title
> that we'll have on the site. Do we really need a performance image?
> Isn't the header good enough?
> Don't get me wrong, the images look good, we just don't want to over
> clutter the site. Ends up looking too busy.
Ok, I'll try to fix it.
>> And... About the content of the site.. We need a small plan.
>> My ideas are:
>> 2) Separate the documentation - User documentation and Developers
> This is essentially done. docs.e.org needs to be re-written but it's
> already split into sections for EFL docs, the books and the wm docs.
>> 1) Rewrite/update the user guide on get-e.org and move it in the
>> official site as user documentation. It will cover ONLY e17 itself and
>> the official modules (ibar, ibox, etc etc)
> We can cover other applications as we see fit. There is no reason it has
> to be just e17. enlightenment isn't only the wm. What about entrance or
> other applications we create. Their just as much a part of the
> enlightenment project.
>> 2) Anything that is outside of E17 itself should have it's documentation
>> on the wiki. All maintained stuff in apps/ and e_modules/. Bigger
>> projects such as Etk and Ewl can have their own web sites if wiki page
>> is not enough for them - etk.enlightenment.org, ewl.enlightenment.org or
>> with their own domains.
> This I disagree with. Enlightenment isn't just the WM. We want product
> pages for the different libs on the main site that not everyone can
> change. The currently setup works well with the libraries having a page
> under the about libraries section. This should stay. We might also want
> to add entrance or other apps as they become useful to the site.
> Adding a subdomain per library is going to get unwieldy pretty quick.
> Sure they'll all have wiki sites as well. Ewl has a lot of information
> on the wiki. We still want it on the main site.
Everything in apps/ (except E and perhaps Entrance) and in e_modules/ is
just hosted on our CVS. Anyone can write an app and host it somewhere
else. Imagine this situation: we work hardly we release E. Great. But
when people start to write modules and apps using EFL they will be using
their own places to host their work. The fact that Ephoto, Exhibit and
Extract (for example) are hosted on E CVS does not make them "special"
or essential parts of the project. They are separate projects. They are
all important because they are some of the first good and working apps
written using EFL. Nothing more. Thus, in my opinion, we have to
document their features in the wiki - as every new application that will
pop up in the future (if the author(s) wants to use E's wiki).
>> 3) Rewrite/update the current developers documentation for core EFL.
>> Libraries that are outside of core EFL should have their documentation
>> on the wiki. I can't help here, unfortunately - I'm not a hacker myself.
>> The question here is: should the themeing docs be in this section or
>> they should stay in the wiki? Should we include documentation for
> Define core EFL. Do you mean just what the WM requires as that cuts out
> a large chunk of the enlightenment code. Anything in libs, that isn't
> dead, should be game to have a section on the website.
Well, the biggest and maintained libraries can have their subdomains and
separate websites with docs, wikis and whatever you want.Etk had its
own web site, but seems that it's currently offline. But I just don't
see a reason to include, for example, Engrave - small library, not much
maintained, don't need big documentation, so a wiki page(s) perhaps will
be the proper choice for it. If you really want all working/maintained
libs documented on the site - ok, no problem. Yet, read above what I've
said about the apps and modules - imo, its the same situation with the
libs that E does not depend on.
> Themeing and translation docs should appear on the wiki as they'll
> inherently have a lot of changes.