Explain functional aspects of Nexus in the README

[eloydegen]

I am trying to figure out what Nexus actually does. The current README does not really help me understanding Nexus, and I think it should do that, in technical terms. The quotes from the main site do not tell me much:

• Publish and cache components in a central repository that connects natively to all popular package managers.
• Control the lifecycle of staged builds and custom metadata directly from your CI/CD server.
• Handle global workloads with dynamic storage, cleanup policies, and multi-node resiliency.

How does it communicate with other nodes, some TCP protocol? Does the software has a web interface? What packages managers are considered the popular ones here?

Questions like that would be great to answer in a README.

[nblair]

Hi @eloydegen - thanks for opening an issue. Sonatype maintains comprehensive documentation about Nexus Repository at our help site: https://help.sonatype.com/en/sonatype-nexus-repository.html

This github repository is simply read-only mirror of the core, open-source elements of the product.

[eloydegen]

Hi, thanks for the link! I clicked a bit through it... but I still don't really see an easy explanation of what Nexus actually is (in technical terms) and how the open source core fits into this wider product.