The progress portion is coded roughly in HTML with a label as follows:
<li class="bookprogress"><progress value="177" max="465">38%</progress> <label for="">38.0% done; loc 4290-4847 of 12932</label></li>
You could always use <p> or <span> instead of ul/li tags (with some app specific classes to allow the receiving site to create its own custom CSS for display. Otherwise browsers should be able to display a reasonable visual default.
I’d recommend support for pages, percentages finished, and potentially even Amazon’s default location numbers, with the ability to translate back and forth potentially when given at least two of the parameters as a minimum which should allow the calculation of the others. I find in practice that it’s generally pretty rare to have both page numbers and location numbers, but it could happen.
Here’s the description of the book from the publisher:
The world is working exactly as designed. The combustion engine which is destroying our planet’s atmosphere and rapidly making it inhospitable is working exactly as we designed it. Guns, which lead to so much death, work exactly as they’re designed to work. And every time we “improve” their design, they get better at killing. Facebook’s privacy settings, which have outed gay teens to their conservative parents, are working exactly as designed. Their “real names” initiative, which makes it easier for stalkers to re-find their victims, is working exactly as designed. Twitter’s toxicity and lack of civil discourse is working exactly as it’s designed to work.The world is working exactly as designed. And it’s not working very well. Which means we need to do a better job of designing it. Design is a craft with an amazing amount of power. The power to choose. The power to influence. As designers, we need to see ourselves as gatekeepers of what we are bringing into the world, and what we choose not to bring into the world. Design is a craft with responsibility. The responsibility to help create a better world for all. Design is also a craft with a lot of blood on its hands. Every cigarette ad is on us. Every gun is on us. Every ballot that a voter cannot understand is on us. Every time social network’s interface allows a stalker to find their victim, that’s on us. The monsters we unleash into the world will carry your name. This book will make you see that design is a political act. What we choose to design is a political act. Who we choose to work for is a political act. Who we choose to work with is a political act. And, most importantly, the people we’ve excluded from these decisions is the biggest (and stupidest) political act we’ve made as a society.If you’re a designer, this book might make you angry. It should make you angry. But it will also give you the tools you need to make better decisions. You will learn how to evaluate the potential benefits and harm of what you’re working on. You’ll learn how to present your concerns. You’ll learn the importance of building and working with diverse teams who can approach problems from multiple points-of-view. You’ll learn how to make a case using data and good storytelling. You’ll learn to say NO in a way that’ll make people listen. But mostly, this book will fill you with the confidence to do the job the way you always wanted to be able to do it. This book will help you understand your responsibilities.
I suspect that this book will be of particular interest to those in the IndieWeb, A Domain of One’s Own, the EdTech space (and OER), and really just about anyone.
How to participate
I’m open to other potential guidelines and thoughts since this is incredibly experimental at best, but I thought I’d lay out the following broad ideas for how we can generally run the book club and everyone can keep track of the pieces online. Feel free to add your thoughts as responses to this post or add them to the IndieWeb wiki’s page https://indieweb.org/IndieWeb_Book_Club.
Buy the book or get a copy from your local bookstore
Read it along with the group
Post your progress, thoughts, replies/comments, highlights, annotations, reactions, quotes, related bookmarks, podcast or microcast episodes, etc. about the book on your own website on your own domain. If your site doesn’t support any of these natively, just do your best and post simple notes that you can share. In the end, this is about the content and the discussion first and the technology second, but feel free to let it encourage you to improve your own site for doing these things along the way.
Folks can also post on other websites and platforms if they must, but that sort of defeats some of the purpose of the Indie idea, right?
I’ll also try to keep track of entries I’m aware about on my own site as read or bookmark posts which I’ll tag with #IWBCMM (ostensibly for IndieWeb Book Club Mike Monteiro), which we can also use on other social silos for keeping track of the conversation there.
Perhaps as we move along, I’ll look into creating a planet for the club as well as aggregating OPML files of those who create custom feeds for their posts. If I do this it will only be to supplement the aggregation of posts at the stub on indieweb.xyz which should serve as the primary hub for the club’s conversation.
If you don’t already have your own website or domain to participate, feel free to join in on other portions of social media, but perhaps consider jumping into the IndieWeb chat to ask about how to get started to better own your online identity and content.
If you need help putting together your own site, there are many of us out here who can help get you started. I might also recommend using micro.blog which is an inexpensive and simple way to have your own website. I know that Manton Reece has already purchased a copy of the book himself. I hope that he and the rest of the micro.blog community will participate along with us.
If you feel technically challenged, please ping me about your content and participation, and I’m happy to help aggregate your posts to the indieweb.xyz hub on your behalf. Ideally a panoply of people participating on a variety of technical levels and platforms will help us create a better book club (and a better web) for the future.
Of course, if you feel the itch to build pieces of infrastructure into your own website for improved participation, dive right in. Feel free to document what you’re doing both your own website and the IndieWeb wiki so others can take advantage of what you’ve come up with. Also feel free to join in on upcoming Homebrew Website Clubs (either local or virtual) or IndieWebCamps to continue brainstorming and iterating in those spaces as well.
Kickoff and Timeline
I’m syndicating this post to IndieNews for inclusion into next week’s IndieWeb newsletter which will serve as a kickoff notice. That will give folks time to acquire a copy of the book and start reading it. Of course this doesn’t mean that you couldn’t start today.
Share and repost this article with anyone you think might enjoy participating in the meanwhile.
I’ll start reading and take a stab at laying out a rough schedule. If you’re interested in participating, do let me know; we can try to mold the pace to those who actively want to participate.
I’ve already acquired a copy of the book and look forward to reading it along with you.
As I mentioned in my IndieWeb Summit wrap-up, I added support for IndieBookClub while in Portland. IndieBookClub is a little like Goodreads, but built on standards like Microformats and Micropub so that you can post what you’re reading to your own blog.
Now that I’m back in Austin, I’ve tweake...