> For the complete documentation index, see [llms.txt](https://www.computerscience2.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.computerscience2.com/introduction.md). # Introduction Computer Science II is a full year course for students who have successfully completed Computer Science I and are continuing in the Academy of Information Technology. During the second year of study, students will be introduced to 3 major topics that will allow them to expand their Computer Science expertise attained in their first year. This includes learning to design a website for a small business using HTML and CSS while following Technology Project Management procedures and practices in all work, JavaScript Programming, Creating Android Mobile Apps with the MIT App Inventor Open Source Platform and Web Design with Database Concepts/E-Commerce. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://www.computerscience2.com/introduction.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.