The Key Principles of the IndieWeb.

β€” Own your data, content, metadata and your identity.
β€” Publish data for humans first, machines second.
β€” Scratch Your Own Itches. Make tools, templates, etc. for yourself first.
β€” Use what you make!
β€” Document your stuff.
β€” Open source your stuff!
β€” UX and design is more important than protocols, formats, and data models.
β€” Build platform agnostic platforms.
β€” Longevity. Build for the long web.
β€” Plurality.
β€” Have fun.


Although I very much like the initiative, I have to disagree that UX and design is ought to be more important than protocols, formats, etc.

Personally, I think it is the other way around; form follows function. More than often, that exact principe is the foundation of open source. But hey, just my two cents.

@h3artbl33d Reading through their guidelines, it seems like they work like this: Prototype first, and implement function later. Their approach to dogfood is, create content and a front-end first, build managerial tools later, based and around that content.

Β· Β· 1 Β· 1 Β· 1

@neauoire Might be dependent on the phrasing I guess. Most software is developed to satisfy a need, to achieve a certain goal.

From that perspective, I'd say the architecture comes first, function second and user interface third and last.

@h3artbl33d Yeah, that's the thing right. I'm sort of defending IndieWeb's approach even tho it's not personally how I am doing things now. But their thinking is that the specs will adapt to the person's designs(xml classes), and the designs do not have to adapt to their specs(json-ld).

@neauoire Interesting and valid point! Didn't think about it in that way. Spending too much time with web hipsters can mess with one's mind.

Sign in to participate in the conversation
Sunbeam City 🌻

Sunbeam City is a anticapitalist, antifascist solarpunk instance that is run collectively.