From the Virtual Handshake:
Intellectual property law is really screwy sometimes. In order to legally protect your IP, you have to make it public (eventually)
The good to come from this is that some of Google’s ranking algorithm secrets have been revealed.
A few interesting points, including:
- Length of domain registration (longer is better)
- Speed with which links are acquired (slower is better)
- Frequency and amount of updates (again, neither extreme is good)
Much is common sense (with the benefit of hindsight, of course) but it’s interesting that Google measures the speed at which you aquire inbound links. So any strategies involving aggressive link building may be best avoided. A longer-term plan might be best adopted, and this goes hand in hand with the frequency of updates. Looks like some things just can’t be rushed.
Food for thought, anyway.
Tony Aslett presented a tutorial at Brisbane’s Web Standards Group meeting in April that very simply shows how to use the DOM (Document Object Model) to change classes and styles on the fly.
I wasn’t at the meeting, but just the presentation on it’s own is a useful resource.
From the Sydney Morning Herald:
A company called Remote Approach is using a feature in Adobe’s PDF Reader to track how many times a PDF document has been accessed, according to a report in the Linux Weekly News.
For the feature to be used, a PDF had to be created, uploaded to the company’s server to be tagged, and then distributed, the report said.
The tracking failed when the PDF was viewed by other readers such as Xpdf and Kpdf, and version 5 of Adobe Reader.
However, when the document was opened using Adobe Reader 7, Remote Approach began logging the number of times it was viewed from the IP address of the computer on which it was opened.
The information is submitted over port 80 using HTTP – the standard port for web servers – which no home or office firewall would normally block.
I can hear Michael breathe a sigh of relief now…
Ever since I saw the concept of the Page Description Diagram I liked the idea. A simple way of sorting out what a page has to do without any other distractions.
Actually putting one together is a bit harder than I first thought. Where do you start?
Then Ryan Singer from 37 Signals penned An Introduction to Using Patterns in Web Design. Bingo – someone has joined the dots for me!
- Make a list of your “bits”- everything on the page and anything that the visitor might have to do
- Group them where they share some commonality
- Prioritise them (Hey, the contents of a Page Description Diagram!)
- Design each chunk, and then put those chunks together (Hey, a wireframe!)
- Then design away (Hey, a comp!)
Following Ryan’s steps would make it difficult to end up with a comp that didn’t achieve what it was supposed to in terms of site goals.
Not impossible, mind you, but difficult.
A bunch of new entries to the CSS Zen Garden. Some I like:
That’s not a typo – Hengarden; not Zengarden…
Now this is pretty cool.
Most examples of list sorting I’ve seen involve little up and down arrows, and you have to click away and only move the item one step at a time.
Forget about that – drag and drop items on the list instead!