Wire Frames for Hyku MVP

[adamjarling]

Create generic wireframe templates for the following pages which can be shared between Samvera websites (Hyrax, Hyku, Avalon)

• Home
• Blog List
• Blog Entry
• About / Generic
• ?

[heathergreerklein]

A working group put together a preliminary sitemap that could be relevant to the other platforms as well (under "what is important to Hyku?").

[heathergreerklein]

Top level menus in caps:

FEATURES & IMPLEMENTATIONS

• Current release features
  • Roadmap
  • Path to implementation
  • Hyku vs. Hyrax
• Implementations
  • In Production
  • In Development

GETTING STARTED/WHAT IS HYKU?

• Hyku & Samvera
• Documentation
  • User Documentation
  • Links to Dev Documentation/ReadME
  • Link to Repo
  • Documentation on Docker & Kubernetes
• Community
  • Hyku Interest Group
  • Hyku Dev Call
  • Samvera Slack #hyku
• Glossary

LEARN MORE ABOUT HYKU

• Demo (repo.samvera.org?)
• Presentations
• YouTube
  • Official Hyku
  • Hyku for Consortia
• Service Providers
• • Samvera.org
• FAQ
• History

BLOG

CONTACT

[adamjarling]

@heathergreerklein Will these top level navigation items noted above serve as generic navigation items for the Hyrax and Avalon sites as well?

Also, thinking through the Hyrax MVP project, and how to handle linking up top level navigation and subnavigation, here's a few ideas. NextJS for example uses file system based routing, which means if a project has directories like this:

/about
- me.jsx
- our-organization.jsx
/news
- latest.jsx
...

Then the routes are automatically created when the app builds. So the process would be:

1. Defining the route in the project code, file structure
2. Plugging these value into Contentful CMS, in an order which the Admin prefers.

We can think more through this to get the easiest solution.

[heathergreerklein]

Top level menus in caps:

Template Menu:
FEATURES & IMPLEMENTATIONS
GETTING STARTED
LEARN MORE ABOUT HYKU
NEWS
CONTACT

FEATURES & IMPLEMENTATIONS

• Current release features
  • Roadmap
  • Path to implementation
  • Hyku vs. Hyrax
• Implementations
  • In Production
  • In Development

GETTING STARTED

• Hyku & Samvera
• Documentation
  • User Documentation
  • Links to Dev Documentation/ReadME
  • Link to Repo
  • Documentation on Docker & Kubernetes
• Community
  • Hyku Interest Group
  • Hyku Dev Call
  • Samvera Slack #hyku
• Glossary

LEARN MORE ABOUT HYKU

• Demo (repo.samvera.org?)
• Presentations
• YouTube
  • Official Hyku
  • Hyku for Consortia
• Service Providers
• • Samvera.org
• FAQ
• History

NEWS

CONTACT

[heathergreerklein]

Create folders for each of the top level navigations in the site. Model in each for updating from Contentful. Template can create a subnavigation for sections of the page from above the fold. Every admin can set these as they want with the same template.

[adamjarling]

@heathergreerklein @DraxIndustries79 Maybe something like this for a wireframe on the landing page?

[heathergreerklein]

This is perfect!! What is our next step?

[adamjarling]

@heathergreerklein Thanks for adding me as a Samvera org admin. I created this repo, and will start wiring things up...

https://github.com/samvera/hyku-next

[elynema]

Firstly, this looks great, and Jon Cameron and I are excited to try moving the Avalon website to this infrastructure as well.

We took a look at the top level menus here with regard to the Avalon site. Our biggest question was whether the sub-menus can be modified to fit Avalon's needs. Looking at the Hyku site in progress, it looks like the answer to that is yes, as it doesn't actually have a sub-menu nav, just content in the page. For example, under LEARN MORE, Avalon would not have Youtube or Service Providers categories.

We might want sub-navigation for each top-level page, which looks like is available in the template, too.

It looks like the LEARN MORE heading was dropped in favor of PRESENTIONS and DEMOS on the Hyku site, which would work well for Avalon.

I personally might suggest CONNECT instead of CONTACT since that takes you to Slack channel, mailing lists, user meetings, etc. I assume that's a change we could adjust on our local Avalon site if we want to?

Will this infrastructure support a contact form? We have one that can be used to submit questions to Avalon folks at IU on the Avalon site. That's not a dealbreaker; I imagine we might be able to provide an email address instead.