> For the complete documentation index, see [llms.txt](https://components-for-learning.gitbook.io/components-for-learning-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://components-for-learning.gitbook.io/components-for-learning-documentation/advanced/display-inline-components-grouped.md).

# Display inline components grouped

When editing content with C4L, some components (such as `Due date`, `Estimated time`, or `AI use allowed`) are designed to appear as short labels. In many cases, it is clearer to show more than one of them on the same row.

At the moment, the plugin does not provide a direct option to group these components exactly as needed. For now, the most reliable method is to use **code mode** and add a small HTML structure.

You do **not** need programming knowledge: just copy a template, paste it, and replace the sample text.

### Step by step

1. Edit the page or activity where you want to display these components.
2. The components should **not** have the Align Left variant applied, so if that's the case, remove it first. The alignment will be controlled from the container we are adding.
3. Open the editor code mode Main menú →View → Source Code.
4. Find the place where you want the block to appear, i.e:

```html
  <div class="c4lv-duedate" aria-label="Due date">
    17 Nov
  </div>
  <div class="c4lv-aiuseallowed" aria-label="AI use allowed">
    AI use allowed
  </div>
```

6. Wrap your components with the `c4l-inline-group` class:

```html
<div class="c4l-inline-group">
  <div class="c4lv-duedate" aria-label="Due date">
    17 Nov
  </div>
  <div class="c4lv-aiuseallowed" aria-label="AI use allowed">
    AI use allowed
  </div>
</div>
```

7. (optional) By default, that class aligns the group of items to the right. You can aligne those to the left by adding the class `c4l-display-left`:

```html
 <div class="c4l-inline-group c4l-display-left">
  <div class="c4lv-duedate" aria-label="Due date">
    17 Nov
  </div>
  <div class="c4lv-aiuseallowed" aria-label="AI use allowed">
    AI use allowed
  </div>
</div>
```

7. Save changes and return to the normal editor view.

### Which components can be grouped?

* [Estimated time](https://componentsforlearning.org/components/estimated-time/)
* [Due date](https://componentsforlearning.org/components/due-date/)
* [Grading value](https://componentsforlearning.org/components/grading-value/)
* [AI use allowed](https://componentsforlearning.org/components/ai-use-allowed/)
* [AI use not allowed](https://componentsforlearning.org/components/ai-use-not-allowed/)
* [AI use reported](https://componentsforlearning.org/components/ai-use-reported/)


---

# 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://components-for-learning.gitbook.io/components-for-learning-documentation/advanced/display-inline-components-grouped.md?ask=<question>&goal=<endgoal>
```

`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.