In the last CDEvents working group meet up, I suggested creating a FAQ, "Frequently Asked Questions", page.
A FAQ page can be a good landing spot for people who are unfamiliar with CDEvents. It can also hold information that does not fit neatly into other technical docs or the whitepaper.
Some sample questions:
When will the next version of CDEvents be published?
How does CDEvents deal with private data?
I want to update the spec with new data. What should I do?
To try to minimize duplication, we can refer to existing docs, whitepaper, or github issues.
I propose we start by creating a new document, "faq.md", in this repository.
If we find this page has valuable content, we can then update either the documentation or community sites with links to this faq page.
In the last CDEvents working group meet up, I suggested creating a FAQ, "Frequently Asked Questions", page.
A FAQ page can be a good landing spot for people who are unfamiliar with CDEvents. It can also hold information that does not fit neatly into other technical docs or the whitepaper.
Some sample questions:
To try to minimize duplication, we can refer to existing docs, whitepaper, or github issues.
I propose we start by creating a new document, "faq.md", in this repository.
If we find this page has valuable content, we can then update either the documentation or community sites with links to this faq page.