Idno is a group publishing platform that you own. We take the best of personal publishing and apply it to collective storytelling.
In 2013, my mother had a double lung transplant. The rules for recovery post-transplantation are that you can't have a bridge between you and the hospital; they don't want you to be stuck in traffic if you need emergency attention. So we rented an apartment in the Inner Sunset, where we all sat with...
I love Known - it's an elegant blogging tool that supports most Indieweb standards right out of the box. The biggest challenge I've had with Known is getting it upgraded. I host my blog with Reclaim - a great little hosting service with excellent customer support.
If you’re thinking about doing something like WithKnown (aka Known, the CMS your post is on), and interested in the WordPress portion, you might consider doing a full/partial Domain of One’s Own program through Reclaim Hosting or even rolling your own. Even if you go small with just a few classes, you might consider adapting the Homebrew Website Club model at your site where you invite students to tinker around, help each other out, and then show off or demonstrate their work. The related IndieWeb wiki and online chat are free to join and can provide a wealth of information and help for students (and educators!) working at owning their own domains.
Incidentally, if you’re unaware, WordPress now has a suite of plugins that will allow it to have a lot of the site-to-site communication capabilities that Known does. I’ve not done it before, but I’m fairly certain you could run it on a multiuser installation of WordPress much the same way you’re using http://janevangalen.com/cms/.
Another interesting option would be to have students try out accounts on micro.blog which are relatively inexpensive, though I suspect if you touched base with Manton Reece and explained what you were doing, he might offer free or significantly reduced hosting for a reasonable period of time. I know he’s given away a year of free hosting to attendees of IndieWebCamps who are starting out with their own domains. If he did then you might be able to use some institutional funds to purchase domains for students to get them started.
By the way, good on you for opening up your planning process for teaching and learning on the open web. It certainly sets a useful example for others who are exploring and following in your footsteps.
Tomorrow at 12 PM Eastern/ 9 AM Pacific I’ll be be hosting a Connected Courses discussion that will explore the IndieWeb movement as a people-centered response to the corporate web. How do core IndieWeb principles such as owning your content, remaining better connected, and redefining control online intersect with the values of connected learning? Take a bit of time tomorrow and join myself, Mikhail Gershovich, Ben Werdmuller, Erin Jo Richey, and Simon Thomson to find out more.
[Withknown is] the posterchild of the IndieWeb.
— Jim Groom
I’ll agree that it is pretty darn awesome!
Some slight rephrasings from Ben in the video that I thought were spot on:
IndieWeb: allowing people to connect online without caring about what platforms or services they’re using.
IndieWeb puts the learner first. The LMS, which primarily serves an administrative function, should not be the center of the process.
I've been blogging - albeit not consistently on the same site - since 1998. That's a long time in internet years, and in human years, and over time I've conditioned out any self-editing impulse I might have. I write, hit publish, and share. Done. Because I'm fairly prolific, friends and colleagues o...
Seems like "going Indieweb" has given my online presence a huge boost by checking out the search results looking up myself;— Johan Bové (@johanbove) November 18, 2019
I’ve been running versions of both for many years and they each have their pros and cons. In terms of IndieWeb support they’re both very solid. Why not try them both for a bit and see which appeals to you more? Depending on your skill level and what you’re looking for in your site you may find one easier to run and maintain than another.
Personally I’ve used WithKnown (I’ve used it for multiple sites since it started) in a more “set it and forget it” mode where I just post content there and worry less about maintenance or tinkering around. On my WordPress site I tend to do a lot more tinkering and playing around, particularly because there is a much larger number of plugins available to utilize without writing any of my own code. Lately I am kind of itching to play around with Drupal again now that it has a pretty solid looking IndieWeb module (aka plugin).
Creative Growth 2013 Home show and fashion show (72) flickr photo by origamiguy1971 shared under a Creative Commons (BY) license Plurality stitches a beautiful quilt of complex choices, and each person adds their own unique spin on the #IndieWeb. As long as you wrap yourself in the warmth of #...
Some important changes to Known were merged in over the weekend.
Most notably, (most) external dependencies are now managed and installed via Composer, and not included natively in the repository itself.
This makes updates easier to manage, but it does mean that if you are installing from (or more importantly, upgrading from) the git repository directly, you will need to perform an extra step.
cd /path/to/known; composer install
This is particularly important if you’re upgrading, and your site is a checkout of the git repo.
Well, that was weird. Something had gone wrong with my little PHP script for adding items from my list at reading.am to my WithKnown-powered stream. It ran, reported no errors, and yet produced nothing at the other end. Gorgeous Saturday morning, blue skies and sunshine; what better way to spend it than indoors debugging?
Holiday is on, and apart from relaxing with the family, I aim to look into a bunch of stuff before I'm back at the factory in January. My Indieweb life is coming on well, thanks to Known, and the #indieweb community in London. I attended my first couple of Homebrew Website Club meetups in town in 20...
It’s nice that there are mass-scale projects like WordPress, WithKnown, Get Perch, Grav, Drupal, and a few others which have one or more “IndieWeb-centric” developers working on them that allow those without the coding skills to jump in and enjoy the additional freedom and functionality. The occasional drawback is that those big-hearted developers also fit into the broader fabric of those massively distributed projects and sometimes their voices aren’t as well heard, if at all.
I’m aware of the disruption of the Gutenberg Editor within WordPress v5.0 and how it applies to those using IndieWeb technology on WordPress. I’m sure it will eventually get sorted out in a reasonable fashion. Sadly, throwing out the baby out with the bathwater as it comes to WordPress and IndieWeb may not be the best solution for many people and may actually be a painful detriment to several hundreds.
While it would be interesting to see a larger group of developers converge on building an open and broadly used IndieWeb system as you suggest, it takes a massive amount of work and community collaboration to get such a thing moving. I think this bears out if you look at the lay of the land as it already exists. Just think of the time effort and energy that the core IndieWeb community puts into the tremendous amount of resources that exist today.
Looking back on the past 4+ years of IndieWeb within the WordPress community, I’m really amazed to see exactly how far things have come and where things currently stand. There used to be a dozen or more pieces that required custom code, duct tape, and baling wire to get things working. Now it’s a handful of relatively stable and well set up pieces that—particularly for me—really makes WordPress deliver as an open source content management system and next generation social medial platform that aims to democratize publishing. In terms of building for the future, I suspect that helping to bring new people into the fold (users, developers, designers, etc.) will increase and improve the experience overall. To some degree, I feel like we’re just getting started on what is possible and recruiting new users and help will be the best thing for improving things moving forward. IndieWeb integration into large-scale projects like WordPress, Drupal, etc. are very likely to be the place that these ideas are likely to gain a foothold in the mainstream and change the tide of how the internet works.
While it may seem daunting at times, in addition to the heroic (part-time, it needs to be noted) developers like Mathias Pfefferle, David Shanske, Micah Cambre, Michael Bishop, Ashton McAllan, Jack Jamieson, Ryan Barrett, Peter Molnar, Amanda Rush; enthusiastic supporters like you, Greg McVerry, Aaron Davis, Manton Reece; and literally hundreds of others (apologies to those I’ve missed by name) who are using and living with these tools on a daily basis, there are also quieter allies like Brandon Kraft, Ryan Boren, Jeremy Herve and even Matt himself, even if he’s not directly aware of it, who are contributing in their own ways as well. Given the immense value of what IndieWeb brings to the web, I can’t imagine that they won’t ultimately win out.
If it helps, some of the current IndieWeb issues pale in comparison to some of the accessibility problems that Gutenberg has neglected within the WordPress community. Fortunately those a11ys are sticking with the greater fight to make things better not only for themselves, but for the broader community and the world. I suggest that, like them, we all suit up and continue the good fight.
Of course part of the genius of how IndieWeb is structured: anyone is free to start writing code, make better UI, and create something of their own. Even then they benefit from a huge amount of shared work, resources, and simple standards that are already out there.