json-schema-org / json-schema-org/website
[📝 Docs]: Discussion on Feedback Form Usage and Increasing Conversion
Open
Nobody has claimed this yet.
📝 Documentation
agenda
GSoD
Status: Available
Status: Do not close
- Dominant language
- HTML
- Stars
- 169
- Forks
- 484
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 6
Description
What Docs changes are you proposing?
Description:
We have identified a recurring pattern where users are submitting questions through the feedback form on the website. But, users are not following up by raising an issue or joining the Slack server for further discussion. We do not take email or name, as this isn't a support form. Any ideas on how we can increase conversion on this?
Code of Conduct
- I agree to follow this project's Code of Conduct
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the website feedback form flow and the follow-up paths to issue creation or Slack described in the report. Define a concrete conversion change and a measurable completion criterion before implementation; no files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100