...
Christine said most of what’s in the list of requirements is very standard; some are already being used at least on the ACO site and/or is in the initial style guide
Julie said the detail in the guide should actually be as detailed - rather than high-level - as possible
Developers said they are looking more for how to design/use various elements of the pages rather than what a full page might look like
JP: We do want to ensure the top banner and footer are identical, but that the middle sections can be different WHILE adhering to uniform styles
They don’t need code, per se, but they need a guide to style
My ACCESS is ready on the back end so we should be able to put that into the guide
Need to determine the selections/what’s in the drop-down list
Andrew says there is a list
Julie says they don’t need code for this, just what it would look like
Discussed News dropdown
ACO is OK with there being a universal dropdown that includes:
News
discussion on how to organize news to pull in from various sites, but also to be vetted for what shows up on the main site
The development team needs to decide how to manage the news that’s on the ACO site and also what’s on the Support news site
Discussed Support’s site being called “Announcements
Events - will be hosted on the Support site, but a dropdown could go there
Discussed Login
What would it look like and what are the dropdown items
Andrew says you’d have a universal login and from there it could be:
My ACCESS - your profile and account info
ACCESSonDemand - you can get to
Resource Providers
Perhaps “Resources” in the top navenav
Team needs to decide where it will go
...