Skip to content

Archive for the ‘XHTML/CSS’

Premium discounts in April for PSD to XHTML/CSS conversion

Thursday, April 15th, 2010

We would like to announce premium discounts for PSD to XHTML/CSS conversion in April 2010!

Here is what you get:

  • PHN0cm9uZz41MCUgZGlzY291bnQ8L3N0cm9uZz4= for PHN0cm9uZz5QU0QgdG8gWEhUTUwvQ1NTPC9zdHJvbmc+ conversion
  • PHN0cm9uZz5OTyA8L3N0cm9uZz4= up-front payments
  • PHN0cm9uZz5OTyA8L3N0cm9uZz4= hidden extra costs

We offer 50% discount for all the PSD to XHTML/CSS orders submitted by 30th April 2010 .
This way the price for the first page conversion starts at $60 .
We also don’t require anything up-front - you can pay in full after we deliver your project.
The price is fixed before we start - we don’t add anything to the price during the
coding process.

Don’t miss your chance and send your project our way before 30th of April !

We are looking forward to your orders as … read more

Two colors in sIFR and useful sIFR3 hints

Wednesday, May 6th, 2009

These days most frontend CSS-developers face with a problem of using custom fonts when coding web pages. The technology of sIFR (Scalable Inman Flash Replacement) became very popular because it gives rather flexible and easy to use solution of this problem. If you are new to this technology please check sIFR Documentation for more information.

Though sIFR gives many useful additional abilities for the developers there is one thing which is not trivial to do with sIFR. Imagine that you need to highlight some parts of the sIFR text with different color(s). The solution which cames in mind is splitting the text into several tags and applying sIFR to every tag individually. Unfortunately this doesn’t work in many cases because of impossibility to make the width of sIFR element flexible, so more elegant solution needs to be found.

If you ever tried to find ready-made solution you’ll definitely find the … read more

Specifics of large projects slicing

Thursday, November 27th, 2008

Quite obviously slicing for an unpopular site with few pages isn’t the same as coding and supporting of huge popular portal.
So let’s try to review some nuances and solutions which an HTML coder should always be ready for.

A few advises

An HTML page and style files code should be well structured and should have an ability of extending without any problems. Every site, and especially large and popular site, tends to growing and expanding.
Generally the bigger is the project the harder it is to provide changes to pages structure. This means that from the very beginning of coding you should be ready for permanent changes, adding new blocks and elements to the page in future.

Correct coding should be laconic

You should understand that sometimes page services are overcharged. That is why you should work scrupulous on the generated code trying to make it maximum simple and laconic. A few … read more

HTML coding without hacks

Thursday, November 27th, 2008

When using semantic coding each developer will necessarily face the problem of compatibility in different browsers. In most cases it is necessary to use “hacks” to solve these problems. Usually this means a special way of writing selectors or rules which would work only in a concrete browser. However compatibility with CSS in the majority of browsers has already reached the level when it is necessary to limit “hacks” usage.

Most often, a browser which has the biggest number of difficulties is Internet Explorer (more often - IE6). The variety of errors in CSS realization at this browser t surprises even the most skilled web-designers, and, in particular, slicers. That is why there are situations when it is necessary to use alternative rules for Internet Explorer, in similar cases it is recommended to apply “hacks”. If you would need to use alternative rules for Firefox only it is … read more

HTML Hacks

Thursday, November 27th, 2008

1. The problem with Min-width in Internet Explorer

IE understands this property as width. But the following hack … read more

Markup quality assurance

Thursday, November 27th, 2008

From time to time we’re asked to estimate the quality of the coded page. Also when surfing we often check quickly if the page was professionally created. For all this time a number of standard criteria has been formed which we would like to share with you.

Tools

As all this is performed online we usually use Firefox with Web Developer plug-in for an estimation of coding quality.

Criteria in the order of importance

0. The site should work normally.

Certainly it is the major criterion. It is necessary a priori for the coding estimation, what would be the sense to estimate otherwise? The site should be enough compatible in different browsers: IE6-7, FF, Safari, Opera – that is my list.

1. Semantics of a code

We check this in two ways.

  • Disconnect styles on page Ctrl+Shift+S (Apple+Shift+S for mac) and it is visible at once whether the page remains understandable? Whether the navigation is visible? Headings? Or all is done as text in DIVs …
  • read more