This pack will let editors add pages if a doc owner allows it.
I asked Coda before making this.
It removes the hard hit on wiki-heavy teams where editors want to make pages just for content.
That said, it’s not a replacement of upgrading. There’s plenty of motivation to become a Maker (or a Champion and get Coda for free ).
I hope this is interim and Coda works on features to support the wiki folks better, e.g. by launching “rows as pages” eventually (an option to show canvases from a table as subpages on the left pane)
Coda 4.0 comes with a permission change: only Makers can now add and manage pages. While to me it makes a lot of sense, this change will make a lot of wiki people unhappy. They’re used to adding pages extensively not so much for “doc structure” as simply for “content structure”.
This pack is meant to be a temporary relief. It allows the doc owner to install a button that will allow editors to add pages to that doc.
- Only the doc owner can install the pack
- Can only access the doc it’s installed on
- Handy autocomplete for the parent page
- Autocomplete for page icons (default icons only, no custom icons — but you can always just type in the icon id)
- Free & Open Source
This pack uses Coda API, which has endpoints for creating and primitively editing doc pages. These endpoints will be unavailable to editors but stay functional for doc makers. Since the packs platform is designed to make requests on behalf of the person who installed the pack and created the connection, this remains a valid way for a maker to consciously allow editors to add pages to their doc.
While this pack provides a relief for page-hoarding workspaces, it’s not a full replacement of becoming a Maker. There is no API methods to delete or reorganize pages — this is still limited to Makers only. And aside of that, there’s plenty of reasons to upgrade
As one of the most devoted Coda makers, I want to see this platform grow and thrive. I understand and welcome that Coda wants to encourage more ‘passive’ users (viewers, editors) to convert to makers. But knowing Coda for a long time, I also know that they would never abandon their less-spendy audience. I’m sure the reason for this change comes not from the place of greed but to encourage better practices of working with docs. Paywalling isn’t a motivation to upgrade — if anyone wanted to game it there’s plenty of ways already (in the worst case the whole team could just share one login and password.) Offering the convenience of being a maker on your own is.
I’m also sure that until this change comes into effect in November, the team will keep on looking for a way to support wiki scenarios in a way that will be better designed than what we’ve had before. One of such features could be an option to display all canvases from a table as pages on the left navigation pane — I know this has been explored internally and I hope this makes it to the roadmap.
Lastly, before making this pack I ran this idea by Coda, and they were okay with it. This API capability is not going anywhere, so someone would’ve found it eventually anyways. There’s plenty of Coda API packs already, from generic (e.g. 1 2 3) to all-encompassing ones, which already enable this. I just made a specialized one that hopefully provides a little better UX than the rest, and also more security (by not allowing all the API modifications there can be but restricting it only to pages)