Skip to content

Commit 87a7483

Browse files
committed
Merge branch 'main' into develop
2 parents 51746d8 + dea51b2 commit 87a7483

File tree

13 files changed

+52
-61
lines changed

13 files changed

+52
-61
lines changed

.github/ISSUE_TEMPLATE/blank-issue.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,8 @@
22
name: Blank Issue
33
about: Consistent formatting make Issues concise and easy to navigate
44
title: ''
5-
labels: 'feature: Missing, milestone: missing, role: missing, size: missing'
5+
labels: 'complexity: missing, feature: missing, milestone: missing, role: missing,
6+
size: missing'
67
assignees: ''
78

89
---

.github/ISSUE_TEMPLATE/dev-onboarding.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,4 +26,4 @@ Tasks
2626

2727
### Resources
2828

29-
- [Resources](https://hackforla.github.io/CivicTechJobs/resources/)
29+
- [Resources](https://hackforla.github.io/CivicTechJobs/resources/)

.github/ISSUE_TEMPLATE/post-an-open-role.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
name: Post an open role
33
about: Recruit volunteers for specific open roles template
44
title: 'CTJ: Open Role for: [Replace with NAME OF ROLE]'
5-
labels: 'feature: recruiting'
5+
labels: ''
66
assignees: ''
77

88
---

.github/workflows/deploy-stage.yml

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,9 @@ on:
33
push:
44
branches:
55
- main
6+
paths-ignore:
7+
- "mkdocs/**"
8+
- "dev/**"
69
workflow_dispatch:
710
jobs:
811
deploy:

README.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,7 @@ The tool will match volunteers by availability, role, and program area. Future i
1010

1111
Civic Tech technology practitioners are a diverse and interdisciplinary group of people. Their backgrounds are in technology, design and product. They work inside governments, at nongovernmental agencies, and within for-profit corporations. Some of them do this full time as a career. Some do this to develop their personal skills in collaboration. Others do this in their spare time, as a hobby.
1212

13-
[One Sheet](https://github.com/hackforla/product-management/blob/a8cbef76c3d8b79b181ee8bd19548cc6ce5ce487/project-one-sheets/CTJ_%20Civic%20Tech%20Jobs%20One%20Sheet%20-%202023.pdf)
14-
13+
[CTJ_Civic Tech Jobs One Sheet - 2025.pdf](https://github.com/user-attachments/files/19147691/CTJ_.Civic.Tech.Jobs.One.Sheet.-.2025.pdf)
1514

1615
## Technology used
1716

mkdocs/docs/developer/backend.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
# Backend Architecture
22

3+
test
4+
35
_<p style="text-align: center;">Overall project structure</p>_
46

57
```yml

mkdocs/docs/index.md

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,40 +1,42 @@
11
# Welcome to the Civictechjobs.org Wiki!
22

3+
Here, you'll find all the essential information about our project. This wiki is designed to be a helpful resource for both new and existing team members.
4+
35
## Project Definition
46

5-
CivicTechJobs will be a site to find open volunteer positions for projects at hackforla.
7+
CivicTechJobs will be a site to find open volunteer positions for projects at Hack for LA.
68

79
## Introduction To The Project
810

911
### What is Civictechjobs.org?
1012

11-
CivicTechJobs will be a platform to help prospective volunteers find interdisciplinary projects that will be useful for their career development while contributing to positive civic impact, and also a CMS (Content Mgmt System) for Hack for LA projects to be able to list their open roles.
13+
Civic Tech Jobs is a platform designed to connect prospective Hack for LA volunteers with interdisciplinary projects that align with their career goals while driving positive civic impact. The custom-built CMS enables this by allowing projects to list required skills and then matching volunteers based on their availability, skills, and program area.
1214

1315
### Why do it?
1416

15-
To match the right volunteers with the right projects at hackforla.
17+
CTJ will tackle key challenges in project recruitment and organizational sustainability, with future development focused on connecting volunteers to opportunities that align with paid job postings.
1618

1719
### Hasn't it been done already?
1820

19-
Yes, through CoP GitHub pages. However, the process is cumbersome and involves multiple steps to match the candidate with the right role.
21+
Yes, there are recruitment issues on project boards. However, the process is cumbersome and involves multiple steps to match candidates with the right roles.
2022

2123
Read more about what lead up to us developing this project, at our [History](History) page.
2224

2325
### So how is this different?
2426

25-
We would like to streamline the process so that Product Managers can post the open oppotunities within their team efficiently, but most importantly a volunteer is able to find the right match with a project based on their skills, and aspirations.
27+
We aim to streamline the process so that Product Managers can efficiently post open opportunities within their team. Most importantly, we want to ensure that volunteers can easily find the right match with a project based on their skills and aspirations.
2628

2729
## Guiding Objectives
2830

2931
### What are our guiding objectives?
3032

31-
1. Provide product managers ability to post, edit, or close open positions on an easy to use instinctive site (CMS)
32-
2. Assist potential volunteers to self-filter for roles that matches their availability
33+
1. Enable product managers ability to post, edit, or close open positions on an easy to use instinctive site (CMS).
34+
2. Assist potential volunteers to self-filter roles based on their availability.
3335
3. Provide potential volunteers list of open roles with different projects that matches their skills, and interest.
3436

3537
## Project One Sheet
3638

37-
You can access our [project one sheet here](https://docs.google.com/document/d/1bfxY8YlyCjzCL3oP0rpa77uEY4vuymDYZY_xWEgXiGs/edit?usp=sharing).
39+
Access our project one sheet [CTJ_ Civic Tech Jobs One Sheet - 2025.pdf](https://github.com/user-attachments/files/19147708/CTJ_.Civic.Tech.Jobs.One.Sheet.-.2025.pdf)
3840

3941
## Key Resources
4042

mkdocs/docs/joining-the-team/intro.md

Lines changed: 4 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -1,22 +1,11 @@
1-
**_DRAFT NOT YET FILLED OUT_**
2-
3-
### Introduction
4-
5-
Welcome to the Civic Tech Jobs team! This guide will help get you up to speed on what you need to know to get started as a project team member.
6-
7-
---
1+
Welcome to the Civic Tech Jobs team! This guide will help you get up to speed with everything you need to know to get started as a project team member.
82

93
### Let's go!
104

11-
If you have not read the [Guide for New Volunteers](https://www.hackforla.org/getting-started), please do so.
12-
13-
1. Check the [Community of Practice -> Open Roles Board](https://github.com/hackforla/communities-of-practice) for current open roles in the Civic Tech Jobs project.
5+
1. Before proceeding, please confirm that you have reviewed and completed the steps outlined in Hack for LA’s [Guide for New Volunteers](https://www.hackforla.org/getting-started)
146
2. Read [Introduction to the Project](https://hackforla.github.io/CivicTechJobs/) if you haven't already read it.
15-
3. If interested in joining the team, complete this form [Team Roster Onboarding Form](https://docs.google.com/forms/d/e/1FAIpQLSfv-VTLseKixhzbPvY_hBHW30CaokUh4FOmst-4ZEM639EinQ/viewform).
16-
4. Join the [Civic Tech Jobs](https://hackforla.slack.com/archives/C02509WHFQQ) Slack channel and introduce yourself and mention the role you are interested in. Our PM's will help you get onboarded with the following steps.
17-
1. Accept your Google Drive invite to access the [shared folder](https://drive.google.com/drive/u/0/folders/0AMdnUkSXicNCUk9PVA).
18-
1. Review the [Glossary](https://hackforla.github.io/CivicTechJobs/misc/glossary/).
19-
1. Attend our monthly all team meeting on the third Tuesday at 5pm PST. You can find the link pinned in our slack channel.
7+
3. Check the [Community of Practice -> Open Roles](https://github.com/orgs/hackforla/projects/67/views/8) for current open roles in the Civic Tech Jobs project. Please follow the steps outlined in the respective open role issue.
8+
4. Attend our monthly all team meeting on the third Tuesday at 5pm PST. You can find the link pinned in our [Civic Tech Jobs slack channel](https://hackforla.slack.com/archives/C02509WHFQQ).
209

2110
---
2211

@@ -30,10 +19,6 @@ Click the link that applies to you to find a sequence of immediate action steps:
3019

3120
[UI/UX Researcher](UI-UX-Researcher)
3221

33-
[Data Scientist](Data-Scientist)
34-
35-
[Content Writer](Content-Writer)
36-
3722
[Product Manager/Owner](Product-Manager-and-Owner)
3823

3924
[Other Volunteer](Other-Volunteer)

mkdocs/docs/joining-the-team/product-manager.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,14 +4,14 @@
44

55
Each of the resources below can be considered a work-in-progress. These resources will evolve and adapt as the team and team needs change. Feel free to open an issue with a link to whichever resource needs improvement and a description of the suggested change.
66

7-
1. Learn how we setup our [GitHub Kanban boards](https://docs.google.com/document/d/11Fe7mNdmPBP5bD_yLJ1C0_I1TmoK47AuHHrdhdDyWCs/edit?usp=sharing) and please comment if there is anything in the document that is unclear.
7+
1. Learn how we setup our [GitHub Kanban boards](https://docs.google.com/document/d/1CuRX6hhWzs8ydVCnl6OrGZ4LeVSk9X_pIzoKchAqFcU/edit?tab=t.0#heading=h.xwpqk588zdpy) and please comment if there is anything in the document that is unclear.
88

99
2. This [Software Development Lifecycle Diagram](https://drive.google.com/file/d/1emxhYv9N6KuCVrG-gnqkqHdGnjhm_Qvb/view?usp=sharing) is a sample of what the process is generally like at Hack for LA and each project is different.
1010

11-
3. Review our [OKRS](INSERT-PROJECT-OKRS-SPREADSHEET-LINK).
11+
3. Communicate with other product team members and leadership to discuss project priorities and strategic direction.
1212

13-
4. Communicate with other product team members and leadership to discuss project priorities and strategic direction.
13+
4. Review the [Project Board](https://github.com/orgs/hackforla/projects/37/views/4) and the [Product Management issues available on that board](https://github.com/orgs/hackforla/projects/37/views/7) to identify an actionable backlog item.
1414

15-
5. Review the [Project Board](https://github.com/hackforla/[INSERT-REPO-NAME]/projects/1) and the [Product Management issues available on that board](https://hackforla/[INSERT-REPO-NAME]/projects/1?card_filter_query=label%3A%22role%3A+product%2Fproject+mgmt%22) to identify an actionable backlog item.
15+
5. Review Hack for LA [Product Management Templates](https://github.com/hackforla/product-management/wiki#started).
1616

17-
6. Review Hack for LA [Product Management Templates](https://github.com/hackforla/product-managment/projects/2).
17+
6. Review our [OKRS](INSERT-PROJECT-OKRS-SPREADSHEET-LINK).

mkdocs/docs/joining-the-team/uiux-designer.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,10 +4,7 @@
44

55
1. Review the UI/UX issues on the [Project Management Board](https://github.com/hackforla/CivicTechJobs/projects/1?card_filter_query=label%3A%22role%3A+ui%2Fux%22) and identify an actionable backlog item.
66

7-
1. Communicate with PM your interest in being assigned a task.
8-
9-
1. Ask your lead to invite you to the [Civic Tech Jobs figma workspace](https://www.figma.com/files/team/1040075117587297658/Civic-Tech-Jobs?fuid=775836858007206739)
10-
- Leads should send invite to team members AFTER they have been added to the Google Drive and put their information into the team roster.
7+
1. Communicate with the UI/UX Design Team Lead about your interest in being assigned a task.
118

129
## Additional Reading
1310

0 commit comments

Comments
 (0)