codebar / codebar/planner

Members can leave a testimonial

Open
#1,438 9 comments 0 reactions 1 assignee View on GitHub

@matyikriszta is already working on this.

Since Oct 8, 2022.

high-priority
Dominant language
Ruby
Stars
104
Forks
205
Avg merge
1d 5h
Merged PRs (30d)
63

Description

Description of the issue 📄

A member that has attended more than X events and has no testimonial associated with them can leave a testimonial

  • Add controller and related view so that a new member can add a testimonial
    • Add some text to inform members that any testimonial along with their name and profile picture might be used for the promotion of codebar (website, prospectus, etc)
    • Only allow for one testimonial per member
    • Once testimonial is created the page should no longer be available to member (or maybe a read-only version only can be available)
  • Extend testimonial model to have public boolean field
  • Add rake task to update existing testimonials to public
  • Add admin/testimonials#index page
    • List all testimonials, with member name, text, current status and actions columns
    • Enable admins to toggle the status
    • Only available to users with the admin role
  • Update main page testimonials query to only retrieve public testimonials - https://github.com/codebar/planner/blob/master/app/controllers/dashboard_controller.rb#L17

To do 📋

  • Claim this issue (comment below, or assign yourself if you are part of the codebar org)
  • Fork and clone the repository
  • Update the relevant files. Follow the steps to fix section in this issue.
  • Commit your changes as one commit. Use the title of this issue as your commit message
  • Submit a pull request
  • Mention this issue in the PR description by including it's number
  • Have your pull request reviewed & merged by a codebar team member

Contributor guide

Open the contributing guide

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.