-
-
Notifications
You must be signed in to change notification settings - Fork 843
Open
Labels
Complexity: SmallTake this type of issues after the successful merge of your second good first issueTake this type of issues after the successful merge of your second good first issueP-Feature: Communities of Practicehttps://www.hackforla.org/communities-of-practicehttps://www.hackforla.org/communities-of-practiceStatus: Help WantedInternal assistance is required to make progressInternal assistance is required to make progressrole: back end/devOpsTasks for back-end developersTasks for back-end developersrole: front endTasks for front end developersTasks for front end developerssize: 0.25ptCan be done in 0.5 to 1.5 hoursCan be done in 0.5 to 1.5 hourstime sensitiveNeeds to be worked on by a particular timeframeNeeds to be worked on by a particular timeframe
Milestone
Description
Prerequisites
- 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.
- You have already read our How to Contribute to Hack for LA Guide.
Overview
We need to keep project information up to date so that visitors to the website can find accurate information.
Action Items
- In your IDE, open the
_data/internal/communities/ops.ymlfile. 1 - Observe the existing syntax of the front matter block 2 in the file.
- Find the
namevariable and change the following:
From:To:name: Opsname: DevOps - Open
assets/js/communities-of-practice.js3 and find
if (communityName === "Project/Product Management") {
projectName = "Product Management";
} else if (communityName === "Ui/Ux") {
projectName = "UI/UX";
} else {
projectName = communityName;
}
- After
projectName = "UI/UX";
add the following
} else if (communityName === "Devops") {
projectName = "DevOps";
- Verify the name change and meeting times are showing up by viewing the following in your local environment with Docker, and include 'before' and 'after' screenshots with your pull request:
- Communities of Practice page 4
Resources/Instructions
Footnotes
-
Link to the community of practice file in HfLA Website repo: https://github.com/hackforla/website/blob/gh-pages/_data/internal/communities/ops.yml ↩
-
Link to the communities-of-practice.js file in HfLA Website repo: https://github.com/hackforla/website/blob/gh-pages/assets/js/communities-of-practice.js ↩
-
Communities of Practice page URL: https://www.hackforla.org/communities-of-practice ↩
Metadata
Metadata
Assignees
Labels
Complexity: SmallTake this type of issues after the successful merge of your second good first issueTake this type of issues after the successful merge of your second good first issueP-Feature: Communities of Practicehttps://www.hackforla.org/communities-of-practicehttps://www.hackforla.org/communities-of-practiceStatus: Help WantedInternal assistance is required to make progressInternal assistance is required to make progressrole: back end/devOpsTasks for back-end developersTasks for back-end developersrole: front endTasks for front end developersTasks for front end developerssize: 0.25ptCan be done in 0.5 to 1.5 hoursCan be done in 0.5 to 1.5 hourstime sensitiveNeeds to be worked on by a particular timeframeNeeds to be worked on by a particular timeframe
Type
Projects
Status
Questions / In Review