43 Folders

Back to Work

Merlin’s weekly podcast with Dan Benjamin. We talk about creativity, independence, and making things you love.

Join us via RSS, iTunes, or at 5by5.tv.

”What’s 43 Folders?”
43Folders.com is Merlin Mann’s website about finding the time and attention to do your best creative work.

Beautify Instiki (even more) with custom CSS

You probably already know about Instiki. It’s is a terrific, elegant, beautiful wiki that I personally use for half a dozen of my own projects. I’ll probably run a longer post on Instiki some time in the future, but I can especially recommend the OS X install for Mac users. If you have a server that can handle Ruby 1.8.1, I can equally recommend the regular Ruby install. The app is gorgeous and works swell either way.

One of my favorite things about Instiki is how attractive and simple it is to use (PHPWiki, you’ll always be my first love, but sometimes, you’re just too high-maintenance). Instiki even lets you apply your own custom style sheets without having to change any actual code (Dear Typepad: Please steal this idea. Love, Merlin.). Here’s a quick tip for adding your own styles to your Instiki wiki.

  1. Download, install, and configure Instiki for your corner of the web

    • In practice, this is likely to take less than five minutes
    • Mac users only need to install Instiki.app, which brilliantly contains its own Ruby installation and WEBrick server (serves over port 2500 on the out-of-the-box install)
  2. Pull up the home page of your wiki

  3. Click the Edit Web link from the bottom of the home page
  4. Under the Specialize section, click the See styles >> link.

    • This will reveal a textarea field
  5. Type or paste in your CSS styles

    • Note that you can View Source on any Instiki page to see which HTML elements you can hook on to
  6. When you’re finished adding styles, type in your system password and click Update Web

  7. Behold your pretty new look.

Hint: Here, as in most cases, it’s really easier to just refer to an external style sheet, so you can make changes in a text editor (rather than having to diddle around in a textarea and repeatedly save changes). I welcome you to swipe my “hamburger helper” Instiki style sheet to get you started. You’re also welcome to just link to it as is (proviso: may go away some day without warning). To apply it to your wiki:

  1. Follow steps 1-4 as above
  2. Paste the following into your style textarea:
  3. @import url("http://www.merlinmann.com/43f/instiki.css");

  4. Save as in 6 above

Note: There are many many other swell wiki packages out there (I estimate that three new ones have been released since I started writing this). Mac users who want something even simpler should definitely look at VoodooPad, which brings a fairly robust, very intuitive wiki to a desktop Mac app. Fave feature? Export all your pages to your iPod. Neato!

dougj's picture

I've been experimenting with ways...

I've been experimenting with ways of using SiteBar plus a wiki (see http://www.douglasjohnston.net/weblog/index.php/archives/2004/10/04/gtd-sitebar-wiki/ for the how and why), and I really have to concur with Jay. For years I have been building up hundreds of little text files throughout four or five different computers, and it was nearly impossible to find anything ("grep" notwithstanding). With a wiki (first emacs-wiki locally, then twiki on the Net) I was able to finally aggregate all these texts together in one place and cross-link everything as I needed. By setting up a hierarchy within the wiki, I could easily navigate and add materials, or just jot my info down on the fly and reparent it later as needed. For the first time, my life started to really feel organised.

Now, the next part of the plan is implementing GTD within it as well. Since I change machines on an hourly basis, having a centralised wiki to handle things is a virtual necessity. (I tried Instiki, and it was great for OS X, but that's only one of several machines in three different places.) The SiteBar thing is extremely helpful and cross-platform, and allows me to zoom in on exactly the GTD (and other) info I need.

The system isn't perfect. Wikis have their plusses and minuses, to be sure. For example, I can think of no easy way of "moving" Next Actions that are completed to an archive, besides cutting and pasting. SiteBar linking to the edit forms does vastly improve the speed of doing this, though, and is certainly far faster than shuffling around papers and rewriting things using pencil. If you're not "WebOS-friendly", wikis may seem cumbersome and not worth the effort. They're second nature to me, and so my effiency is much improved over previous organisational attempts. If you're still flailing around looking for a perfect solution, you might as well give Instiki or another wiki a try: it costs nothing, and you might even find other uses for it down the road.

cheers, dj

 
EXPLORE 43Folders THE GOOD STUFF

Popular
Today

Popular
Classics

An Oblique Strategy:
Honor thy error as a hidden intention


STAY IN THE LOOP:

Subscribe with Google Reader

Subscribe on Netvibes

Add to Technorati Favorites

Subscribe on Pageflakes

Add RSS feed

The Podcast Feed

Cranking

Merlin used to crank. He’s not cranking any more.

This is an essay about family, priorities, and Shakey’s Pizza, and it’s probably the best thing he’s written. »

Scared Shitless

Merlin’s scared. You’re scared. Everybody is scared.

This is the video of Merlin’s keynote at Webstock 2011. The one where he cried. You should watch it. »