sfbrigade / codeforsanfrancisco.org Goto Github PK

Crawl the old blog index (brigadehub.codeforsanfrancisco.org/blog) and create redirects to their new location so that existing links continue to work.

My photo appears over Greg's name on the website. https://codeforsanfrancisco.org/about/team/

https://codeforsanfrancisco.org/about/team/

Update the organizing team page to streamline the content. For example, there's a link to "core-team" but with no direction on when to use that email.

Also, Reid needs an avatar.

https://codeforsanfrancisco.org/about/leadership-council/

The "Leadership Council" page is both static and out of date. Should be dynamic, automatically maintained, or simple a link to the public gdrive folder

The work that the project delivery team did on the lifecycle has stayed trapped in a presentation: https://drive.google.com/file/d/0B3CHxhx2-3cOazNyRldqMGtxYjg/view?usp=sharing

While we reference it in the status of each project, we don't explain what it means or what the criteria are for each in an easy to discover way.

I think we can do even more here to make the process for submitting and vetting ideas prominent, simple and criteria driven, but we can save that for another issue.

Some inspiration:
https://codeforphilly.org/pages/project_guidelines
https://docs.google.com/presentation/d/1d7zazkSMwshShctmlLavJHFl9EQVUxavuwTaaudGEZ8/edit#slide=id.g24c386e236_0_13

• Display the status to the project index /projects
• Include projects on index that are non-active (currently only active are shown)
• Create a page describing the statuses and their criteria and any additional information that may be helpful (we can iterate with user testing)
• Provide tooltips or reference links from the projects and project index to make the lifecycle more prominent (also consider using visual cues to show the status as part of a process?)

Transfer roles over from https://github.com/sfbrigade/resources/blob/master/Core%20Team/Roles.md to https://github.com/sfbrigade/codeforsanfrancisco.org/blob/master/_data/leadership-councils.yml

Use https://www.sheltertech.org/volunteer for extra ideas.

Would like to support /projects/?search=skills_needed:nonprofit so that we can link to it from other pages. This way if we are on a project page and click one of the tags, we can take them back to the search with the tag already filled in.

Deliverables

• Visiting /projects/?search=skills_needed:nonprofit adds query parameter to text input
• Visiting /projects/?search=skills_needed:nonprofit immediately triggers search with query

Would be good to get some notes on thoughts / desires for the website. However this isn't super critical as there are a lot of self-evident areas of improvement on the website today we have on our roadmap to tackle.

Update the "team" page here: https://codeforsanfrancisco.org/about/team/

Consider options for creating a projects page (hosted at /projects).

Possibilities:

• Jekyll pages
• Jekyll data
• Dynamic pulling from Github (maybe using civic.json?)
• Others?

Eventually we'll want to dynamically populate this based on the work that the UX research group is doing on the project match making to avoid duplication of information (as their app will also require populating similar information to what we will want to display).

Change "Past Events" to "Events" in global footer. The link is to all past and upcoming events.

A constant onboarding issue is getting people to join slack. I agree the rsvp should be the top CTA, but it should have a twin CTA right next to it for people sitting in CityHall conf room at 6:15 on Wed that takes them to step by step instructions for getting on slack and finding and joining project channels. Once there, projects can take the ball and provide further onboarding instructions.

The date of the next event is listed as 12-12, but today is 12-17. Does not appear to be an issue with the event markdown files.

The About page has a section displaying "500 Internal Server Error"

https://codeforsanfrancisco.org/about/

I'm noticing the headings on a lot of pages are inconsistent. We should go through and clean these up to be more consistent.

• All layout headings should be consistent
• All standalone page headings should be consistent
• Paragraphs of free text should be properly enclosed
• Superfluous markup and classes should be removed

Be creative!

This will help make it easier for people to edit projects. Since all changes go through Github moderation we should not worry about permissions and access.

There are 2 rows of Sponsors that are blank and a few sentences above. We can probably drop the sentences and just have a CTA button to get people to sponsor.

Run accessibility checks against the site and determine if there are any issues to be fixed.

• Either fix or create issues for issues to be fixed.
• Integrate into a CI build (consider previous accessibility build as reference https://github.com/sfbrigade/sfbrigade.github.io/blob/master/.travis.yml)

See breadcrumbs here: https://codeforsanfrancisco.org/events/2018-12-05-weekly-civic-hack-night/
and here: https://codeforsanfrancisco.org/projects/hours-equals-price-project/

Lets make em a bit more consistent.

The current organization is a little messy, I'd like to continue adding more links to resources, which may involve a drop menu or slightly different organization.

Create a resources page with links and descriptions of resources for brigade projects.

Examples:

• https://chihacknight.org/data-resources.html
• https://www.openoakland.org/resources/

@jszwedko - this link needs to be changed, but if we change this here, will it update past events too?

Some projects have been completed or are inactive but have progressed enough that having someone take them over could be useful.

Lets add a new archived property or reuse / change the active field to be a multi-state field. I honestly don't think the current project_status is that beneficial and may prove an appropriate place for the new state property.

Once we've done that we can start sorting on status.

This would allow us to quickly add filtering capabilities to the search.

• Clicking on a skill or interest should add needed_skills:[skill] to search
• Clicking on a skill or interest should immediately trigger a search

We use meetup.com to organize brigade events, but would also like to have event pages on codeforsanfrancisco.org. Consider strategies for synchronizing the event information (either from or to meetup.com) with the site.

Some considerations:

• Each hack night will have an agenda document
• Some events will have their own picture
• Jekyll event metadata is structured

I've created a sample event for use as reference.

Update reviewer team