Database: co-author (reviewers) per lesson

[Markkos89]

• Design prisma co-author (reviewers) per lesson tables relationships implementation
• Refactor UI on each Lesson Page
• Design new figma for showing co-author (reviewers) on each Lessons like co-authors

[elPiablo]

• Design new figma for showing Reviewers on each Lessons like sub-authors
  'co-author' is more preferrable than 'sub-author'
  I mentioned this in Database: co-author (reviewers) per track #203 so sorry for the repetition 😄

[Markkos89]

• 'co-author' is more preferrable than 'sub-author'

piablo the message it's a bit confusing (because of the quote editor).
You said this: 'co-author' is more preferrable than 'sub-author' ? If it's so, I can replace the spelling.

[briangershon]

This will be a nice feature!

Another common scenario will be also having an original author, and then a new author that rewrites/updates the lesson.

In the case of TierNFT Lesson 5, the original was authored in 2022 and is being rewritten in 2024: #216

An option could be to display this in sort of "chronological changelog" format showing each author and giving a short blurb on author's role. e.g. September 2022 - Person 1 wrote lesson. March 2024 - Person 2 updated lesson.