-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Design: About Page: Advisory Network Members #43
Comments
Currently each advisory network member has their "team-title" listed (see: e.g. https://docs.google.com/document/d/17v8kB_BhnIYy-Cy741dc3J12KBmD7vKlonoBMg5CH8g/edit) but we can do something like: team-title: Spaghetti Carbonara advisor for 349 and proud or organization: 349 and proud or organization: 349 and proud ...all are just as well to me |
I vote for option one: If that's the case then in terms of styling only the part that serves as a hyperlink should be grey and underlined. |
Let me know if help is needed with formatting of these? (Also, I confess I've been ignoring notifications from GitHub but will pay more attention from here on in -- if anything's awaiting my input or action, please let me know!) |
@daveomitchell I'd like us to revisit this now that we're rebuilding and format the doc correctly so it doesn't say "Advisory member" under each member. @rapicastillo the screenshot above should be the correct stylization |
@adrian-the-git would it be possible for us to have an attribute under the person for a |
Under each of the advisory network member's names we were supposed to have a hyperlink to their organizations. Right now it's says "advisory network" under each with no hyperlink.
Screenshot reference from ai file

If we're not planning to have the names of their organizations associated with them we should remove "advisory network" from under their names. It's repetitive otherwise they're already in the "advisory network" section.
The text was updated successfully, but these errors were encountered: