-
Notifications
You must be signed in to change notification settings - Fork 4
New Student Onboarding
Welcome to the Applications Development Practicum! This checklist is your starting point for setting up your environment and getting access to all team resources. Complete each step in order β if you get stuck, ask your instructor or a team lead on Slack.
To work effectively within the practicum, you must have the following accounts set up.
β οΈ ATTENTION: Starting Spring 2025 you will be required to use your Seattle Colleges email for Notion and Figma access. It is advised to change your Notion email to a personal one after you graduate so that you do not lose access.
| Platform | Purpose & Access Notes |
|---|---|
| GitHub | Primary code hub. You should already have a GitHub account. To request access to project repositories, you must reach out to the TPM or Security Administrator. Be sure to add your name to your GitHub profile so we know who you are! |
| Slack | Day-to-day communication. You should already be on Slack. If you are not, contact your instructor. |
| Figma | UI/UX Design. Used for mockups, prototypes, and user experience flows. |
| Postman | API Testing. Used to test and interact with backend endpoints during development. |
| Notion | Legacy Documentation. Currently serves as a secondary wiki. If you are tasked with doing research, it is advised to make a Notion page so the rest of the team can see your work. You will need to request access for editing permissions from your instructor. |
π Need help with access? Reach out to your instructor on Slack for Notion/Figma permissions, or the TPM/Security Administrator for GitHub repository access.
Install and configure all essential tools needed for development.
| Tool | Purpose | Status |
|---|---|---|
| Git | Version Control System. Must be configured with your GitHub email. | β |
| IDE (VS Code) | Your primary code editor. | β |
| Node.js / npm | Runtime environment for most web projects. | β |
| Other CLI Tools | (e.g., Docker, Python/Pip, depending on project) | β |
Need help with setup? The Git and IDE/Text Editors guide provides step-by-step installation instructions.
These guides cover essential team processes, workflow, and professional conduct.
-
Practicum Workflow: Learn how the team runs two-week sprints, daily standups, and planning meetings.
- β‘οΈ Agile Workflow page
-
GitHub Workflow: Follow the 7-step process: Issue β Branch β Code β Commit β Push β PR β Review.
- β‘οΈ GitHub Workflow guide
-
Code of Conduct: Understand expectations around communication, professionalism, and collaboration.
- β‘οΈ Code of Conduct section
| Task | Description | Status |
|---|---|---|
| Introduce Yourself | Post a short intro in the #general Slack channel. | β |
| Review Team Directory | Familiarize yourself with your PMs and Leads. | β |
| Clone Project Repo | Get the code for your assigned project onto your machine. | β |
| Attend Monday Meeting | Join the first team meeting for updates and Sprint Planning. | β |
Home β’ New Student Onboarding β’ Guides β’ Projects β’ Code of Conduct β’ FAQ
Last updated: 12/7/2025