[kdewebdev-site] Things to do

[Eric Laffoon]

On Wednesday 02 March 2005 04:42 am, Andras Mantia wrote:
> On Wednesday 02 March 2005 01:17, Eric Laffoon wrote:
> > Hi all,
> > let me preface this do list.
>
> So we should find volunteers for the items, if I'm right. ;-)

You remembered my perfect world. ;-)
>
> > some foundational things done. Now we need to do more. I will be glad
> > to work on content once our frameworks are up and we need to keep in
> > mind that we will be moving to the PHP5 server as soon as I do a few
> > things to get it ready, hopefully in the coming weeks.
>
> Anyway, we must be sure that this site works, as the move might happen
> only after 3.4.0 is released.

I changed the links in CVS to show this site... oh, server move. We will have 
the luxury of having accounts on both servers and much of what is on the 
current server is directly usable. Right now we have the luxury of doing it 
almost right and re-implementing in PHP5 older and wiser. (I'll be the 
older... 48 this month [shudder])
>
> > DO LIST - things that need done. If you're going to do something be
> > sure to read the whole email for other sections.
> > 1) Set up subdomains. I have set up a functioning Kommander
> > subdomain. We need to copy applib.php and set up a template for the
> > index page. I think the most important here is to get the quanta
>
> Right. BTW, I've created an appmenu.php (based on a code from Kommander)
> which is in kallery/public_html/include that can be used to create
> application-specific menus. This way the amount of code needed to put
> in each PHP file goes down.

I modified this in CVS but did not upload. I made it look a little less 
strange to PHP coders, ;-) cleaned up a markup aesthetic in rendering and 
added validation with the option to disable it...

I just modified it again. Let's split the file and move the main function to 
the central include and the menu array to the local applib.php right before 
this is called.
>
> > (I
> > have a masthead for it up) page up, but all of them should go up. One
> > key factor I would like to discuss, but not get bogged down on, is a
> > general subdomain menu framework. Probably secondary pages don't need
> > the main menu for the main site, only the subdomain index.
>
> A way to access the main site would be nice tough.

You mean a link just to kdewebdev.org?
>
> > There are
> > two doc links in Kommander and I need to put up a third. Ideally we
> > should have a docs link and list them there. My suggestion for
> > subdomain links is
> > main - index
> > news - archive
> > faq - common and app specific
> > screenshots - duh? ;-) (there should be a key image on the main and
> > all on application)
> > links - app specific
> > docs - all
> > resources - KNewStuff interface
>
> I'm fine with it.
>
> > 2) FAQ improvements - while this will be fully developed with
> > simplexml we can at least manage the categories and provide a link
> > section. On the main site it will include common and all application
> > faqs but at the top it will provide a link to each application area
> > faq. Application (subdomain) area faqs will only show common and
> > application specific faqs. This should be pretty easy to modify with
> > Andras' code.
>
> The code is basicly ready. Might need some touches to get exactly how
> you want.

I'll look in a bit. 
>
> > 3) screenshots - we need screenshots for each application along with
> > key shots to go on the main page which will offer a preview of all
> > applications
>
> Anybody wanting to make screenshots? Read the screenshot guide on
> i18n.kde.org. Shortly: use 75dpi (you can use Gimp after you took the
> shot to reduce the dpi), use Plastik decoration, widget theme and
> colors.
>
> > 4) News - I will be doing all the database management so
> > I will set this up as I already have a news system I use on
> > kittyhooch.com that can expire news. I will need to add categories.
> > We will show information on the latest news on the main site and
> > application index pages with more info an details on a news page. I'm
> > happy to let others design the markup for this I hope to offer the
> > data classes to expose this shortly.
>
> Ok, so we are waiting for you to put this up.

I've got to do a little database prep, but it's in work.
>
> > 5) KNewStuff - I need to read up on this at http://kstuff.org. I plan
> > on buffering submissions and I have a lot in mind for this. I also
> > think it would be good to set up a user database so it gives us the
> > option to email anyone if they have downloaded something that we
> > later find has a security problem. Anyway the application interfaces
> > can be begun now to review online similar to from Quanta and also we
> > can begin the submission pages soon, but I will be introducing data
> > management classes so we can wait for that. Also we will need
> > maintainers for KNewStuff submissions.
>
> I'm ready to help anybody with the KNewStuff part.

If nobody else steps forward I may be able to work with you on it next week.
>
> Andras