Fine-Grained User Role Management
This feature allows for precise control over user permissions by enabling custom role creation and the ability to adjust restrictions down to the field level. • Custom Roles: Define user roles tailored to your project’s specific needs. • Granular Permissions: Assign and modify permissions at a detailed level, for every action within the project and organization. • Enhanced Security: Ensure only authorized users can access or modify specific parts of your content, improving overall security and workflow control. • Scalable for Teams: Perfect for teams of any size, offering flexibility in user access and content management.
AI Multilingual Document Translation
This feature allows users to translate project content into multiple languages directly within Caisy using AI-based models. By integrating any AI provider via an API key, users can generate translations for specific fields within a project. • Flexible AI Integration: Simply add your API key from any AI provider (such as OpenAI), and the system will handle translations within Caisy. • Language Selection: Choose the language you want to translate from and apply translations to empty fields within your project.
Automatically create slug based on document title
Currently, I have a hard time explaining to some of my customers (who are used to WordPress) why they have to manually set a slug for each document. To make life easier for my customers and myself, I would love for caisy to just automatically set and update a slug based on the title of the Document, converting spaces to hyphens and dealing with Umlaute automatically. Demo: document_title: "Über uns", autogen_slug: "ueber-uns", Why is this important? If I don't want my customers to manually add slugs, I currently have to fetch all Documents just to convert the title of these Documents to a slug-version. With the converted titles, I can then perform a .find() on them to match the current URL to one of the converted slug.
Add external datasources for select fields
I would like to add external datasources for select fields. I will use a sql database in addition to caisy, and I have some serverless functions returning a list of entries as an array of json objects. (e.g. mypage.com/api/v1/categories) will return an array of objects like [{value: 'mycategory', label: 'My category'}, ...] I would like to have a possibility to add this endpoint to my select fields as possible values, so that an author can select one of these entries.
where filter: make filterting connections possible
(Sorry for the feature request spam, I'm currently evaluating if caisy could be the right thing for a new project) I would like to create a GraqhQL query with some where: rules, that filter connection items. Meaning that, "give me all posts where the field `categories` includes the category with the field `slug` = `example`" So for example: query { allPost(where: {category: { slug: { eq: "example" } } }) { ... } }
2-way-binding connection field
I am pretty new to GraphQL, so I might be doing it wrong. If so, please tell me :) However I think this could make things easier: Sometimes I have to fetch all Categories (a component-bp. I use) that I created. Each category has a connection field where 0-n Articles (a document-bp. I use) can be linked. Obviously, I now get a nice list of all Categories with the linked articles. However, when I fetch a specific Article and want to know which category it is in - I now have to make a somewhat redundant "Category" field and manually select the category it is in - eventhough the Article is already linked to the category, but only from the side of the Category. As I said, I don't know if I am missing something or just do it wrong, but an "advanced" connection field, that works 2-ways would be nice. So as soon as I link an Article from my Category using the "advanced" connection field - this field is automatically generated in my Article-Blueprint and connects the article to the category.
Zapier Integration
Integrate our system with Zapier. This will enable users to automate workflows between our system and other applications they use.
Document Commenting Function with User Mentions and Priority Setting
Introduce a commenting function within the document editing environment that allows users to leave comments, mention other users, and assign priorities to their comments.
Live Preview
Introduce a live preview feature that will allow changes made within caisy to be instantly reflected on the frontend.
Real-Time Editing
Enable live collaboration on documents, allowing multiple users to work simultaneously on the same document and visibly track each other's activities. Real-Time Editing: Multiple users should be able to edit the same document simultaneously. Any changes made by one user should immediately be visible to all other users working on the document.
Collapsible Navigation Bar with Label Visibility
Introduce a collapsible navigation bar in the user interface that users can open and close. When open, users should be able to see the labels next to the icons, and when closed, only the icons should be visible.
Modify Rotation and Zooming Point to Center of Cropping Area
Change the rotation and zooming point of an image from its current middle point to the middle of the cropping area. This adjustment will give users more control over the display and manipulation of their image.
Convert Document Blueprint to Component and Vice Versa
Provide users the ability to convert a Document Blueprint into a Component and vice versa. This will help to rectify accidental misuses or misclassifications of documents and components in the system.
Focal Point for Image Assets
Enable users to select a "focal point" on image assets after they have been uploaded to the system. This focal point should remain visible at all times, irrespective of any cropping or resizing that may be applied to the image.