Fork webpages

I’m looking for something a bit unusual. Say you are following the instructions for installing a software package (rl example:…/webmin/installing-webmin). Now you find out the instructions are outdated, or incomplete.

How do you keep your notes/additional instructions together with the original? Now you have two problems, your instructions and the original can be updated independently. What happens when the original is updated, or a new version of the software is released?

Wouldn’t it be great if you could fork the webpage and update it (or even submit a pull request to the maintainer)?

Is there any practical way of working this way – or will I be stuck with a notetaker / blog / bunch of outdated textfiles?

A lot of questions – maybe one of you has the answer.

February 17, 2012 at 11:47 AM in Development, Web

Link: Stop paying your jQuery tax

Speed up your jQuery powered site by moving scripts to the footer.

Turns out that pushing jQuery to the footer is quite easy for the common case. If all we want is a nice $.ready function that we have accessible everywhere we can explicitly define it without jQuery. Then we can pass the functions we capture to jQuery later on after it loads.

The big lesson learned is that we could avoided this whole problem if we started off with my proposed helper.

via Stop paying your jQuery tax.

February 17, 2012 at 11:07 AM in Development