dev-launchers / site-projects Goto Github PK

We're expecting three parties to view any project page

1. Visitor, not authenticated (signed in)
2. Authenticated user but NOT part of the team
3. Authenticated user and participating in the project

I think it would make much more sense if we let users who are AT LEAST authenticated to see the upcoming sessions of a specific project.

This is the link the button should take you to:
https://devlaunchers.com/c/sponsorship/

Storybook is a tool for UI development. It makes development faster and easier by isolating components. This allows you to work on one component at a time. You can develop entire UIs without needing to start up a complex dev stack, force certain data into your database, or navigate around your application.

for more info: https://storybook.js.org/

It would be great if we can add this to the existing Session component, there's appointment slots feature in Google Calendar but I'm not sure if it has an API. We can fallback to calendly API if Google Calendar API was complicated or doesn't exist!

As a user not currently associated with the Site Projects project, I see Mohammed listed twice under the Team section.

I did notice that the two Mohammed users have different email addresses.

Getting familiar with typescript by adding types to components we've had before.

Refactor codebase in the component to TypeScript

As a user not currently associated with a project, the sessions that I see as of 16:35 EDT on 11/04/2021 are:

I have not attempted to use any of the "Join" links. Mohammed mentioned I could possibly use this for the meeting on Friday (11/05/2021). I feel like it would be more useful to see future meetings if they exist, and only see past meetings if no future meetings exist (possibly within some arbitrary threshold).

When you hover your mouse over one of the links in the navbar at https://devlaunchers.org/projects you see the following

when it should be requesting https://devlaunchers.org/_next/data/cUoLKwsvAUH0GoX3Rc5Mr/learn.json instead..
I assume it has something to do with configuring the basePath correctly on our end in the next.config.js

When making a request for a collection that has nested relations or a many to many relation like in Interests and SubProjects, strapi doesn't populate it by default. You'll have to customize the population.
eg:
entities = await strapi.services.project.find(ctx.query, ['interests']);

Add a isHidden variable to open role cards in order to make them appear of not according to the IsHidden variable.

right now the project prop doesn't return the profile picture in the team object.

Example: going to the URL https://devlaunchers.com/projects/site-projects?Team would take you directly to the team section of the project.

This would consist of a few tweaks and require a lot of UX research to find the perfect solution to the following problem: how can we allow the large number less experienced developers we have applying to our programs to learn and contribute effectively in a low commitment, easily approachable way (and still be manageable by Dev Launchers). The current thought on how to tackle this is:
An inexperienced developer lands on our Projects page and wants to tackle something to gain experience. They then have one of three choices

1. Apply to one of the big teams as a beginner and hope against the odds that they get accepted (and then put in a ton of work)
2. Browse a list of open "Micro Projects", consisting of 2-3 developers with predefined tasks working toward a small predefined outcome(?), and apply to join one of them
3. Create their own "Micro Project" from one of many "Micro Project Templates", and act as a "Micro Team Lead". Examples include: Tic-Tac-Toe, hangman, a simple landing page, etc (basically something you would create in a school group project)