> For the complete documentation index, see [llms.txt](https://knowlg.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowlg.sunbird.org/learn/product-and-developer-guide/content-service/content-apis/code-structure.md). # Code Structure ### Repository Please refer to the provided link for the content APIs code. {% embed url="" %} ### Folders structure #### Content Actors Within this module, the functionality to handle concurrency and scalability is implemented using AKKA actors. #### Content Service By utilizing the Play framework, this module ensures a streamlined and organized approach to developing RESTful APIs. It simplifies the process of defining routes and implementing controller actions, allowing for efficient handling of incoming requests and consistent responses. The Play framework's emphasis on clean and concise code contributes to the overall maintainability and scalability of the application. #### Hierarchy manager \ #### Collection CSV actors \ --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://knowlg.sunbird.org/learn/product-and-developer-guide/content-service/content-apis/code-structure.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.