More CSS
More CSS
I know ... I'm want too much
As far as I can see, phpwcms is going more and more the right way concerning valid HTML and CSS Code. But .... (don't hit me !) ... even in the current release RC4 there one thing missing (or not correctly implemented):
In the page layout section you can choose between :
- Table
- CSS-Div
- custom (from template main block)
Nice feature, but CSS/Div (even custom) is nearly useless.
For example If you say "CSS/Div" all rows&columns(head, left column, center and right column, footer) from the pagelayout are created via Div and CSS. Nice !
But as soon as you start working with pictures, article lists, etc tables are used for design. This means even if one wants to creaty pure tableless css designs, he has to use tables implemented by those functions.
Currently I completly designed an article via Dreamweaver, and copied the HTML source in the article.
It would be much better (IMHO) to put all elements created via contenttype or replacement-tags in Divs, as soon as the admin chooses CSS/DIV in the page layout section. OK, for the user of phpwcms it means that he has to use stylesheets, but OK thats css
for example :
the "insert Picture/Text" Content Type could be realized like this :
<div class="articletextpicture"><div class="picture"><img src="yourpic.jpg" /></div><div class="text">Place all your text here</div></div>
and the "article list" Content Type could be done this way :
<ul class="articlelsiting">
<li><a href="link1">article 1</a></li>
<li><a href="link2">article 2</a></li>
<li><a href="link3">article 3</a></li>
</ul>
Even if some of you don't understand why it is important, but after many years of webdevelopment I still didn't find a free and easy-to-use CMS that is able to create pure AND valid XHTML/CSS pages. I think if there is way to implement this, then the phpwcms community could get bigger, much bigger
As far as I can see, phpwcms is going more and more the right way concerning valid HTML and CSS Code. But .... (don't hit me !) ... even in the current release RC4 there one thing missing (or not correctly implemented):
In the page layout section you can choose between :
- Table
- CSS-Div
- custom (from template main block)
Nice feature, but CSS/Div (even custom) is nearly useless.
For example If you say "CSS/Div" all rows&columns(head, left column, center and right column, footer) from the pagelayout are created via Div and CSS. Nice !
But as soon as you start working with pictures, article lists, etc tables are used for design. This means even if one wants to creaty pure tableless css designs, he has to use tables implemented by those functions.
Currently I completly designed an article via Dreamweaver, and copied the HTML source in the article.
It would be much better (IMHO) to put all elements created via contenttype or replacement-tags in Divs, as soon as the admin chooses CSS/DIV in the page layout section. OK, for the user of phpwcms it means that he has to use stylesheets, but OK thats css
for example :
the "insert Picture/Text" Content Type could be realized like this :
<div class="articletextpicture"><div class="picture"><img src="yourpic.jpg" /></div><div class="text">Place all your text here</div></div>
and the "article list" Content Type could be done this way :
<ul class="articlelsiting">
<li><a href="link1">article 1</a></li>
<li><a href="link2">article 2</a></li>
<li><a href="link3">article 3</a></li>
</ul>
Even if some of you don't understand why it is important, but after many years of webdevelopment I still didn't find a free and easy-to-use CMS that is able to create pure AND valid XHTML/CSS pages. I think if there is way to implement this, then the phpwcms community could get bigger, much bigger
Pure CSS is a very good idea.
And when "conf.template_default.inc.php" changed another idea is to use Standard-html-Tags.
<h1> and not "articleHead"
<p> and not "articleText"
<pre> and not "articleCode"
Design-Changes could be done via CSS, and if the frontend-user uses a textbrowser, screenreader, ... he see correct information!
And when "conf.template_default.inc.php" changed another idea is to use Standard-html-Tags.
<h1> and not "articleHead"
<p> and not "articleText"
<pre> and not "articleCode"
Design-Changes could be done via CSS, and if the frontend-user uses a textbrowser, screenreader, ... he see correct information!
Ralf
Me again ...
As I'm still trying to design a page using pure XHTML/CSS there are non-stop problems. I tried to rewrite some of the php code, but had to give up, as nearly everythings needs to be rewritten.
As far as I can see at the moment it is absolutly impossible to create a standard compliant webpage using phpwcms.
Are there plans for the near future allowing phpwcms to create valid sites ?
If there are such plans ... please say something, because I really want to use phpwcms, but I do not plan to rewrite every new release.
Some problems :
- table-tags still use border and align attributes
- as rk said before: instead of using <span class="articleText>blabla</span> using <p> would be more useful ....
Thanks
As I'm still trying to design a page using pure XHTML/CSS there are non-stop problems. I tried to rewrite some of the php code, but had to give up, as nearly everythings needs to be rewritten.
As far as I can see at the moment it is absolutly impossible to create a standard compliant webpage using phpwcms.
Are there plans for the near future allowing phpwcms to create valid sites ?
If there are such plans ... please say something, because I really want to use phpwcms, but I do not plan to rewrite every new release.
Some problems :
- table-tags still use border and align attributes
- as rk said before: instead of using <span class="articleText>blabla</span> using <p> would be more useful ....
Thanks
yes, I understand and agree. But maybe we also should look to the future.
Current webdesigners are using CSS more and more because of the compatability with all the browsers.
There is only 1 way to make a site full compatibel with all browsers: CSS
Not a single chance you can make a site (and I'm not talking about the very basic site's) compatible for all browsers by using tables.
So maybe it's not a priority, but when I look at the future, it better be a priority. (this is not a flame, just my own opinion)
Current webdesigners are using CSS more and more because of the compatability with all the browsers.
There is only 1 way to make a site full compatibel with all browsers: CSS
Not a single chance you can make a site (and I'm not talking about the very basic site's) compatible for all browsers by using tables.
So maybe it's not a priority, but when I look at the future, it better be a priority. (this is not a flame, just my own opinion)
aCCuReRaS,
I fully agree with you and many others (it's my own opinion): CSS and XHTML is the future. Your points arre correct and I will not say anything against it.
I discussed this subject with Oliver some time ago and he explained to me that, as long as every browser will display the content (almost) correctly as it is generated by phpwcms at the moment, he sees no need of changing the output to valid XHTML. He puts his attention to more important things like security and functionality.
Nevertheless I am sure that XHTML will have a priority some day, you can be sure that Oliver has this in mind, but you shouldn't expect this soon.
Many greetings
- Jérôme
I fully agree with you and many others (it's my own opinion): CSS and XHTML is the future. Your points arre correct and I will not say anything against it.
I discussed this subject with Oliver some time ago and he explained to me that, as long as every browser will display the content (almost) correctly as it is generated by phpwcms at the moment, he sees no need of changing the output to valid XHTML. He puts his attention to more important things like security and functionality.
Nevertheless I am sure that XHTML will have a priority some day, you can be sure that Oliver has this in mind, but you shouldn't expect this soon.
Many greetings
- Jérôme
I am sure there are plans, but, as always - "so many plans, so little time"... There is only one developer working on this CMS and his plate is pretty full. However, he has shown that he is more than willing to incorporate community contributions, when possible and when they make sense, given the overall CMS design and code constraints.LANtastic wrote:Me again ...
Are there plans for the near future allowing phpwcms to create valid sites ?
If there are such plans ... please say something, because I really want to use phpwcms, but I do not plan to rewrite every new release.
Thanks
So, if you can and have the skills to do it, why not do it gradually? Pick one area, fix it to validate, or use DIV's instead of tables, post your contribution to the forum and see how it goes.
If it gets incorporated, then we are all one step ahead. If not, you don't spend time on the remaining parts.