Open jvalkeal opened 2 years ago
During a development of a carvel packages it has been convenient to keep adoc files in a sources itself. When getting close to supported release it makes sense to move these docs into microsite.
Essentially zap everything under https://github.com/spring-cloud/spring-cloud-dataflow/tree/main/src/carvel/docs and switch README to point to microsite. If there's something carver development related, keep those there.
Docs need a walkthrough to guide the user better from a "new to carvel" and "step by step" approach.
Related to #5371
During a development of a carvel packages it has been convenient to keep adoc files in a sources itself. When getting close to supported release it makes sense to move these docs into microsite.
Essentially zap everything under https://github.com/spring-cloud/spring-cloud-dataflow/tree/main/src/carvel/docs and switch README to point to microsite. If there's something carver development related, keep those there.