Introduce a commenting function within the document editing environment that allows users to leave comments, mention other users, and assign priorities to their comments.

Planned

Document Commenting Function with User Mentions and Priority Setting

Hi there! I would prefer to have explicit enum types in GraphQL for select fields. So that I know the value is going to be one of those values. E.g. color: `null | 'green' | 'blue'|`. Currently, I only get `string` as a type.

Low Priority

Select fields: Correct types in GraphQL Schema

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.

Modify Rotation and Zooming Point to Center of Cropping Area

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.

Convert Document Blueprint to Component and Vice Versa

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.

In Progress

2-way-binding connection field

Introduce a live preview feature that will allow changes made within caisy to be instantly reflected on the frontend.

Live Preview

If I create a "Tag Field" and select it via GraphQL, I only get an array of Ids. This doesn't help much, since I don't see an option to get the actual tag values anywhere via the api.

High Priority

Tag Field GraphQL field returns only ids

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.

Completed

Real-Time Editing

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.

Collapsible Navigation Bar with Label Visibility

Rebuild the grid view of the asset library from scratch, focusing on improving performance and enhancing user experience.

Improved Grid View for Asset Library

(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:<pre><code class="language-typescript">query {
 allPost(where: {category: { slug: { eq: "example" } } }) {
 ...
 }
}</code></pre>

where filter: make filterting connections possible

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.