By Albert Sala on
Wednesday, January 18, 2012
When converting a design to a DotNetNuke skin the fonts are always a subject of high importance. The known standard web fonts supported by all browsers in all platforms is quite limited so we either have to replace fonts with something more standard or have to find a way to include the fonts in the web.
Google Web Fonts is a nice option but you are limited to the list of fonts available online (+400 at the time of writing). So if you need a special font not available on Google’s list you are out of luck.
|
By Albert Sala on
Monday, January 16, 2012
When converting a web design (Photoshop, Dreamweaver, Indesign, HTML...) to a DotNetNuke skin you have a couple options for adding texts.
|
By Albert Sala on
Saturday, January 14, 2012
In DotNetNuke you can configure the containers used for modules at different places. One of the options is to fix the container in a given pane from the skin definition. This can save a lot of time when adding new modules to the site if you know in advance that all modules in a given pane should share the same design.
This is commonly used, for example, in a media pane, where you will always include images for banner purposes.
|
By PSDtoDNN . on
Thursday, April 28, 2011
Google web fonts has a selection of non-standard typefaces that can be used in any website, and works by including a stylesheet link to a hosted CSS file in the <head> section of the HTML document, and then defining a style within the website CSS file that uses the new font family.
|