> For the complete documentation index, see [llms.txt](https://docs.launchboard.app/cxd/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.launchboard.app/cxd/code-web-app-data-visualization/dashboard-layout-examples/dashboard-layout-with-html-css.md).
# Custom Grid 1
To create a grid layout like the sketch above, adjust your HTML and CSS like the following examples. But be careful not to simply copy and paste everything here.
### HTML
Notice that the "card" for the first chart also has a class called "full-width". We will use this class to make a chart span the full width of the page, while the others will fall into a grid with 3 charts per row.
```markup
```
### CSS
First, notice the *id="page" (#page)* style defines the normal grid design of 3 elements (or 3 columns) per row. `grid-template-columns: 1fr 1fr 1fr;` This applies to all the grid elements inside the *id = "page"* element.
Next, any element with the class *"full-width"* will start at the first position and span 3 columns. `grid-column: 1 / span 3;`
We can also add a style (look for *@media* ... below ) that makes our dashboard mobile-friendly where all the charts just stack on top of each other if the screen is less than 700px wide.
```css
/* This is not the complete CSS file contents.*/
/* It simply demonstrates the important styles for this layout example. */
#page {
display: grid;
grid-template-columns: 1fr 1fr 1fr;
grid-gap: 15px;
}
.full-width {
grid-column: 1 / span 3;
}
@media only screen and (max-width: 700px) {
.card {
grid-column: 1 / span 3;
}
}
```
---
# 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://docs.launchboard.app/cxd/code-web-app-data-visualization/dashboard-layout-examples/dashboard-layout-with-html-css.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.