Specifications

- 75 -
Keep this in mind when you create Type Drawers. To avoid unnecessary billing, a good plan is to leave the Type
Drawer in the disabled state, add fonts and websites to it, generate the CSS, and add the CSS to the appropriate
style sheets. When you have done all this, enable the Type Drawer and enjoy your customized websites!
Managing websites
A website can be:
• A complete hostname, such as www.example.com.
• The word localhost, for testing on a web server on your local workstation.
• An IP address, such as 12.34.56.78 (especially useful for websites on your local network).
• A hostname with wildcards replacing the subdomain, the top-level domain, or both.
A website string with wildcards is a powerful way to easily include all possible sites for a client. For example, by using
*.example.com, your Type Drawer will serve fonts to www.example.com, blog.example.com, jobs.example.com, and
any other subdomain of example.com.
You can also include multiple top-level domains by using the wildcard in the final position of the website name. For
example, using example.co.* allows a single Type Drawer to serve fonts to example.co.uk, example.co.jp,
example.co.de, and all other "dot-co" websites.
Website strings cannot include wildcards to replace part of a string, like www.ex*le.com, and cannot be used to
cover all domains, like www.*.com. The wildcard can only be used to specify the subdomain, the top-level domain, or
both.
Cautions
• Be careful deploying CSS to a live website when localhost is assigned to the same Type Drawer. localhost
is useful for local testing, but if published CSS includes a Type Drawer with localhost, it could lead to
unexpected overages in your bandwidth.
• Don't include wildcards for hosts that might be outside your control (such as *.blogger.com or
*.intuitwebsites.com). Anyone with a subdomain on these hosts could conceivably copy your CSS and use
your WebINK fonts, causing you to be billed for the higher bandwidth usage.
Estimating Font Usage and Cost
In order to estimate the usage of the fonts in your Type Drawer, and so what your monthly cost might be, you should
understand a little about how WebINK fonts are delivered and used, and you will need to make some assumptions
about your visitors.
Because different browsers support different downloadable font formats, the font file that WebINK delivers for one
browser may be a different size than the same font is for another browser. The difference in size will generally not be
much and is taken into account in your actual billing, but for estimating purposes you can use an average font size.
When a browser loads your web page for the first time, it downloads the fonts for that page and stores them on the
visitor's computer. Each time the font is downloaded to a computer, this is counted in your bandwidth usage.
However, this doesn't mean that every time a person visits a page on your website that you get charged for it. The
browser will use the local copy of the font that it downloaded as long as it is available. This caching of resources is
under the user's control and depends on their browsing habits. Typically a font may remain in the browser's cache
for as long as a day, so when a user visits your website and moves through its pages, the fonts will only be
downloaded once. If they visit your site every day, it is likely that the fonts will stay in their cache for all that time.
Suppose you have five fonts in your Type Drawer, each about 40kb in size. (Most fonts available in the WebINK
service are between 35kb and 50kb.) Now suppose that your website has 10,000 visitors in a month. This gives you
a bandwidth of 5 fonts (times) 40,000 bytes per font (times) 10,000 downloads per month or
5 × 40 000 × 10 000 = 2 000 000 000
or roughly 2 gigabytes per month.