[kdewebdev-site] HTML->PHP

[Eric Laffoon]

On Wednesday 23 February 2005 03:06 pm, Andras Mantia wrote:
> Hi,
>
>  I've also converted the about.html to about.php, and improved the left
> menu PHP, so it contains more variables and those are used in the other
> php files to have a consistent menu. The content is not changed.
>  I also forgot to tell, that the FAQ XML can have now HTML tags inside,
> the only rule is that you cannot have single tags (except <br />).
>  The modified version is at the URL I posted in the other mail.
>
> Andras

This is all up. Thanks Andras. Now... for the other useful stuff. First off 
there is a lot not being used in here that doesn't have to be used right now, 
but it would be nice to at least add the data. In particular -
    <maintainer name="name" email="email" />
    <category name="category" />
    <product name="product" />
It would be nice to fill in these. I'm going to make some suggestions with a 
forward looking view.
1) maintainer - pretty obvious
2) category - I suggest we allow for more than one like so
<category>
  <area>Editing</area>
 <area>installing from source</area>
</category>
3) product -> application

Okay, now for some fun. There are two things the present themselves and Dave 
and I had discussed this. For one there will be common and application 
specific information. Andras asked a question on this and the easiest way to 
manage this is to centralize it and then catgorize it. So we should comment 
sections as follows
<!-- common -->
<!-- quanta -->
etc...
For available areas we should add them like so...
<!-- quanta -->
<!-- install | editor | projects | etc... -->
Optionally we might provide the areas in XML instead. Ideally this may go into 
the PHP5 version where it's easier. Here are the two benefits.

Site - we can show a FAQ on the subdomains for common and application specific 
items. When the list is long we could also offer filtering of all or a 
particular area for an application.
Users - I can create a Kommander dialog that will generate the XML framework 
filled in and deposit it in an email ready to send using DCOP. We can offer 
the Kommander file on site and people can click it which will open the dialog 
(with appropriate warnings of course)