Closed pwright closed 6 years ago
It think is worth to mention that proposal it's only to cover documentation for services. Other website elements are not covered.
@finp We have something tangible now with https://github.com/aerogear/service-docs. This is a single repo for anything related to the mobile services that end users (Mobile/Mobile Backend developers) would find useful.
I'd imagine there'd be other docs sources for things like UI guides, CLI installation & guides, IDE plugin installation & guides in the future too.
Is this OK with you? IS there anything needing updating in the proposal based on this approach?
@david-martin I see the content in services-docs as being orphaned for now. We'll need a lot more context and structure before publication, but I don't see anything to block progress. I wonder where docs related to mobile-core will live? another repo? would a mobile-docs repo make sense for all generic material?
would a mobile-docs repo make sense for all generic material?
Do you mean move existing content from service-docs to a new metrics-docs repo? I don't mind if that would make things easier for you.
Approving this PR as is though
Good to merge if we get another +1 or approval
+1
I like this idea. If the retrieval of docs from x many other repos can be kept automated, that would be great.
Maybe outside the scope of this proposal, but should we be thinking about how search will work on the site?