Apparently, you can’t use embedded style sheets in WordPress.com, but you can use inline styles. In this post, I’m going to attempt to replicate one of my old CSS-styled HTML pages. I’ll start with my CSS Font Properties Test that I first published in HTML with embedded and inline CSS in February 1998. Here goes:
[Remainder of table truncated]
font PropertyPosted in Writing for the Web
Tagged authoring, CSS, historical, HTML, legacy, porting, style sheets, Web, wordpress.com
There would be no World Wide Web without hyperlinks. Hyperlinks are what allow us to add photos to web pages, link from one page to another, etc. These days, much of this hyperlinking is done for us automatically on sites such as Flickr. But Flickr also allows you to create hyperlinks yourself in many areas of the site, including photo descriptions, comments, and group threads. I create links between photos and members all the time, and it’s easy for me to do so because I’ve memorized the HTML. Once you learn the HTML for a hyperlink, you can be a hyperlinker yourself!
An HTML tag begins with a less-than sign, created by holding down the shift key while you tap the comma key. Then you type “a” for “anchor” and “href” for “hypertext reference”. Then you type the equals sign (=) followed by a quotation mark. This quotation mark is the beginning of a “container” for the URL, or “uniform resource locator.” The URL is the “web address” for the object to which you are linking. As a mnemonic device, I think of this opening tag as the English phrase, “Anchor hypertext reference is…”
Recently, I posted a photo I took of a fellow Flickrite at a FlickrMeet. Continue reading
Posted in Writing for the Web
Tagged accessibility, grammar, HTML, hyperlink, hypertext, tutorial, Web authoring
Yesterday, I spent some time revising the bylaws I wrote for SDCRID so they could be repurposed for AzRID. The AzRID president asked me to do this, because she had heard from a little bird (Rob Balaam, RID Region 5 Representative) that I had done the bylaws for SDCRID. Since there are some interesting lessons to be learned from my work about bylaws and, incidentally, about HTML and CSS, I thought it might be beneficial to share them here.
First of all, my sources for the bylaws were the RID bylaws, the RID Affliate Chapter Handbook Sample Bylaws (pp 238–257), and the AzRID bylaws (which link will probably be broken soon when they upload the new ones). I also consulted Robert’s Rules of Order Newly Revised when I was writing the SDCRID bylaws. I pretty much followed the Sample Bylaws except when I felt the RID bylaws were clearer or more up-to-date. I also, of course, checked the AzRID bylaws for any special bylaws that needed to stay. That takes care of the bylaws part of it.
I also had an interesting challenge and a gratifying success with writing the bylaws in a plain-text editor (BBEdit) using XHTML 1.1 and CSS. I did this because I wanted tight control over sectioning and listing. Bylaws documents need to be very structured. One can write in all the sections, subsections, and list numbers, but that is a waste of time, especially if one ever wants to rearrange the order of sections and list items. If one does use styles in a word processing program, sometimes formatting can become corrupted during routine editing operations such as cutting, pasting, deleting, etc., and then one can lose the document structure. Besides, I enjoy the challenge of hand-coding HTML and CSS, and I like to demonstrate the power of these structural and presentational markup languages working hand-in-hand.
Posted in Writing for the Web
Tagged bylaws, community, counters, CSS, ethics, grammar, HTML, organization, outline, photo, RID, screenshot, service, tutorial, Web authoring
[This page resided at http://danielgreene.com/fontprop.html from 1998–2010.]
font Property Continue reading Posted in Writing for the Web
Tagged CSS, design, fonts, formatting, HTML, layout, standards, typography, Web browsers
[This page resided for many years at http://danielgreene.com/cssbug.html]
Results are shown when using the following embedded CSS declarations [now done with inline CSS because this blog doesn't allow embedded CSS.]:
code { font-family: Fixedsys, "Lucida Console",
"Courier New", monospace; }
.p { background: #CFC; /*lightest green*/
color: black; }
.v { background: #CFF; /*lightest blue*/
color: black; }
.d { background: #FCF; /*lightest purple*/
color: black; }
.samp { background: #FCF; /*lightest purple*/
color: black;
margin: 1em 3em;
border: thin solid black;
padding: 5mm; }
.test { background: #CCC; /*lightest gray*/
padding: 1em; }
Here’s how it looks in your browser:
{ font: 150% serif; }
The quick brown fox jumped over the lazy dog.
This is what it looked like in my browser (MSIE 4.72.2106.8 for Win95): Continue reading
Posted in Writing for the Web
Tagged CSS, design, formatting, HTML, layout, standards, style sheets, Web authoring, Web browsers
| Aqua | Blue | Black | Fuchsia |
| Gray | Green | Lime | Maroon |
| Navy | Olive | Purple | Red |
| Silver | Teal | White | Yellow |
You can use these mnemonic color names instead of numbers when writing CSS (style sheets). Makes your life a little easier! 
[This page resided at http://danielgreene.com/style.html from 1996–2010 and is now presented for historical content rather than as the CSS demonstration it once was.]
“CSS is an easy way to effect sweeping stylistic changes in your web pages without much effort.”
Have you ever come across a web page that was “stylish” to the point of illegibility? Of course you have. As a web surfer, have you ever wished you could turn off web author’s “style” and view content the way you please? As a web author, have you ever wished there were a way to stylize your web pages without having to resort to using hundreds of extended tags like <FONT> </FONT> all over the place? Haven’t we all! Now there is an alternative to all this nonsense: Cascading Style Sheets (CSS). CSS is an easy-to-use document formatting language developed by the The World Wide Web Consortium (W3C). CSS uses common terminology known to anyone familiar with typography, and was designed to give web publishers nearly as much creative control in their web pages as in printed material.
The beauty of CSS is that it works right along with proper, structural HTML (HyperText Markup Language, used in writing web pages). Web pages written in proper HTML reveal the logical structure and outline of your document, and are guaranteed to display properly in any browser, regardless of platform or system configuration. Documents written in proper HTML enhanced with style sheets give viewers freedom of choice. CSS support can be toggled on and off by the user, so that, if your readers don’t like your style, but still want to read your content, they can turn off your “kewl” blue on black color scheme, and read your offerings in a more palatable palette. 
Continue reading
Posted in Writing for the Web
Tagged accessibility, browsers, CSS, design, fonts, formatting, HTML, layout, standards, style sheets, tutorial, typography, Web, Web authoring, Web design
[This page resided at http://danielgreene.com/design.html from 1996–2010.]
This site was originally my “Notes on This Site” page, and it has turned into something of a guide to best practices in Web design, which is how I present it now, in the hope that people seeking to learn how to write better Web sites will read this and use what they learn here to make the Web a better place for everyone. I use the first person, and use examples from my own Web site, but what I am doing here, anyone can do to make their Web site more accessible, speedy, stylish, and device-independent.
Although this site looks nifty when viewed with a Web browser that supports Cascading Style Sheets, it was written to look good and be accessible to all browsers:
BGCOLOR or FONT COLOR tags directing your browser to view entire pages with certain text on a certain background, so if you don’t like the background or text colors, you have the power to change that in your browser’s user preferences.Even my style sheets were written with accessibility in mind: Continue reading
Posted in Writing for the Web
Tagged accessibility, CSS, design, HTML, layout, markup, tutorial, Web authoring, XHTML
|
Latest DeafReads
