Greetings fellow staffly people.
One of the first projects we're making headway on since the shift in the Tech Team structure, is an overhaul of the team hubs page.
To action this, I've created a mock up of how it'd look for the tech team.
This is like…67-81% finished (arbitrary numbers!) with some final tuning needed for the css and layout, but this is about what you can expect.
Overall Design Philosophy
- Each topic needs a quick splash on the hub, and a separate page for additional details
- Information needs to be laid out in a way that is breadcrumb navigable
- All pages related to a team need to be tagged for ease of use. Tags in general are super useful, might as well use them.
- The less raw text on a single page, the better. Wikidot starts to turn in to hell after about 30 pages worth of text (hence why saving the series pages takes forever)
So what goes on that page?
Whatever tabs/pages you already have linked will become pages/subpages of the hub already. I basically deconstructed the tabview on our hub, and turned it in to a sprawling breadcrumb linked hub.
I'd be doing the same for any team who was like "Sure, do the things, gimme a proposal." Tabs/sections become line separated, table-of-contents linked page sections, each with a linked details page.
Overhauling your team's hub
If you'd like this format to be used for your own hub, I'm more than willing to take specifications from any other team, or you can just go "That's pretty Magnus, fix your bot" and live with the current.
If you'd like this formatting to be applied to your hub and/or you'd like your hub overhauled, please have your captain respond to this thread, with a specification of any major deviations from the linked format
Project specification will be tracked on my sandbox tech team project workbook.
Feedback is appreciated, and this should be replacing the technical team hub by 1/1/2018, unless there's serious objection.
