-
Notifications
You must be signed in to change notification settings - Fork 2
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
Create pages for each chapter #22
Comments
There's currently 2 pages that I know we need:
☝️ feel free to make the urls less verbose if you want. I could imaging something like
chapter pageOn the chapter page I want:
eventually I want sub-pages that describe how to become a sponsor / organizer / host an event, but we can figure that out later IMO. events pageI want a page like the national conference page, but for OYEs https://www.writespeakcode.com/2019/ OYEs have all the same contact as the national conf (eg. schedule, program, speaker list) so TBH we can use all the same style and structure, just swap in different content. The primary goal here is to use this page to help drive requirements for OYE. That is, create a place where we can compare national events / EOY events against each other, and see where we can improve / plan ahead. The secondary goal here is to create an alternate event front-page, in replacement of ti.to. That said, the MVP of this page will almost certainly include a link to ti.to somewhere. |
@lynncyrin I'm working on the Seattle chapter page! Do you have any photos specifically of the seattle chapter that I could use? |
@deweydell I'll go find a bunch now, and collect them in google drive 👍 |
partially assigning this to myself so that I don't forget about it ^^ |
Create a page for each chapter
Summary
Each chapter will have a page at writespeakcode.com/city.
The page will contain information like who are the chapter organizers and what are the upcoming events (pulled from meetup API).
Acceptance Criteria
Each page will have:
Motivation
Questions
Resources
The text was updated successfully, but these errors were encountered: