Clip

KO | EN

gitlite — search

#javascript #llm #golang #android #machine-learning #rust #deep-learning #linux #macos #java #awesome #vue #awesome-list #ios

(★ 9)

Content creation rules for Umbraco CMS

Clip Latest Version Download

Download Latest Version (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

One of the great features of Umbraco's backoffice is the permissions model applied to document (and media) types - developers can implement a tightly controlled information architecture by configuring the parent-child relationships between those document types.

That's lovely, and allows developers plenty of control over how the site is ultimately structured.

However, there are a couple of gaps in how that model works:

- it's not possible to control who can create which types
- it's not possible to control how many of each type can be created

Fret not, Clip is here to help.

# Control who creates what

We know Umbraco offers lots of flexibility, but sometimes we need to reign that in a little.

In large sites, with lots of user groups and more document and media types, we need to be able to control which groups can create which types.

Clip adds this functionality to the backoffice by allowing administrators to set permitted document and media types for each user group.

When creating new items, the allowed child node list is filtered to include only the permitted types.

# Control how many of each type

Sometimes it doesn't make sense to allow more than one instance of a document or media type.

Typically, a site might have one news landing page. It more than likely has one homepage.

A site for a restaurant might have a page for each location, but shouldn't allow editors to create additional locations.

Clip adds this control to the backoffice by allowing administrators to set a maximum item count for any document or media type.

When creating new items, the allowed child node list is filtered to include only types that haven't hit their maximum item count.

## Configuration options

- If a user group is added and has no document or media types selected, the group will be unable to create any items
 - If a user group is added and has only document types selected, the group will be able to create all media types as well as the selected document types
 - If a user group is added and has only media types selected, the group will be able to create all document types as well as the selected media types

The two latter options above are true assuming the document/media type has not hit a configured limit.

# Why Clip?

Clip follows hot on the heels of [Flip](https://github.com/nathanwoulfe/flip) and [Blip](https://github.com/nathanwoulfe/blip), so obviously needed to follow the silly naming pattern.

Blip is the Block List Item Picker.

Flip is the document-type flipper.

Clip trims the allowed child types.

Easy!

# Getting started

Install Clip: `dotnet add package Clip.Umbraco`.

After restarting your site, you'll find a new node in the settings tree - 'Content Creation Rules'.

The view allows adding rules for user groups and content type limits.

# Contributing

Sure, pull requests are more than welcome. Go for it.

# Changelog
Upgrading from v1.0 to either v10 or v11? There's some manual tomfoolery required.

Since v10+ includes support for media, the underlying data store had to change which meant Clip needs to distinguish Document and Media types, as well as the actual content type.

That then means there's no upgrade path without data loss (ie, if you update, you'll lose configuration). To combat that, export your existing configuration either manually or straight from the database, and manually re-enter same after updating. It's a bit of a pain, but a lot less painful than writing a migration to do the same.

Clip

Clip Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

Clip

Clip Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

Download README