feat: add ability for the user to comment on the documentation

[JivusAyrus]

Checklist

• run make test
• PR title must follow conventional-commit-standard
• tests and/or benchmarks are included
• documentation is changed or added
• commit message and code follows the Code of conduct

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
wundergraph-docs	✅ Ready (Inspect)	Visit Preview	Oct 17, 2022 at 2:07PM (UTC)

[StarpTech]

The preview doesn't seem to work.

[JivusAyrus]

The preview doesn't seem to work.

Sorry have to add envs in Vercel

[JivusAyrus]

Don't think it would work in the preview as it's a different domain.
giscus.wundergraph.com has frame-ancestors 'self' wundergraph.com *.wundergraph.com;

[StarpTech]

Fine for me if it is working on prod.

[StarpTech]

LGTM

[jensneuse]

Just one question. Would it make sense to start discussions on this repo with the topic docs? This way we keep it all in one place. Website docs can go into the other repo.

[JivusAyrus]

That's what I thought initially.
What do you mean by "Website docs can go into the other repo."?

[jensneuse]

That's what I thought initially. What do you mean by "Website docs can go into the other repo."?

We have one repo (https://github.com/wundergraph/comments) where we put the comments for the website (wundergraph.com).

Should the comments on docs.wundergraph.com be handled on this repo here (wundergraph/wundergraph) or should they also go on the wundergraph/comments repo?

[JivusAyrus]

I would prefer wundergraph/wundergraph. We can create a "Docs" category in discussions.