Website redesign

[bast]

Website issues

Discussion points

• list upcoming planned workshops
• make clear that there is follow-up funding
• create historical section with:
  • funding partners up to 2021
  • training hubs
• make clear that gitlab will most likely continue
• Home: lead text mentions future activities for a) learners b) volunteers c) institutions
• define benefits and show how people can contribute
• differentiate "tiers", e.g.: hackmd is available to partners, or an exercise review session is available ...
• who we are:
  • official consortium partners are a basis
  • "community champions"
• list what we want to happen instead of how it is right now

Structure and contents

• Top page:
  • Vision, inclusive image
  • Upcoming workshops
  • How to keep informed
  • give hints on what persons/orgs can do to help/prepare/stay in touch
  • Logos of the funders/partners at the bottom (or somewhere) like at https://fair-software.nl/endorse
    • logos of supporters as well?
  • positive feedback carrousel
• Get involved (becomes a menu)
  • Get involved(how to join?)
    • Light-weight!
    • move "to the left" right after "home"
    • Concrete: where, how
    • Hierarchy/steps
      • Helper
      • Bring your team
      • Co-teach
      • involve orgs etc.?
  • Subpages of "who we are", "Instructors and helpers", "Funding partners", "Training hubs"
  • Meeting minutes
• About
  • meeting minutes -> move under "get involved"
  • project
    • write new and then check old page whether anything important got forgotten
    • split up into history, present, strategy/future
    • rewrite objectives from "project owner perspective" to community perspective
  • history
  • strategy: "in 5 years we will be at ..."
  • where we are now
  • Articles and Reports → move to bottom of "About"
  • move instructors/helpers, "who we are", "Funding partners", "Training hubs" under "get involved"
  • describe also what they do and why one would like to do that
  • Who we are
    • example: https://jupyterhub-team-compass.readthedocs.io/en/latest/team.html
    • example: https://carpentries.org/governance/
    • https://jupyter.org/about
• Workshps/events
• Lessons
  • Separate currently running and
  • Make more clear that some lessons are outdated but could be revived by somebody ("special topics")
  • Merge "Resources"
  • Make clearer which lessons are part of our 6 half-day workshop curriculum
    • could https://hands-on.coderefinery.org/coderefinery/ be the "virtual workshop list" page?
• Blog
• Code repository hosting
  • RB will edit
• Resources: -> move all of that close to relevant lessons
• Move "Funded by NeIC" somewhere into past/present funding
• Refine the interesting points on left of navbar and collect the less important to the right

[bast]

For more context, we came up with this in a meeting with Richard and Naoe.

[rkdarst]

I added one more thing: workshops/{impact,statistics} → about/ . I added redirect pages since these are likely to be referred to by various reports and stuff. (is there a way to do proper redirects?)

[rkdarst]

get-involved/ needed a section name, and somehow get-involved didn't seem right, so I named it organization. perhaps there is a better way

[bast]

I added one more thing: workshops/{impact,statistics} → about/ . I added redirect pages since these are likely to be referred to by various reports and stuff. (is there a way to do proper redirects?)

Example for proper redirects: #606

[bast]

Some tasks I will convert to follow-up issues and mark the task as "done" (example: adding logos of funders/supporters as this will come later and no need to wait for it to be in place to resolve).

[bast]

This big issue split up and followed up in #618, #619, and #620.