Skip to content

Instantly share code, notes, and snippets.

@mnyrop
Last active July 21, 2023 20:52
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save mnyrop/8c392818e6340e8b58d8644791c329ea to your computer and use it in GitHub Desktop.
Save mnyrop/8c392818e6340e8b58d8644791c329ea to your computer and use it in GitHub Desktop.

Marii and Alex meet to plan the future of Wax…

Here are some of the ideas that surfaced

Note: Checkboxes designate if a tangible issue has been created and added to project board.

  • wax_tasks#91 > Produce separate JSON file instead of adding to data CSV #tasks
  • Namespace wax-protected fields (e.g., wax:full_image wax:largest_image wax:thumbnail wax:iiif_manifest) #tasks #theme
  • Allow config of metatada dictionary in item layout without having to edit layout directly #theme
  • Make variables configurable for OpenSeadragon #theme
  • Take out Wax configurations out from _config.yml. Maybe put in _data folder? #theme
  • Be less opinionated about image sizes, warn but let them figure it out #tasks iiif
  • Make image derivative depth configurable (e.g., zoom level) #tasks iiif
  • Make simple theming changes easier via Sass vars #theme
  • Use tailwind(?) or other non-bootstrap scss framework #theme
  • Explore ways to bring in data/md into item pages more seamlessly or generalizable. #tasks
  • Make a wax thor cli package versus invoking with rake #tasks
  • Add GitHub Actions template to kit version #meta
  • Redo documentation #docs
  • Add simple multi-language support via core theme or recipe #theme #docs
  • Minify, compile, optimize--just go as far as we can pretending this is React. #theme
  • Make it easier to use remote manifests (can test integration with aperitiiif) #tasks
  • Use the vips upgrades to wax_iiif that are hiding in a branch. Make vips vs imagmagick requirement change clear in docs. #tasks #iiif #docs
  • Consider deprecating Dockerfile? #kit
  • Create wax_theme repo and move all the jekyll theme files to it. #meta

    Note: Recommend folks fork the theme if they want to do lots of customizing and load theme from their fork; core theme should support basic theming from sass vars overrides.

  • Convert wax repo into demo & flagship repo that it kind of is already, but load theme from theme repo & keep things clean & simple. Include some "kit" features, e.g., "Here's all the stuff put together for you, with gem theme & gem tasks loaded, github actions ready to publish to gh-pages for you" #meta
  • wax#105 > Move tests from wax into wax_tests repo; load from gem into wax kit but make it easy to remove from gemfile & drop the dependencies (e.g., html-proofer and nokigiri which are slow) #meta
  • Create a v1 folder within wax wiki and move current docs into it for archive viewing. #docs
  • Integrate behavior from wax-facets #theme
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment