Documentation process

[MaryBethBaker]

Hi @steve-h,

Is there any part of this project where I can help document or provide context to others that might want to re-use it?

Thanks,
Mary Beth

[steve-h]

I am going to do some basic high-level-view illustrations for a meeting next week and these can be added to the repo.

The code IS the document so far, and anyone reusing it now would need to have code-level understanding. It is not near turnkey deployable. As a minimum viable product, the focus was to learn about functional user experience first before deployability at scale was addressed.

I need to list the known roadmap items as well as a start to forward planning so that others know what is done and what needs work in future iterations. The dev branch is the latest and I was waiting for the first consultation to close before merging it to master.

drupalwxt uses Hugo as a documentation site base. The consultation tool would ultimately need a sophisticated approach like this. Thus a separate companion documentation repo.

Setting up such a documentation repo would be my recommendation and if you want to get an empty one going then that would be useful while waiting for content :-)

[MaryBethBaker]

@steve-h Thanks for the suggestions. I'm excited to see the MVP and presentation next week.

@sboots Do we have experience using Hugo or does your php framework integrate with an alternative documentation repo... something like handlebar.js? Or maybe something I haven't heard of.

Thanks all!