Home

Hello hello!

This Wiki is an overview of:

• different tools the RED team uses
• how we work together - our workflow
• where to find different assets

This Wiki page also contains the "Onboarding Checklist" for any new RED team member.

Access to demo environment

Note: the demo environment might be reset at any time; assume that any data in it might get lost at any time.

Admin panel

• https://admin.demo.connect.redi-school.org
• User/password: [email protected] / [email protected]

Frontend

Connect

• https://app.demo.connect.redi-school.org
• Create your own user, or use one of these pre-created users:
• Mentor user/pwd: [email protected] / [email protected]
• Mentee user/pwd: [email protected] / [email protected]
• After creating your own user, approve yourself in the admin panel (log in > click Edit button for your profile > click Approve)

Talent Pool

• https://app.demo.talent-pool.redi-school.org

Backend server

• https://api.demo.connect.redi-school.org/explorer

Designer Workflow

• What product does a design task belong to: Design tasks are listed in two project boards on GitHub (TP Board and CON Board), marked with UX/UI Design labels. In Design tabs contain tickets that are ready to be taken into work. There are cases where a designer might work on a common task for both of the products.
• Track & define a design task: We use GitHub issues (think of an issue like a “ticket”). Issues are created by a Product Owner, designer, or developer and refined/scoped/specced taking input from anyone on the RED team.
• When is a design task done? The link to the finished design should be added to the ticket. The ticket should be moved to Ready for Execution tab on the board after the designer is done with the task and the work has been reviewed by the Product Owner & Design Team (Ligia and Rita, alongside the other design team volunteers).

Working on designs:

1. Create a File under Work in Progress project in Figma here
   • File naming convention: (IssueNumber)(Platform)Initiative_Name.
2. You can find the Foundational Designs (Production Screens) in the Product Design Flows file.
3. Copy the screens you need for the screen and work inside of your own file.
4. Make sure you are using the ReDI Design System, which is a work in progress in the following files: Common Library, ReDI Connect DS and ReDI Talent Pool DS.
5. How to track task stage/status? When you start working on the ticket, please assign it to yourself. Once the design work is finished, please add the Figma link to the ticket.
6. Get a design task reviewed? Drag the ticket to the QA by DevLead, DesignLead & PO column on the board, and tag the reviewers.
7. Hand over completed work to the developer: After the work has been reviewed by the Product Owner & Design Lead, the ticket should be moved to the Ready for Execution tab on the board.
8. Keep Figma up to date: Move your designs to Product Design Flows file, in order to make sure we always have the designs up to date.

💡 Tips

• Always Document your work: leave comments and summaries in the page documenting what was changed and why it was changed.
• Blocked on a task? Use bi-weekly Design Happy Hour, ping the Product Owner, Design Lead, or your design colleagues in Slack.

Onboarding checklist

1. Familiarize yourself with all the links in the sidebar to the right 👉

• The CON and TP Kanban boards track all ongoing work. Every item is called an issue. As work progresses on an issue, it gets moved through the columns, from left to right.
• Miro is the place where we store various visual assets (user story maps, personas, user testing interviews, retrospectives, etc.).

2. Make sure you received invites from @ericbolikowski to all the tools: Github, Miro, Figma, Google Drive. If you're a developer, you also need to get some environment variables, also from @ericbolikowski.
3. Play around in the ReDI Connect demo environment:

Check the “Access to demo environment” part above ☝️ It offers details on how you can access the ReDI Connect demo environment. This is the place to go crazy! Create however many users you like, try whatever interactions… a good way to get a feel for the two personas ReDI Connect addresses: mentors and mentees.

A typical recipe: sign up as mentor and mentee. Log into admin to approve both users. Play around creating profiles for both. Have your mentee apply to your mentor. Then have the mentor log some mentoring sessions. Finally, have the mentor or mentee report a problem.

It’s relatively straightforward to do using two tricks:

• Your main browser window + incognito window
• To get around the “only one user per email address” restriction, sign up as [email protected], [email protected], [email protected] etc. If you’ve not heard of this trick: all the emails will still make it to your inbox.

4. If you're a developer, pick a ticket (ask for one or self-assign) and schedule a pair coding session with another team member to do it together. The point is to familiarize yourself with how we do work in the codebase. Preferably pair up with another volunteer, otherwise with @ericbolikowski or @helloanil