Custom Sidebar Extension #10950
Replies: 3 comments 11 replies
-
|
Like it! I've been thinking through a more "slot-based" extension type, that basically allows you to inject a custom vue component in a number of different "slots" in the app, like the sidebars, headers, etc (cc @nickrum). |
Beta Was this translation helpful? Give feedback.
-
|
i switched to directus from contentful. The feature discussed is presented there from the beginning. As for me -it was the most demanded.
|
Beta Was this translation helpful? Give feedback.
-
|
Heya! Thanks for opening this feature request! This feature request has received over 15 votes from the community. This means we'll move this feature request to the Under Review state! The Core team will schedule a meeting to review this request as soon as possible. The discussion will then be approved or denied. You may or may not be invited to join this meeting with the core team. For more information, see our Feature Request Process. |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
Hi, first of all, thanks for this great project!
I could not find a discussion dedicated to this exact idea/feature so I am starting one here.
Feature Description
It would be great if there was a way to add new modules/components to the sidebar using extensions. Currently, the main purpose of the sidebar is to expose additional context/view-specific metadata and tooling (e.g. revisions, comments, shares in the details view). Additionally, there is also a sticky section at the bottom (currently only contains the activity log) that shows the same elements regardless of the current context/view. I believe it would be great if an extension could add custom modules/components to both of these sections (1. contextual section, 2. sticky section).

For the contextual section, the extension would have to define a condition that determines if the sidebar component should be visible (e.g. only show the component for specific collections, layouts, etc.).
The custom components (both contextual and sticky) should also have access to the current context (e.g. which collection/item is currently displayed)
Example Use Cases
Alternatives
It would be possible to create custom layouts or modules to implement some of the examples above. However, using the sidebar would be a more elegant approach in my opinion. Custom contextual components would also provide an easy way to extend the functionality of the existing layouts/views and extensions would not have to recreate existing functionality in custom layouts/modules (e.g. displaying a collection and allowing multi-selection to perform some batch operation).
Beta Was this translation helpful? Give feedback.
All reactions