> For the complete documentation index, see [llms.txt](https://docs.roomle.com/rubens/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roomle.com/rubens/whats-new/2025/march-2025.md).
# March 2025
## Configurator/Room designer news
### The initial launch of Room Designer attics feature is coming closer :eyes:
We will soon launch our attics feature within the room designer. Here is a small teaser :star\_struck:
Within the room designer, users will be able to create attics for walls. Just select a wall and either create the attic via the flying menu or the corresponding toggle in the wall settings drawer. Users can then adapt parameters like the height of the wall or the distance of the sloping roof in the wall menu. The feature will be launched soon.
Attics in the Rubens Room Designer 3D mode
Same is possible when entering the 2D mode of the plan. The measurements of the attic can be adapted directly in the corresponding measurment bubbles.
Attics in the Rubens Room Designer 2D mode
### Room Designer improvements construction elements
We now show all available windows & doors (configurable and static) as corresponding variant parameters in the UI after the user selected one. So the user can switch between static and configurable construction elements when replacing the selected construction element.
### QR Code for save draft
When clicking the save draft button, the user receives a QR code that holds the link to the saved configuration. The user can then check out his saved configuration/room scene on his mobile device. This feature works both in the configurator and the room designer.
---
# 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.roomle.com/rubens/whats-new/2025/march-2025.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.
%20(1).png?alt=media)
%20(1).png?alt=media)
%20(1).png?alt=media)
%20(1).png?alt=media)