ji-devs / ji-devs/ji-cloud

Community - Phase 2 - Homepage of community

Open
#3,855 1 comment 0 reactions 3 assignees View on GitHub

@ChaykeeMor is already working on this.

Since May 17, 2023.

Dominant language
Rust
Stars
14
Forks
18
PR merge metrics
No merged PRs in 30d

Description

@ChaykeeMor can you see the texts for phase 2 of the community?
https://zpl.io/9qvjjoB

@MendyBerger Here is the list of changes for the homepage of the community:
There is a design of 1024, and 1280, I will add mobile.

Top header of all community pages:
Add icon for Schools. (I will add the design tomorrow.
Pls make sure to change all the other icons to our icons.
Screen Shot 2023-05-17 at 17 32 23

Video:
We will add a video, make it played automatically muted.

List of members:

  1. Change the list of new members to top creators (exclude the Jigzi team).
  2. Add to members in general 2 types of badges (JI and Master teacher: see the design in the components page). For this particular list only master, no JI. @corinnewo Let's discuss the back office how to give a teacher this badge and how to notify the teacher.
  3. Add to the table the names of columns.
  4. Add to the table countries, flags, no. of creations (sort by it)
  5. Add 25 teachers that we can scroll. and a button to see all members.
  6. Make the teacher image + name area link to the profile page, there are hover states for both.

Circles:

  1. Add in the circles names more space for up to 3 lines.
  2. Add a button See all circles

ProDev courses:

  1. Add the component from the JIG card component section.
    https://zpl.io/5EM0E78
    See the Kebab menu for the entire community section.
    The ProDev has a white footer, and instead of ages showing duration.
  2. Add a button See all.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.