Skip to content

A few ideas for improving visitor experience #46

Open
@atodorov

Description

@atodorov
  1. We need to document how people can help us (maybe in blog post and also documentation) and link to this page from the home page
  2. We need to document how people can make changes to the website and:
  • send us pull requests with testimonials
  • PR with contributor profiles
  • PR with other changes/blog posts
  1. Recently I've seen a few blog posts from last year which give a negative review of Kiwi TCMS but don't really say what they were missing or what is wrong. Trying to scour the Internet for such posts and then email people doesn't usually work. Also in all of the cases so far these people have done some sort of internal evaluation but never asked us questions or opened an issue on GH to discuss problems. For all of this we need to document that they MUST open an issue if they see something. This needs to go into a separate short paragraph (in the Everyday testing, Test management, etc. area of the website). Visitors should be clearly presented with instructions what to do and how to report feedback.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions