Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Reorganize documentation so that available modules are more easily visible
See original GitHub issueTitle: Reorganize documentation so that available modules are more easily visible
Description:
Describe your idea. Please be detailed. If a feature request, please describe the desired behavior, what scenario it enables, and how it would be used.
Our current (very thorough and beautiful 😁) readme has become very long and could benefit from being split up into different sections. It could help others better discover our tool if we made it easier to see at a glance what data Cartography pulls.
We can discuss this in more detail below but ideally we would have configuration and installation in docs/setup/ or something and all the other sections in their own folders under docs/.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@marco-lancini I would love that, I think a section on possible deployment options could be helpful. The section wouldn’t be prescriptive, but it would provide helpful examples on how to use it in prod. We could link to your blog post, and we could also take elements of it and adapt it here. I’ll create a follow-up issue to do this.
What would you think of a setup similar to the one outlined in the following blog post? (section “Deployment on Kubernetes”)