Review some tool options for sustainable interfaces

[anjackson]

• Customising Datasette-Lite to explore datasets in the GLAM Workbench
• https://simonwillison.net/2020/Mar/9/datasette-search-all/ and the idea of search slices
• https://sqlite.org/wasm/doc/trunk/index.md
• https://www.npmjs.com/package/sqlite-wasm-http
• https://duckdb.org/2021/10/29/duckdb-wasm.html
• https://observablehq.com/framework/
• https://preset.io/
• Database-like systems, good at tables, but poor at long text, no support for e.g. a field that holds a list of strings:
  • https://docs.nocodb.com/
  • https://baserow.io/docs
• Google Sheet
• Collaborative bookmarks like Raindrop.io e.g. https://raindrop.io/anjackson/digital-preservation-48120476
• CMS-like systems, better at long text and lists:
  • DecapCMS
  • https://github.com/sveltia/sveltia-cms
  • https://pagescms.org/
• https://jamstack.org/headless-cms/
• Prose.io and GitBook don't do the structured data part
• https://tina.io/ cloud version pricing model not great for crowdsourced work
• https://contentrain.io/ commercial option
• DecapCMS https://decapcms.org/
• StaticCMS
• https://github.com/sveltia/sveltia-cms#readme
• For static search https://pagefind.app/
• mkdocs
  • eBook/PDF support: https://github.com/ebadi/mkdocs2book https://pypi.org/project/mkdocs-with-pdf/
  • mkdocs material is very nice and as used by GLAM Workbench
  • https://squidfunk.github.io/mkdocs-material/reference/tooltips/?h=gloss#adding-a-glossary
  • https://mkdocs-macros-plugin.readthedocs.io/en/latest/
  • https://facelessuser.github.io/pymdown-extensions/extensions/superfences/#custom-fences
• mdBook (Rust version, v plain but nice theme)
• Zotero combined with something like zotsite

Academic related work:

• https://chrisdaaz.github.io/static-web-scholcomm/
• Tools and Workflows for Collaborating on Static Website Projects - code4lib
• Using Static Site Generators for Scholarly Publications and Open Educational Resources - code4lib

Themes separate

• Jekyll:
  • Just the Docs
  • https://github.com/hyperrhiz/jekyll-journal
  • https://github.com/lawrennd/proceedings
  • https://github.com/archipelagosjournal/archipelagos
• Hugo:
  • https://jpanther.github.io/congo/
  • https://imfing.github.io/hextra/docs/guide/configuration/#search-index
  • https://lotusdocs.dev/docs/
  • https://www.docsy.dev/docs/
  • https://getdoks.org/docs/start-here/getting-started/
• https://sphinx-book-theme.readthedocs.io/en/stable/sections/header.html

All related to the digipres/digipres-practice-index#4

Consider also options for live environments/tool support:

• Binder
• https://www.gitpod.io/
• Codespaces
• Jupyter
• Linux+Mac Homebrew formulae for specialist tools.
• etc.

We should probably lean towards getting them using CLI stuff rather than making tool UIs, I think? That's the long-term capability. Browser-based tools are a hack around faulty infrastructure? General sustainability of UIs...

[anjackson]

Also looking at this in the context of the learning resources work.