IMHO: we must not rely on "traditional" or "simplest" solutions for the WEB content to provide wide use of the NetBeans
in the WEB development, including the development based on PHP. Yes, a solution with html and css is frequently used in
the WEB development for simplest sites. And, of course, it will be useful to always see proposals for both html and css
in the list of the preferred templates if a user's project is actually based on such solution. But, if a user makes a
decision to use another basis (e.g. xml + xslt) then both html and css are redundant in the list of proposals and it
will make uncomfortable development environment for the user.

So, we must not have any assumptions about user's solutions and chosen development basis when an initial list of
preferred templates will be generated in first time. Only PHP File template might be initially added, because PHP
project has been chosen by a user. But it also is not an axiom, because many of PHP projects don't contain pure PHP
scripts, usually PHP code is embedded, and in this case another template should be used instead.

Note, a list of the preferred templates in the context menu of the PHP project will be extended automatically after
first using of the Cascading Style Sheet template in the PHP project. Therefore, the list will be adjusted according to
the current user needs for its development tasks.

I know how the preferred templates work. There is a consensus that NetBeans project should have muximum 10 preferred
templates. What I'm saying is that to have only one preferred templates is wasting. Like in java project. Is there only
java class? No, there is also some other templates like webservices or entity classes. And we don't expect, that every
user will use WS wizard. 

So why don't put there, what we think that user probably will need.  I don't think that html and css are redundant
there. Probably we should ask some ui expert. 

Guys,
There is prose and contra for each approach. And for sure deeper investigation is necessary.
For 6.0 let's use following set:
------------------------
PHP
HTML
XHTML
CSS
-----------------------

Now, an initial list of the Privileged Templates contains four templates:
 Templates/Scripting/EmptyPHP.php,
 Templates/Other/html.html,
 Templates/Other/xhtml.xhtml,
 Templates/Other/CascadeStyleSheet.css.

This issue can be reopened after 6.0 ...