Pavel,
Yes, I mean a separate repository. The reason is that documentation is
usually updated after the product version is released. As Ilya pointed
out, keeping the docs in the main Ignite repository would entail
completing the docs before the release date, which is not possible under
current circumstances.
Ilya,
You can look at your company's documentation for a working prototype
turned production-ready approach. The approach has been tested for a
while and proved to be successful, at least with respect to our goals here.
-Artem
On 23.06.2020 12:48, Ilya Kasnacheev wrote:
Hello!
I'm not really sold on the github version yet, I would like to see a
prototype of such documentation before deciding, so for me it'w
0
Pavel, we don't have enough discipline to make sure that all documentation
is ready at the time of release, and we may need to add notices here and
there after a release is already out. This means, separate git repository,
or at least separate git tag on that repository, is needed.
Regards,
