Understanding HTML and CSS code is a good thing

Posted in Dreamweaver CSS on 15 December 2008 | Comments

When I was doing some Dreamweaver tuition recently, I was asked about implementing a CSS dropdown menu. I recommended this excellent CSS Menu from Craig Erskine which is itself a derivation of the original Suckerfish Dropdown menus on A list Apart.

Read more ...

New Dreamweaver CS4 beta

Posted in Dreamweaver on 5 June 2008 | Comments

Adobe have released a beta version of Dreamweaver CS4. If you are an existing user, you can enter your serial number for the current product in order to get a serial number for the beta version.

Fireworks CS4 also has a beta version that you can try. It’s good to see Fireworks continue to be developed. It’s a great programme.

The release of these beta versions means that the full release of all the Adobe CS4 products is probably at the end of the year or early 2009.

Technorati : dreamweaver, fireworks

Creating specific page styles with CSS

Posted in CSS Dreamweaver on 31 October 2007 | Comments [1]

Yesterday, I was asked if it was possible to create individual page styles using CSS. In this case, the same style sheet would be used but there would be a specific style rule for page x compared with page y. For example, you may want to have a different background image for your home page compared to your 'product' pages. Perhaps the home page has a 'blue theme' and the product pages are 'color coded' with a different colour...

Read more ...

Building a tabbed menu with Adobe Spry in Dreamweaver

Posted in Web development Dreamweaver on 3 July 2007 | Comments

When you have a lot of text content on a webpage, it's tempting to split it up into multiple pages. However, on some occasions (for example, a FAQs page), it may be better to use a single page but show/hide various sections of the content using JavaScript (of course, always making sure that content is accessible to users with JavaScript turned off).

Read more ...

Valid (X)HTML, Dreamweaver and unencoded ampersands

Posted in Web standards Dreamweaver on 4 August 2006 | Comments

One of the reasons why a webpage might not pass the W3C markup validation test is unencoded ampersands in the link URLs. This can often happen with links provided by affiliate schemes. You copy and paste the link code into your valid (X)HTML page and, lo and behold, the page no longer validates. Well, Dreamweaver can help.

Read more ...