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

Update Communities of Practice: Engineering (Standardize capitalization of "Co-lead") #6137

Closed
3 of 4 tasks
JessicaLucindaCheng opened this issue Jan 21, 2024 · 3 comments · Fixed by #6194
Closed
3 of 4 tasks
Assignees
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue P-Feature: Communities of Practice https://www.hackforla.org/communities-of-practice role: front end Tasks for front end developers size: 0.25pt Can be done in 0.5 to 1.5 hours

Comments

@JessicaLucindaCheng
Copy link
Member

JessicaLucindaCheng commented Jan 21, 2024

Prerequisites

  1. Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our Getting Started page and attend an onboarding session.
  2. You have already read our How to Contribute to Hack for LA Guide.

Overview

We need to standardize the capitalization of "Co-lead" for the Engineering Community of Practice so that it matches the capitalization of "Co-lead" for the other communities of practice and make the page look professional.

Action Items

  • In your IDE, open the _data/internal/communities/engineering.yml file
  • Observe the existing syntax of the front matter block 1 in the file
  • Find the leadership variable. Then, for each person, change the L in "Co-Lead" to be lowercase, so the result is "Co-lead". Thus, change the following for each person

From

    role: Co-Lead

To

    role: Co-lead
  • Verify the changes by viewing the following in your local environment and include before and after screenshots with your pull request: the Engineering section on the Communities of Practice page 2

Resources/Instructions

Footnotes

  1. Info about the front matter block

  2. Communities of Practice page URL: https://www.hackforla.org/communities-of-practice

@JessicaLucindaCheng JessicaLucindaCheng added Feature Missing This label means that the issue needs to be linked to a precise feature label. size: missing role missing Complexity: Missing labels Jan 21, 2024

This comment was marked as resolved.

@JessicaLucindaCheng JessicaLucindaCheng added Complexity: Small Take this type of issues after the successful merge of your second good first issue P-Feature: Communities of Practice https://www.hackforla.org/communities-of-practice role: front end Tasks for front end developers size: 0.25pt Can be done in 0.5 to 1.5 hours Ready for Prioritization and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. size: missing role missing Complexity: Missing labels Jan 21, 2024
@Chrisklangley Chrisklangley self-assigned this Jan 27, 2024
Copy link

Hi @Chrisklangley, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:-
i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?)
ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

@Chrisklangley
Copy link
Contributor

Chrisklangley commented Jan 27, 2024

i. Availability: weekdays 6:30pm -9pm
ii. ETA: 1/29/24 EOD

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue P-Feature: Communities of Practice https://www.hackforla.org/communities-of-practice role: front end Tasks for front end developers size: 0.25pt Can be done in 0.5 to 1.5 hours
Projects
3 participants