Skip to content

Add a mean to review and comment blog posts #77

Open
Open
Add a mean to review and comment blog posts#77
Labels
enhancementNew feature or request

Description

@ctmbl
ctmbl
opened on Mar 27, 2023

Currently blocked by #12

Problem

There is no mean, at the time, to review blog posts, for example to fix typos, add/ask for additional information or warn about dead links.
We should also be able to report blog posts.

Some Solutions

Here is a list (from the simplest to the most complex ones) of solutions I imagined:

  • a simple comment section below the post (this is for another issue but the author could be notified)
  • a mean to send private messages to/email the author, with or without some embedding to highlight/show the diff one would like
  • a more complex workflow where, after submitting a post an author, the post is in Review state (analogous to Allow article to be set to private #75) and the author must wait for, designated or not, reviewers approval (same as GitHub PRs or Root-Me solution submitting)
  • some other I didn't think of ??

Activity

  1. ctmbl
    added
    enhancementNew feature or request
    on Mar 27, 2023
  2. ctmbl
    added this to iScsc websiteon Mar 27, 2023
  3. github-project-automation
    moved this to Backlog in iScsc websiteon Mar 27, 2023

  4. dolphinau commented on Mar 27, 2023

    @dolphinau
    dolphinau
    on Mar 27, 2023
    Contributor

    This new feature is, from my pov, quite important, and interesting to add.
    Regarding the solutions you proposed:

    • I understand the idea of a Review state, but I think it's too much work for the maintainers of the blog, and will probably slow the publication process. Nevertheless, we talked about this review process for bloggers who wouldn't have a "iScsc member" or "Verified user" badge, and I totally agree for that!
    • The private message way isn't the best solution for me because I don't think we should make a difference between normal comments (like question, greetings, extra information from other users...) and review comments (typos...). There could be a Type of comment field which would change the color, visibility and priority of comments, but otherwise they should be handled the same way. I don't think making them private is a good solution.
    • The last (first 🙃) solution is the best for me. I think it's time to implement a comment feature. You sorted this solution as the simplest but it's the most difficult I think 😉

    Here is a none exhaustive TODO if we choose this solution:

    • Update the database to add "comments" backend
    • Add API endpoint to Create/Read/Update/Delete (CRUD) comments backend
    • Update frontend to add comments bellow the blog posts frontend

    Fell free to raise other issues to tackle!

  5. ctmbl commented on Mar 27, 2023

    @ctmbl
    ctmbl
    on Mar 27, 2023
    ContributorAuthor

    @atxr
    Thanks for the answer!

    I'd like comments section so I'm happy you prefer it too.
    However we should first make the blog posts editable don't you think?

  6. dolphinau commented on Mar 28, 2023

    @dolphinau
    dolphinau
    on Mar 28, 2023
    Contributor

    Yes of course!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions