ji-devs / ji-devs/ji-cloud

Community - when tabs are empty

Open
#3,969 0 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

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

Description

This ticket replaces #3022:
In User profiles there are 2 sections:
Creations with subsections JIGs, Resources, Playlists, Courses and
Network with Circles, Followers, Following. Empty subsections will just hide.
If ALL subsections are empty...then we have "Empty states". The following items are what to put in these empty spaces:

Empty states viewing your own profile:

Creations: Fill this space! Visit the Jigzi Studio to start creating (Link to Jigzi Studio from those words)
Network: Fill this space! Browse members & circles to build your network (Link to members or circles from those words)

Empty states viewing other profiles: RANDOMIZE JOKES

Creations:

  • Why did the robot take a dance class?
    Because it wanted to learn to do a JIG!

  • Why was the robot so good at dancing?
    He had a great algo-rhythm

  • Where did the robot keep his Jigzi creations?
    In its JIGabyte of cloud storage.

  • Why was the robot confused?
    Because it couldn’t solve the JIGsaw puzzle.

  • What did the JIG pirate say to the robot?
    A.I. A.I. captain!

  • Why did the robot use Jigzi?
    He wanted to improve his A.I.-Q

Network:

  • How did the robot create his own Jigzi network?
    With WiFi and a little effort. Same as you.

  • How did the robot connect with awesome educators?
    By building a Jigzi network for machine learning.

  • What did the robot plan for alternative education?
    Programming.

  • Why did the robot need a worldwide community of educators?
    He 'app'-reciates connecting with educators who care.

@GaliShapira to add in illustrations for the empty areas, We thought of our JIG creature using a microphone like in stand-up comedy...

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.