You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 13, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 13, 2026. It is now read-only.
We want to show who the organizers are and what their role is.
Why this is valuable:
This will help people get a sense of who runs the community and give organizers an ability to feel seen as a thank you for all the hard work.
Acceptance Criteria
There is a page at writespeakcode.com/about-us
The Page has a separate section for photos/bios in this order: board members, chapter leaders, organizers, and website contributors.
The data for the page is managed in a data file and pulled in via a page query.
Development Plan
Oct 11 - Nov 8
Discovery around other about pages. Questions to ask: How are roles distinguished? What data is displayed?
https://designsystems.nyc/ - I like the speakers and organizers section here. The simpler the better, minimal interactivity at least for the first iteration and less barrier to content.
@nayonnapurnell I'm happy to take the lead on the design and the gathering of organizer data on this one. The other next step in this one is to add the organizer content type to the CMS config file - do you want to take that on?
Yes. I am okay with that. So, I don’t need to create the page? I just need to add content right?
On May 7, 2019, at 2:18 PM, Nicola B. <notifications@github.com<mailto:notifications@github.com>> wrote:
@nayonnapurnell<https://github.com/nayonnapurnell> I'm happy to take the lead on the design and the gathering of organizer information on this one. The other next step in this one is to add the organizer content type to the CMS config file - do you want to take that on?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#17 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AENZO7N4NPAXBNVZ3Z5FBTTPUHBWZANCNFSM4HF27CGQ>.
I turned the About page issue into an epic and am going to break it up into smaller tickets. I assigned. you to the issue above ^ which is the smaller task you can get started on while I gather information and draw up the design.
For designs I'm thinking something like this similar to the sponsors section on the landing page:
For each person something like this. This would require adding an optional city to the organizer data.
I also think it would be nice to put the conference organizers for 2019 on the conference page too. This would require adding a list of conference years to the organizer data.
@deweydell Do you envision this being a distinct page or a section of the landing page? Right now, I've set it up as the latter.
Also, any update to designs? I think I remember the sponsorship design changing a bit between May and the conference. If not, no worries. I can give it a go and we can revise in review.
@halfghaninne I would like it to be a separate page! It will eventually contain everyone involved in the org, so it will be pretty big.
Re: design. Can you start working on it just getting the data up and rendering the people in each section? I can draw up some screenshots of what I think it should look like, because yeah I have some new thoughts now. Part of the dev approach also can be gathering some inspiration from other about pages/team pages that we like.
@halfghaninne some sketches for the design implementation! Though for the image, I'd like to use the photo of all of us on stage at the 2019 conference. For the first iteration, let's implement something like what we did for 2017/2018 organizers (but with navy text on white background and link styles that match our current design).
I like the idea of "cards" or something that can show more info for board members, chapter leaders and main organizers, but that can be 2nd iteration.
@deweydell Sorry I didn't see your message from a couple weeks ago! No help per se, though it would be helpful to have access to netlify logs to see why my PR builds are failing! I'd also love some feedback on the look of the page so far.
Oh! I also have a question on page interactivity. I've left out bios on the first pass at the organizer components, but we've collected the information. Do we want to include an extended view of each organizer that includes their bio (similar to the speaker dialogue part of the 2019 conference page)? Or do you want to leave it out for this iteration?
Ok nw, I look into adding you to netlify and check out your page locally and leave some feedback.
Let's leave bios out for now. In the meantime DMing you the netlify log failures on slack.
Activity
deweydell commentedon May 7, 2019
@nayonnapurnell I'm happy to take the lead on the design and the gathering of organizer data on this one. The other next step in this one is to add the organizer content type to the CMS config file - do you want to take that on?
nayonnapurnell commentedon May 7, 2019
deweydell commentedon May 7, 2019
I turned the About page issue into an epic and am going to break it up into smaller tickets. I assigned. you to the issue above ^ which is the smaller task you can get started on while I gather information and draw up the design.
deweydell commentedon May 16, 2019
For designs I'm thinking something like this similar to the sponsors section on the landing page:

For each person something like this. This would require adding an optional city to the organizer data.

I also think it would be nice to put the conference organizers for 2019 on the conference page too. This would require adding a list of conference years to the organizer data.
halfghaninne commentedon Oct 5, 2019
@deweydell Do you envision this being a distinct page or a section of the landing page? Right now, I've set it up as the latter.
Also, any update to designs? I think I remember the sponsorship design changing a bit between May and the conference. If not, no worries. I can give it a go and we can revise in review.
deweydell commentedon Oct 6, 2019
@halfghaninne I would like it to be a separate page! It will eventually contain everyone involved in the org, so it will be pretty big.
Re: design. Can you start working on it just getting the data up and rendering the people in each section? I can draw up some screenshots of what I think it should look like, because yeah I have some new thoughts now. Part of the dev approach also can be gathering some inspiration from other about pages/team pages that we like.
deweydell commentedon Oct 19, 2019
@halfghaninne some sketches for the design implementation! Though for the image, I'd like to use the photo of all of us on stage at the 2019 conference. For the first iteration, let's implement something like what we did for 2017/2018 organizers (but with navy text on white background and link styles that match our current design).
I like the idea of "cards" or something that can show more info for board members, chapter leaders and main organizers, but that can be 2nd iteration.
deweydell commentedon Oct 19, 2019
Here's the photo I like for the main page
deweydell commentedon Nov 11, 2019
@halfghaninne do you need any help with this page?
halfghaninne commentedon Nov 24, 2019
@deweydell Sorry I didn't see your message from a couple weeks ago! No help per se, though it would be helpful to have access to netlify logs to see why my PR builds are failing! I'd also love some feedback on the look of the page so far.
Oh! I also have a question on page interactivity. I've left out bios on the first pass at the organizer components, but we've collected the information. Do we want to include an extended view of each organizer that includes their bio (similar to the speaker dialogue part of the 2019 conference page)? Or do you want to leave it out for this iteration?
deweydell commentedon Nov 24, 2019
Ok nw, I look into adding you to netlify and check out your page locally and leave some feedback.
Let's leave bios out for now. In the meantime DMing you the netlify log failures on slack.