Skip to main content

Writing your first UserScript, Template as a beginner's tutorial

UserScripts are fun, useful and often productive. A lot of sites have small improvements you think could add a lot of value. And just because you are not the author of the site, you need not give up. With some basic javascript skills, you could write a userscript, install it on your browser, and make the site behave.

Step 1. Build a script from the template

Start with the following template and modify what you want
// ==UserScript==
//Displayable Name of your script 
// @name           My First Script 
// brief description
// @description    Alerts Hello   
//URI (preferably your own site, so browser can avert naming collisions
// @namespace
// Your name, userscript userid link (optional)   
// @author         sarathonline (****) 
// If you want to license out
// @license        GNU GPL v3 ( 
//(optional) may be used by browsers to display an about link
// @homepage 
//Version Number
// @version        1.0
// Urls process this user script on
// @include        http://*
// Add any library dependencies here, so they are loaded before your script is loaded.
// @require
// @history        1.0 first version
// @history        1.0b first beta version, who knew!!
// ==/UserScript==

//And of course your code!!
window.alert("Hello.. My Extension processed you..");

Thats it, You have your first userscript. By convention user scripts are

Step 2. Host your UserScript on web.

You have by now authored yourscript.user.js file. Now you need to distribute this as an extension. To do that you need to find a home for this file on the web. If can host a js file, on your own website. You could. However, if you do that on, your script is instantly available to a much larger audience. is a free user script hosting site, that also doubles as a market place. also provides an easier way to edit the code online, in case you need to update.

Step 3. Share and Install (coming)

Popular posts from this blog

Appcache manifest file issues/caveats

Application cache (appcache) is a powerful feature in HTML5. However, it does come with baggage. Many (see links below) advocated ferociously against it due to tricky issues it comes with. For someone who is just testing waters, these issues may throw them off grid. Knowing them before hand helps reduce some unpredictable effects.

Being a Vegetarian

I am a Proud Vegetarian. I don't eat Meat or Eggs. People say its hard here in US to be one. I beg to differ. The mere fact that I am hail and healthy these 4 years is a definitive proof. Apart from being bullied and trash talked by The Meat-Eaters, There is really nothing that makes this choice of mine any more than a debatable issue at a lunch or dinner. Other things aside, I am writing this blog having watched a PETA Video. Before you click on the play button, I ask you - If you are a vegetarian : Dont watch it. If you are not : Dare to watch it till the end. If you think going veg is just a fashion, think again . Even if you just want to do it for Fashion . Do it. Go Vegetarian. And Feel better asking the waiter for a Vegetarian Entrée in your next lunch.

classpath*: making your Modular Spring Resources

Spring gives multiple options to load XML resources for building contexts. the reference documentation does explain this feature quite well. However, I am taking my shot at explaining the different practical scenarios ( by order of growing modularisation) For Example, A simplest Spring based web Context Loader can be configured with resources like this <context-param> <param-name>contextConfigLocation</param-name> <param-value>applicationContext.xml</param-value> </context-param> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> You just need to put applicationContext.xml in WEB-INF/ folder of your webapp. However, Typically an application is n-tiered. You can also have multiple files setup and in relative paths. like <param-value> context-files/applicationContext.xml context-files/dao.xml context-files/service.xml </param-value>