The SDK's front door. CGS is the singleton every other service is reached through, SdkConfig configures it, and three of the services it hands out — Content, Download, Reader — live here too. The fourth, CgsAuth, has a package of its own.
The SDK's entry point: initialize it here, then reach every service from here.
Which backend the SDK talks to.
Everything the catalogue holds — articles, issues, videos, media and publications — as seen by the profile currently active on the session.
Fetching issues onto the device so they can be read offline, and following what the fetching is doing.
The reading experience: an issue rendered page by page, or an article rendered as text.
How the SDK is set up. Build one and hand it to CGS.init.