[kdewebdev-site] Things to do

[Eric Laffoon]

Hi all,
let me preface this do list. First off I seem generally sleep deprived and 
ready to tell the world to get lost. I'm going to start back to weekends at 
the Saturday Market and I have a bug in some very complex PHP in my order 
system at kittyhooch.com that I have as yet not been able to reproduce... and 
it randomly shows up more or less. Because of this I have been postponing a 
push that could be a sizable income jump. I'm not going to start another year 
or work without resolving this. Between that and other things I really need 
to try to limit my exposure here for a week or so. Regardless I wanted to get 
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. When we do we will be working on the 
new and improved architecture and transfering files. Once we're happy the new 
XML file management and all is good we will move the DNS pointer. In the mean 
time I want to get work done, but we do want to keep in mind that we will be 
changing and moving things soon.

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 (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. 
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
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.
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
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.
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.
6) Developer area - the project developer stuff I need to work on with data 
management foundations and then get people involved, so hold off on that for 
the time being.
7) Site development help - I believe we should put up some persistent 
information for working on the site. Several options are available, but my 
thinking is that we don't need to do a public page. At the same time we don't 
really need to do anything on site at all as we can simply add an HTML/PHP 
section that we don't post but put in CVS. This will enable anyone to look at 
this if they have a site checkout. I will take recent posts for setting up 
CVS and make this available as a link when setting up new accounts.

I have had several interruptions trying to write this and haven't gotten 
through my other morning emails and it's well into the afternoon. I can't 
remember the rest of what I had to say. Rule one is common sense applies. ;-) 
We do need to work on some standardization ideas, but previously this was a 
roadblock on the list so I'm not going to get into absurd minutia, but 
consistent approach is useful.

Currently I'm the only one set up to upload. I don't think that's a problem 
because I can always upload within 12 hours. However I plan to change this 
soon and designate others who can upload. The point is that I don't want to 
be retracting work and design that is up.

I'm sure there is more but I will post when I think of it. Most of all let's 
have fun and make a great site. We should get all areas in work so that the 
content can be directed to those who will be writing it. If you want to 
handle a certain area post the list. Also don't forget to update your local 
CVS before committing. If you are not activated with an account and want one 
the place to go is https://kittyhooch.com/kdewebdev.php.
-- 
Eric Laffoon
Project Lead - kdewebdev module