Tatham begins by pointing out that Expression Web is not dependent on Microsoft’s server-side products, and thus well worth an investigation whether you’re using HTML, ASP.NET, or PHP. He then sings the praises of building towards web standards, and mentions some benefits of doing so (faster loading with CSS layouts, for example).
As we move on we’ll see how important it is to work out which standard you want to target before jumping into the code, and how Expression Web is all about enabling that process. It’s smart HTML IntelliSense, in-built ‘Compatibility Checker,’ and HTML-styled ‘Find and Replace’ function all make web standards that much simpler.
Given that the website for it is still a broken train wreck, I feel really bad for anyone DUMB ENOUGH to be duped into using piles of junk like this one. Another laundry list of how not to build a website, where things like valid markup and the WCAG are completely alien concepts.
Hi fendeanson - there have been a few issues with PHP in earlier versions (like v1 and v2) but they should all be well and truly fixed by now. If you’re still having issues, feel free to send them through to me and I can raise them with the team.
There’s first class support for PHP in Expression Web which I’ll be showing in the next article.
Outstanding article man! Maybe I am biased being a .NET junkie. Your writing is fluent, clear, and informative, unlike alot of article writers here on SitePoint who go for shock-and-awe to get hits. Looking forward to the next MS article!