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

Create Layout for New Toolkit Page #3959

Closed
1 of 6 tasks
jdingeman opened this issue Feb 9, 2023 · 19 comments
Closed
1 of 6 tasks

Create Layout for New Toolkit Page #3959

jdingeman opened this issue Feb 9, 2023 · 19 comments
Assignees
Labels
Complexity: Large Feature: Feature Branch Requires Branching off a Feature Branch instead of gh-pages Ignore: Duplicate Issue or pull request is a duplicate P-Feature: Toolkit https://www.hackforla.org/toolkit/ ready for dev lead Issues that tech leads or merge team members need to follow up on role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 2pt Can be done in 7-12 hours time sensitive Needs to be worked on by a particular timeframe

Comments

@jdingeman
Copy link
Member

jdingeman commented Feb 9, 2023

Dependency

Overview

We will be implementing a new Toolkit page to replace the one that is currently on the published website. To do so, you will need to work off of the feature-homepage-launch branch. See How to work off of a feature branch

Action Items

  • See Figma design in the red box with an issue 3626 label
    • You will be creating the layout as shown in screenshot below
  • Create a new file in website/pages called our-toolkit.html and implement the design
  • You can use the current toolkit as a reference for the new page.
  • For the dropdown filter, try to use the reusable component made in Fix the dropdown menu design for projects page #3744 when that issue is merged
    • If you are not able to implement it, please provide a write up in the comments with the blockers and what might be preventing it from being used
    • If you are able to implement it, please provide a write up in the comments how you implemented this
    • Your write up will be used later in the Wiki
Proposed Figma design

image

Resources/Instructions

@jdingeman jdingeman added role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers Complexity: Large P-Feature: Toolkit https://www.hackforla.org/toolkit/ Ready for Prioritization size: 2pt Can be done in 7-12 hours ready for product labels Feb 9, 2023
@ExperimentsInHonesty ExperimentsInHonesty added this to the 05. Know HFLA milestone Feb 12, 2023
@ExperimentsInHonesty ExperimentsInHonesty added time sensitive Needs to be worked on by a particular timeframe and removed Ready for Prioritization ready for product labels Feb 12, 2023
@plang-psm plang-psm self-assigned this Feb 18, 2023
@github-actions

This comment was marked as outdated.

@plang-psm

This comment was marked as outdated.

@github-actions github-actions bot added the Status: Updated No blockers and update is ready for review label Feb 24, 2023
@plang-psm

This comment was marked as outdated.

@plang-psm plang-psm removed their assignment Feb 28, 2023
@vanessavun vanessavun self-assigned this Feb 28, 2023
@github-actions

This comment was marked as outdated.

@vanessavun

This comment was marked as outdated.

@jdingeman

This comment was marked as outdated.

@vanessavun vanessavun removed their assignment Mar 3, 2023
@vanessavun

This comment was marked as outdated.

@vanessavun vanessavun self-assigned this Mar 9, 2023
@github-actions

This comment was marked as outdated.

@vanessavun

This comment was marked as outdated.

@vanessavun

This comment was marked as outdated.

@vanessavun vanessavun removed their assignment Mar 20, 2023
@vanessavun

This comment was marked as outdated.

@ExperimentsInHonesty ExperimentsInHonesty removed the Status: Updated No blockers and update is ready for review label Mar 21, 2023
@christinaor christinaor self-assigned this Mar 22, 2023
@github-actions

This comment was marked as outdated.

@christinaor

This comment was marked as outdated.

@christinaor

This comment was marked as outdated.

@christinaor

This comment was marked as outdated.

@jdingeman jdingeman added the Dependency An issue is blocking the completion or starting of another issue label Apr 4, 2023
@jdingeman

This comment was marked as outdated.

@JessicaLucindaCheng

This comment was marked as resolved.

@jdingeman jdingeman added ready for dev lead Issues that tech leads or merge team members need to follow up on Ready for Prioritization and removed Dependency An issue is blocking the completion or starting of another issue ready for dev lead Issues that tech leads or merge team members need to follow up on Ready for Prioritization labels Apr 11, 2023
@jdingeman jdingeman added the Feature: Feature Branch Requires Branching off a Feature Branch instead of gh-pages label Apr 21, 2023
@jdingeman jdingeman closed this as not planned Won't fix, can't repro, duplicate, stale Apr 25, 2023
@jdingeman jdingeman self-assigned this Apr 25, 2023
@jdingeman jdingeman added the Ignore: Duplicate Issue or pull request is a duplicate label Apr 25, 2023
@github-actions

This comment was marked as outdated.

@jdingeman
Copy link
Member Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Large Feature: Feature Branch Requires Branching off a Feature Branch instead of gh-pages Ignore: Duplicate Issue or pull request is a duplicate P-Feature: Toolkit https://www.hackforla.org/toolkit/ ready for dev lead Issues that tech leads or merge team members need to follow up on role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 2pt Can be done in 7-12 hours time sensitive Needs to be worked on by a particular timeframe
Projects
Development

No branches or pull requests

6 participants