- jQuery, CSS, HTML
- Fork the project and get set up locally
- In your browser navigate to
chrome://extensions/
- Click the
Load packed extension
(You might need to compress/zip the folder first — I can't remember) - Make sure it is 'enabled' after loading it
- You should be good to dev. Write me at taylorpoe@gmail.com if you can't get it going.
Chrome Extensions are a bit funky to develop in general.
Tabs are saved in the background.js
file, which runs in a secure environment. To access a console for this environment, go to chrome://extensions/
in your browser and find the MonoTab app. Make sure to first Reload the extension (must be done every time you change background.js). Then — to access the console, click background page
in the Inspect Views
section.
This environment runs on all webpages except for the new tab page
This environment runs on the new tab page
- Please PR against staging unless we've talked about shooting straight to master.
- Please do not update the
manifest.js
file.
Reason it needs to be on a new tab is because most user-list apps out there: Pocket, flipboard, etc tend to become graveyards of "set and forget". When our lists aren't in front of us they are often are never revisited.
MonoTab is different in that it hijacks the new tab screen in Chrome. A screen we all see many times each day. The goal is to create something worth of taking over this prime real estate. It needs to have a remarkable ux — something users will enjoy interacting with.
Save your browser some memory of having all those pages open at once. Write more here.