# spikes ### CSS architecture How should you write CSS to ensure it's easy to read, maintain and scale as a website grows? #### Questions to consider 1. Why are CSS naming conventions useful? 2. When might specificity become a problem? 3. How can *composition* help us build UIs? ### CSS layout How does CSS decide where to put elements on the page? #### Questions to consider 1. What is the box model? 2. How does the `display` property affect layout? 3. How does the `position` property affect layout? ### Responsive design How do you design and build a webpage that looks good on any device? #### Questions to consider 1. What CSS units should we use for dimensions? What are absolute and relative units? 2. When should you use a media query? Are they only for screen size? 3. How can mobile-first CSS make responsive styling easier? ### Github projects #### Questions to consider 1. How can we leverage Github projects to help us plan and track work? ### Accessibility How do you write markup so that your page is accessible to as many users as possible? #### Questions to consider 1. Who does semantic HTML benefit? 2. How does ARIA relate to HTML? 3. What's the difference between *accessible* and *inclusive*? --- # Agent Instructions: 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: ``` GET https://founders-and-coders.gitbook.io/coursebook/src/course/syllabus/developer/week01-project01-basics/spikes.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.