Coder Social home page Coder Social logo

sheltertech.org's Introduction

ShelterTech.org Website Test Status

Created with Gatsby with content managed in Prismic

This repository contains the source code to the sheltertech.org website. To get the code running for the first time, please see the Getting Started Guide. For more specific documentation, visit one of the pages below:

Staging website

To view the current state of any new features the staging website, please visit https://staging.sheltertech.org/.

Storybook component library

We use GitHub pages to host a live version of Storybook, our component library. Using GitHub Actions, it is automatically kept in sync with the main branch. It can be found at http://sheltertechsf.github.io/sheltertech.org/storybook-static.

sheltertech.org's People

Contributors

richardxia avatar derekfidler avatar candywang avatar ivanleeswe avatar lgarofalo avatar davidagustin avatar dependabot[bot] avatar jessica-px avatar lexholden avatar giftofgrub avatar twolfe2 avatar zen-gineer avatar maxastuart avatar petehuang avatar

Stargazers

Dylan B Matthews avatar  avatar  avatar Leon Stafford avatar Alexander Turinske avatar

Watchers

James Cloos avatar  avatar  avatar  avatar  avatar Dylan B Matthews avatar

sheltertech.org's Issues

Create React map component to list out ShelterConnect installation sites

Although the design for the new ShelterConnect page is still being finalized, it looks like we are definitely going to have a map component that lists the specific ShelterConnect installation sites, so we can get started on implementing that map component.

See the map in the middle of the ShelterConnect page under the "Designs V2" Figma page: https://www.figma.com/file/kKaWvJvyzhNS9hD21v7Ei5/ShelterTech.org-2020?node-id=186%3A20

The component should be data-driven and expect the list of sites to be passed in as a prop.

If I recall correctly, I think I spoke with @derekfidler a couple weeks ago and said that we might have a third type of marker, so we should build out the initial version of this with that kind of extensibility in mind.

Set up TypeScript compiler with our build system

This should be configured for both the Gatsby build and the Storybook build.

The way we can test that this has been done correctly is to convert the inline <InputField> field component to TypeScript and check that it builds both in Gatsby and Storybook.

Typo in mission statement

"Since 2015, we've equipped one shelter and 7 SROs with free WiFi providing more than 1000 underserved people with access to the Internet. And that's jus the beginning."

Update copy to be more inclusive

There are several places where could update the copy to use more inclusive language.

Home page

  • In the site <title>, the word "underserved" should be replaced with "under-resourced"
  • In the "Get Involved" section, replace the word "empower" with "connect"
  • In the third quote in the block quote component, the word "vulnerable" should be replaced with "[at-risk]". Since it's a quote, this replacement should include the square brackets

Volunteer page

  • In the hero banner, "vulnerable" should be replaced with "at-risk"
  • In the "Let's work together" section, "underserved" should be replaced with "under-resourced"

Donate page

  • The word "underserved" should be replaced with "under-resourced"

Automate, or simplify, event updates

Currently the events and volunteer pages need to be updated manually for every new event that is added and then again after the event's date has passed. This requires a little, but frequent, amount of developer time each week. It would be better to simplify this process so a non-developer can update this page and it automatically sorts events based on upcoming or past.

Publish Storybook site to GitHub Pages

Set up a GitHub Actions workflow that builds and publishes the Storybook site to GitHub Pages. This can be done similar to the staging site builds, which run on every merge to the main branch and push the static HTML files up to AWS S3.

Add Storybook/github pages info and link to readme

The readme should explain that we use GitHub Actions to auto-deploy storybook to GitHub Pages every time we merge to main. It should also provide the url, which is: https://sheltertechsf.github.io/sheltertech.org/storybook-static.

Refactor mobile grid CSS

We handled the grid system in our mobile views in inconsistent ways โ€” sometimes setting padding on the .bleedWrapper and sometimes setting padding on the .gridParent โ€” so it might be a good idea to go through and update them to be more consistent.

Note that in the actual designs, the left and right margins seem to vary between 20px and 40px, so we may not be able to use just a single grid definition for all components. However, we should still be able to improve the consistency across them.

Case insensitive File Reader for CircleCI

Screen Shot 2020-10-21 at 5 07 43 AM

There was a situation in the CI where the file name was a different case than the import and caused the CI to fail. Locally this is not an issue for MacOS as the file reader of the operating system is case insensitive. The file reader is case sensitive in the CI although. Is there any way that CircleCI can be configured to resolve paths the same way? @richardxia

"Replace references to "AskDarcel" app in sheltertech.org with "SF Service Guide"

@fredciaramaglia commented on Tue May 21 2019


@fredciaramaglia commented on Tue May 21 2019

Since the SF Service Guide app links to sheltertech.org in several places, before the release of SF Service Guide we need to replace the many "AskDarcel" references with "SF Service Guide", in the following places:

  1. Programs page - AskDarcel name and graphic
  2. Impact page - AskDarcel name and graphic
  3. Get Involved page
  4. Team page
  5. Several of the Blog articles

This issue is related to Issue 760: "Replace references to "AskDarcel" app in SF Service Guide with "SF Service Guide" and probably should be done at the same time.

Create a style guide

Even if we mostly follow Prettier and Airbnb's style guides, there are a few things that cannot be programmatically enforced, and it would be good for us to explicitly state what our conventions are.

One concrete example of something that we could mention in the style guide is how we use CSS modules and the classnames library. See #153 (comment).

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.