Dynamic Routing and Navigation aka Header

[zaudtke]

After talking with @csell5, I started looking into changing the WI 2021 Event to use the dynamic routing capabilities available instead of needing to recreate/copy the structure for other events such as TX 2021 or WI 2022 as examples. In addition there was a conversation around how the top level navigation is no longer consistent.

Due to this, I’d like to start a discussion on:

• Clarification / Verification of Assumptions I made
• List of things that should probably now be dynamic that aren’t available in the Api
• Plan of attack to break this down, and make it a reality.

Assumptions

1. The site was started with WI2020, and as it has expanded, an effort was started to go from Default layout to a new Root Layout, which are very similar, with the Header (Navigation) being the biggest difference. It is assumed that the the desired outcome is 1 Header for all pages (single day event, multi-day event, stand alone pages, etc). Assuming this is true, while a simple change, there are few things to consider.
   • Lose Message In Top Left
   • Lose Top right Event Location/Name
   • Secondary Nav of Event is weird (Logo, Links, Signup Mailing)
2. To Use Dynamic routing for Events, it is assumed All Multi Day Event Index pages are the same structure Layout (One Day Events already are setup this way)
   • Hero
   • Learn More
   • What to Expect
   • Speaker Highlight - Currently commented out
   • TimeLine
   • Sponsor Highlights
   • Testimonials
   • Newsletter
   • Bottom Image
3. Dynamic routing also assumes that pages within an event (other than the index) will be the same for every event in general. There are ways to override dynamic routing when specifically needed.

Dynamic Data

1. Dealing with Coming Soon (ie TX 2021)
   • Override routing
   • Logic based on data
   • New Data in Api
2. Various Images - Per Event?
   • Cartoons
   • Photos
3. Static Text
   • Themes? i.e. Camping in WI vs ??? in TX
   • Not sure if actual issue
4. Links
   • Just Fix em
5. Meet Campers (Staff Photos)
   • Per Event?
6. Newsletter Signup
   • Per Event?
7. Speaker Highlights
   • Per Event
8. Testimonials
   • Per Event?
9. Footer Links
   • THAT - OK
   • WI - Show even on pages outside of Event
   • Resources - Link to Event Specific pages.
   • Policies - OK
10. Plan Your Trip
    • Map Link
    • Other Hotels
    • Planes/Trains/Automobiles
11. Active Hosted
    • Uses Id 1 everywhere except Become a Partner.
    • Event Specific
12. Slug Splitting default pages
    • WI/2021 is the Slug, but also a route
    • Currently have a redirect at /WI hard coded to /WI/2021
13. More I probably missed.

[zaudtke]

More things:

I tried added [eventSlug] in the Root of Pages to look at overrides. It failed, because there is also a [markdown].js route used as a catch all for more content based pages. Next can't tell tell the difference between them.

The root [markdown].js page is currently being used for:

• Anti Harassment Page
• Code of Conduct Page
• Commitment to Diversity Page
• Copyright page
• privacy policy page
• terms of use page.

[zaudtke]

While looking at previous Markdown issue, I found a different one related to Event Specific markdown files.

WI/2021 has a [markdown].js file as well, which is used for the pages listed below. The problem with these is specifically that there is now a folder structure of markdown/WI/2021/*.md file, so any other event year would not be able to use these.

Pages in WI/2021 affected:

• Attendee Handbook
• Counselor Handbook
• Counselor Submission FAQ
• Family Handbook
• FAQ

[zaudtke]

Just to make sure things are not lost.

1. Sign In Link not visible on Mobile (new Header). Should be addressed as this is built out, just don't want to lose it.
2. How to deal with Message Bar in Header? Previous Implementation was based on an Event, then look at Notifications for isFeatured. What to do if on a page that isn't a specific event?
3. All Event Id's are set to read from env variables, and are hard coded to WI2020 at this time. Needs to be changed to read from route.