.coop will hold our eighth session in the .hour series on the fourth Monday in May:
Sophie Bloemen (Commons Network, European Municipalist Network, ROSA - Right to the City Amsterdam)

Public-civic collaboration, coop incubators and stewarding digital infrastructure as a commons

Sign up and details here:

Work in progress at - a handbook of protocols in provisioning a digital commons

VERY provisional and incomplete, being augmented thro . In time though, it aims to be means for a kind of college of transformative digital infrastructuring in support of Making the Living Economy.

It's in gitBook temporarily. Looking for a good open-source toolset that supports nested levels of documentation, book-style. Not convinced by the popular tools among hackers

@mike_hales Definitely urge Social.Coop members to check this out. The Meet.Coop Commons Hours are a unique space for thinking about how to collaborate and build commons. As members of Meet.Coop it is a great way for us to participate in the cooperative.

> Looking for a good open-source toolset that supports nested levels of documentation, book-style. Not convinced by the popular tools among hackers

Alas, you probly won't be convinced by - that @lynnfoster used for (to replace gitbook).

She liked it pretty well, though.

Could you point-up an instance of the Drupal book module, thanks. Although . . we wouldn't be in a hurry to adopt AN Other suite of software in our stack.
@bhaugen @lynnfoster

@mike_hales @bhaugen @lynnfoster

This site needs work but shows the basic book module functionality. Book is part of drupal core, so it is well maintained. I am using BackDrop, a variant of Drupal, thanks to @clayton

Thanks Matt. Without a login I can't see much of the content? What I see suggests that navigation isn't thro a sidebar.
@bhaugen @lynnfoster @clayton

@mike_hales @bhaugen @lynnfoster @clayton How much can you see, I am curious. I will need to adjust permissions/publishing status.

Prompted to look again, I can access much more than I first thought. The link you gave as a starter didn't obviously give me an overview or a nav menu. This is bcos it's a VERY long scroll, and the structure of the site only is displayed at the end.
This is the kind of situation where I would be wanting to break out content into smaller segments, and provide a nav sidebar aka contents list in continual view.
Permissions seem fine, it's nav clues that need work.
1of several

@Matt_Noyes 2of?
Thus I hadn't appreciated that it's a handbook. I guess I didn't take enough time to start reading and I only discovered chapter 1 chapter 2 etc after being prompted to come back and look more carefully, and scrolling down a long page.

<About> doesn't seem to lead anywhere. It might be good to put a pointer there to a page that REALLY starts the reader off on a trail? I'd expect <About> - as a first port of call - to help navigate, as well as describe the site's context?

@Matt_Noyes 3of4
The root (Home) page presents content as a blog, which is always a hard format to search in. It gives no hint there's a handbook there too.

Where *IS* the starting point?
- The root page
- About
- The 'horizontal' page
There is NO path from the Home page to what actually seems to be the basic navigation page, the 'horizontal' page. And that one displays the site structure WAY out of sight, a 100 scrolling miles away!

@Matt_Noyes 4of4
The constant presence of a login sidebar made it seem (to this visitor) as if access is member-only. Given how MUCH content is in fact available 👏 it would be good to make this plain on every page? Like, a sitemap?

Breadcrumbs are fine, but no subsitiute for a contents list?

Yes, a bit of work on navigation and transparency would do justice to how much work there is lurking on the site!

I feel confirmed though, in my wish for a sidebar, displaying a nested hierarchy of pages

@Matt_Noyes 5of4
Actually, I would like to see this site as a wiki (federated wiki). When I get a free hour I might just hack a version, to see what you make of it. My perception is, fedwiki is great for collaborative exploration and make-your-own scapbook-handbook-commonplace books.

I'll do this in, which is a nascent wiki hosting coop - no public face yet. But

@mike_hales apologies, I should have explained that my plan is to recreate the side navigation it used to have before migration to mayfirst. Easy to do. It also had a box on the right for tags, another means of navigation, and the books were listed in blocks on the home page as well as the top nav bar.

This all sounds good, covers all the bases by the sound of it :) Do keep me posted, I'd like to see how it looks with these additions.

What kind of hosting does MayFirst provide? D'you yourself have to maintain the instance, does MayFirst do that, does clayton have an admin role?

PS One final grumpy-old-typographer comment - your line lengths are a little short? 60=70 characters per line scans well, is a book typography norm. Your lines are nearer 55?

@mike_hales Clayton helped migrate the site to a new version of drupal and a new version of php, but as Malcolm X used to say the mistakes are all mine. Line lengths can be changed, probably in CSS. First step is to edit the handboom and do a print edition, then fix up the site.

My sense is, mkdocs is rather too close to being a fileserver management system for discrete docs (nice for folks who handle files & folders all the time, dev or admin-fashion). And what a handbook needs is something that you write as a hypertext, in pretty-much wysiwyg mode, oriented to the experience of reading. Also, with more nesting in the nav menu than mkdocs seems to offer.
Outline looks nice for example. Comes as a hosted platform service

Sign in to participate in the conversation

A Fediverse instance for people interested in cooperative and collective projects.