Date: Friday, January 13, 2017
Attendees: Brian, Carol, Cameron, Charnpreet
Target next meeting date: Friday, January 27, 2017
- Continue design work on theme
- Investigate cards and user testing (optimalworkshop.com)
- Check if Cameron's design of single Sphinx page can be easily implemented for Jupyter RTD docs i.e. colors, fonts
- Continue prototype of a Jupyter theme based on work done by Charnpreet. Repo is now on Cal Poly Jupyter organization.
-
Apple
- top level navbar you can tell where you are i.e. Distribute (greyed)
-
Wolfram Alpha
- https://reference.wolfram.com/language/
- Embodies "don't make me think" principles
- Users make one choice - what am i trying to do now
- UI cards are focused on user tasks and goals
- Home page easily leads to finding something -> you are looking at is what you want
- Dropdowns - detailed enough that you don't have to go further down in more dropdowns
- flat dropdown documentation structure instead of lots of levels
Addressing these will come after finding a user friendly and effective design.
- JupyterHub federated docs - Consolidated repo using Git submodules for individual projects Repo Rendered docs
- sentry - armin ronacher (flask/jinja) Docs Repo
- openstack
- Jupyterlab
- Notebook
- JupyterHub
- message subprojects
- developer oriented
- design
- governance
This navbar would be available across everything - website, documentation, nbviewer.
- Jupyter
- Install
- documentation
Consistent Documentation band that persists on all pages
- title: Documentation
- search box global
Smaller topic boxes
- design: color
- card - overlay or on card itself
- top level navbar
- sphinx documentation
- main site header
- nbviewer tool bar
Considerations for nbviewer:
- widgets
- custom mime types
- altair notebooks in nbviewer
- dark grey looks really good on all things jupyter
- See social media updates with dark grey - work by Spoo
Card design testing - card sorting
dendrograms
Tree testing - discoverability (TreeJack)