Itches, in the context of the indieweb, are individuals's personal sources of annoyances using the web or in particular their own website, that they use to itemize and prioritize what to create, design, build, and improve on their own website, often by first listing such "itches" on a section in their User: page.
Because you should focus on scratching your own itches, instead of being distracted by other people's drama about and on sites and software you don't control.
The focus on scratching your own itches was one of the motivations for founding IndieWebCamp.
Creating is self-empowering, and the follow-up, deploying on your own website and selfdogfooding your creations, doubly so.
Write down your itches
Collect Itches on your User: page in an == Itches == section.
== Itches == * something you want on your own site * something else that annoys you about the web you use * ... etc.
Prioritize your itches
When you start collecting lots of itches, you may want to start prioritizing them, perhaps by which are the most annoying, or which annoy you the most frequently.
Start a "Working on" section for that, and put what you're currently working on at the top. Even just one or two at a time:
== Working On == * the next thing I'm working on * the next next thing I'm working on * ... etc.
Create and ship
Then start doing and creating the first thing on your working on list, and deploy it to your site, no matter how small, no matter how partial a solution.
Ship early and ship often.
Use what you create
Selfdogfood what you create, even small things, because only then will you feel what really annoys you the most and what you should work on next.
Then repeat writing down those itches, and iterate openly.
Examples of IndieWeb community members's itches documentation (feel free to add your own)
- Aaron Parecki
- Tantek's itches for Falcon
- Ben Werdmüller's itches
- David Shanske's itches
- Colin Tedford's wants ("wants" b/c thinking of them as "itches" makes me itchy)