Redesign: Team Page: copy

[Cleop]

@markwilliamfirth the existing Team page has no real copy (aside from team member names/ roles). We did discuss having a bio or similar for team members at one point. Is this still something you'd like to include? If so, will you be writing them or should we give people pointers to write their own?

[ghost]

I think there are still a range of ideas surrounding the team page

I think we're going to need two pages

1. Community Page dwyl.com/join

Our Community

dwyl is a worldwide community of over 350 creative technologists that continues to grow.

We have people contributing remotely to our open-source projects from Angola, Argentina, Australia, Bali, Belgium, Brazil, Canada, China, Colombia, Estonia, Kenya, New Zealand, The Netherlands, Portugal, South Africa and the USA.

[Button] Join Us (links to GitHub join link)

Our development services are led by our core team[links to meet the team] based in London, UK. This is a troupe of 20 talented individuals with diverse backgrounds and a range of experiences and technical expertise.

With something like this underneath/in the background: dwyl/stars#18 (comment)

2. Meet the Team Page

Meet the Team

image
name
job title
twitter
GitHub
Bio (50-100 words each in first person) - similar in length to https://buffer.com/about/team
bio can perhaps appear on hover/click on desktop or click on mobile?
I like this: https://pusher.com/team

[Cleop]

Thanks for this @markwilliamfirth - would you like both to be individually accessible from the navbar or will they both come under Team and then be accessed/ flicked back and forth from the team page?

[ghost]

Twitter handles:

cleopearson
harrygfox
iteles
justenbarget
mskatbow
markwillfirth
nelsonic
robstaIIion
simon_lbd
shouston33
conorc1000
carlisle_jack
daniel_whyte
naazahmed11
inbarnoga
sohil_is
tonydaly
mk411192
FinnHodgkin
zooey_miller

[ghost]

#282 (comment)

I think there should be an 'About Us' in the nav bar, this folds down into

• Our Mission (this is the page with the dictionary definition on)
• Our Community (but this also has a link to meet the team as described above)
• Meet the Team

Kinda like this

[Cleop]

Thanks @markwilliamfirth - when you say 'Our Mission', would you like this to replace the values page? or just take the dictionary bit from the values page and the rest of the values page exist separately?

Also, how would you like this to look on mobile for the mobile navbar as that already drops down vertically?

[ghost]

Yes - let's move that page under this umbrella

Let's call them:

Mission & Values
Our Community
Meet the Team

^This will likely evolve - we might have a partnerships section in future for example

Happy for hear feedback from you or @harrygfox here with regards the infrastructure architecture

Also, how would you like this to look on mobile for the mobile navbar as that already drops down vertically?

This is a good solution for now:

On click:

With regards to using this design as a reference:
Don't make everything uppercase - keep capitalisation consistent as we discussed #234
Having a subcategory nav colour to signify difference to the user will be useful (doesn't have to be red obviously)
Please also indent subcategories slightly to show this more

[harrygfox]

@markwilliamfirth I've had a good old think about this (again, thanks for everything you've put in to it) and here's the long/short of it:

I think we should consolidate these three pages into a single point of entry: an About page acting as a Values & Mission page, containing links to the (separate) Community and Meet the Team pages (not forgetting the sitemap links in the footer).

• Fewer links in the navbar is generally a good thing for conveying a clear 'call to action' - ours, right now, being 'sign up'. My understanding from the last design meeting I attended was that streamlined focus on the goal du jour is a necessary business decision (@nelsonic).
  a good example of this is seen on duolingo:
  Navbar
  
  Footer
  
  Duolingo's website is SO focused that there is only one link on the navbar. We'll get there eventually! 👍

• Asking the user to reveal content to them creates usability/acces'ty issues.
  I know this is one of the simplest of all: tab to reveal, hover to reveal, click to reveal etc. My concern is that resolving each of these and their various conflicts/browser support etc AND adding a vertical accordion to the navbar is going to add unwanted and unpredictable development time in build and maintenance.

What dya reckon?

[ghost]

@harrygfox happy for you to override any design decisions above as you are the Design Lead - do you know when @Cleop can expect the final site designs? She's currently in active development, so would be good if we could get them to her soon.

[ghost]

Closing as complete