Christian Heilmann

How to create a CSS Toolshed submission – step by step

Friday, December 2nd, 2005 at 12:54 am

It has been quite a while since I started the CSS Toolshed, and I expected a lot of submissions after hundreds of people downloaded the templates, but now – more than two weeks later – I only got one good submission to show.

OK, I get the message: I cannot expect developers to work in conditions like these to submit something for a project they don’t get any money from. It is frustrating enough having to deal with these at work, but at least there is a paycheck in it.

So, to make it a bit easier, I updated the templates pack to include

  • all the necessary images
  • more templates containing almost all elements of the building block gallery
  • pre-defined CSS selectors with all the content elements

As the pièce de résistance, I created a new demo design called Happy Cock and wrote down what I was doing while developing it.

So if you need to get an insight as to how to create a CSS Toolshed entry (or simply a flexible CSS layout) go and read:

Hopefully this will help the toolshed get some more submissions, I’d hate simply to let it die…

Share on Mastodon (needs instance)

Share on BlueSky

Newsletter

Check out the Dev Digest Newsletter I write every week for WeAreDevelopers. Latest issues:

Don't stop thinking, AI Slop vs. OSS Security, rolling your own S3 Despite AI you still need to think, Bitter lessons from building AI products,  AI Slop vs. OSS security and pointer pointer…
200: Building for the web, what's left after rm -rf & 🌊🐴 vs AI What remains after you do a rm -rf? Why do LLMs know about a seahorse emoji? What image formats should you use? How private is your car?
Word is Doomed, Flawed LLM benchmarks, hard sorting and CSS mistakes Spot LLM benchmark flaws, learn why sorting is hard, how to run Doom in Word and how to say "no" like a manager.
30 years of JS, Browser AI, how attackers use GenAI, whistling code Learn how to use AI in your browser and not on the cloud, why AI makes different mistakes than humans and go and whistle up some code!
197: Dunning-Kruger steroids, state of cloud security, puppies>beer

My other work: