Skip to content
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

Creating "What We Do" #651

Open
1 task done
wwwwwlwwwww opened this issue Sep 15, 2022 · 0 comments
Open
1 task done

Creating "What We Do" #651

wwwwwlwwwww opened this issue Sep 15, 2022 · 0 comments
Labels
enhancement New feature or request triage An issue needs further analysis by a team member

Comments

@wwwwwlwwwww
Copy link
Collaborator

Description

Notes:

We would like to build out a section of the website that will explain what we do and will be titled "What We Do". This will have four separate pages each devoted to one of four categories of DA's work: Powering Aid Supply Chains, Connecting Communities, Empowering Humanitarians, and Responding to Crises. This issue concerns the creation of the Powering Aid Supply Chains page; we have content ready for this one, and coding this one up should make the other ones extremely easy to create once the content is written.

The activities (i.e. things we do) are found in content/blocks/activities. Activities have a field called "category". For this page, we want to include only the activities for which the category field = "Powering Aid Supply Chains". There are three of them:

  • content/blocks/activities/in-kind-donations.md
  • content/blocks/activities/hubs-regular-routes.md
  • content/blocks/activities/ad-hoc-shipping.md

Right now, all four of the What We Do pages will have three activities on them. Eventually, the numbers might not work out so cleanly.

For now, we want to present each activity as a card. The parameters of the generalized card template match up with the fields from each activity as such:

  • Title = title
  • Photo = headerPhoto.headerPhotoFields.asset
    • headerPhoto.headerPhotoFields.altText has alt text for the image for the purposes of accessibility; I'm not sure about best practices for how to include this, but it should be included to make sure our site is accessible.
  • Subtitle = desc
  • Body Text = a few consecutive fields
    • "The Problem It Solves" (header) + challenge
    • "How It Works" (header) + explanation
    • "The Benefits" (header) + benefits

I'm not sure if, given the data, it'll make more sense for the cards to appear three across on the screen (with each one's width being 1/3 of the page) or three down (with each one's width covering the whole page). @jtfairbank Not sure if you have thoughts on this.

Front end feature screenshots

This is the data in our CMS for one of the activities:
image

Code of Conduct

  • I agree to follow this project's Code of Conduct
@wwwwwlwwwww wwwwwlwwwww added enhancement New feature or request triage An issue needs further analysis by a team member labels Sep 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request triage An issue needs further analysis by a team member
Projects
None yet
Development

No branches or pull requests

1 participant