adam/vscode-front-matter
1
0 Fork 0
mirror of https://github.com/estruyf/vscode-front-matter.git synced 2026-11-03 17:12:21 +01:00
Code Issues 77 Packages Projects Releases Wiki Activity

Enhancement: disable certain content types for certain users #507

New Issue
Open
opened 2026-10-05 02:50:49 +02:00 by adam · 0 comments
adam commented 2026-10-05 02:50:49 +02:00
Owner
Copy link
Copy source

Is your feature request related to a problem? Please describe.
Yes. We have different users working on different content types. Some users work on all, but most of our users just work on one of them. For example, User 1 works on blog, User 2 works on docs, but User 3 works on both. Currently, when User 1 opens the Front Matter CMS Dashboard, they always have to change the "Showing" setting to blog, such that they only see the blog items:

image

Describe the solution you'd like
It would be great if we could limit the content types in a local file (for example, one in the .frontmatter directory). If the file is not present, Front Matter CMS behaves as it does currently.

Describe alternatives you've considered
Maybe an alternative would be the Local Settings, but as I understand that feature, it allows us to move the configuration to local files. That means we have to duplicate the configuration: The config of blog would need to be present on both User 1 and User 3's workstation.

If we can disable a content type locally, we could keep them all together in the Team Settings (frontmatter.json).

**Is your feature request related to a problem? Please describe.** Yes. We have different users working on different content types. Some users work on all, but most of our users just work on one of them. For example, User 1 works on `blog`, User 2 works on `docs`, but User 3 works on both. Currently, when User 1 opens the Front Matter CMS Dashboard, they always have to change the "Showing" setting to `blog`, such that they only see the `blog` items: <img width="141" alt="image" src="https://github.com/estruyf/vscode-front-matter/assets/1302357/b5458f38-c7d9-4b60-9ad9-fe9ccfc8130c"> **Describe the solution you'd like** It would be great if we could limit the content types in a local file (for example, one in the `.frontmatter` directory). If the file is not present, Front Matter CMS behaves as it does currently. **Describe alternatives you've considered** Maybe an alternative would be the [Local Settings](https://frontmatter.codes/docs/settings#team-settings-and-local-settings), but as I understand that feature, it allows us to move the configuration to local files. That means we have to duplicate the configuration: The config of `blog` would need to be present on both User 1 and User 3's workstation. If we can disable a content type locally, we could keep them all together in the Team Settings (`frontmatter.json`). <!-- github-sync-id:1874066719 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/vscode-front-matter#507