Roadmap

Have something to say?

Tell caisy how they could make the product more useful to you.

Planned

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.

An Anonymous User 7 months ago

1

💡 Feature Request

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.

Fabian 9 months ago

💡 Feature Request

Completed

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" } } }) { ... } }

Fabian 9 months ago

1

💡 Feature Request

In Progress

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.

Leon 9 months ago

1

💡 Feature Request

Completed

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.

Valentino Loenicker 11 months ago

💡 Feature Request