Hello Sebastian,
It’s been a long time since we met… I came with many new ideas and needs. By the way, I logged into the forum after a long time and saw that many of my requests were developed. This is very pleasing. Thank you.
-
In GraphQL queries, only the id information of asset elements is received in fields such as data__dynamic or component__dynamic. It would be great if this area could be expanded and slug and other important frequently used features could be added. Also, having a place where we can enter alternative text labels for website usage of assets can be a nice feature in terms of meeting website accessibility rules. The most correct use of this would be to create a field where multilingual alternative text can be entered in the image upload field when the type image is selected for the Asset field. However, if this is difficult to do, it would be great to create a multilingual field called Image alternative text where Assets are listed and their properties are entered, and to be able to use the alternative text label data for images in graphql and api calls. (It should not be forgotten that this is also added automatically to the data__dynamic and component__dynamic fields)
-
The Rules section allows us to do creative things in many areas, but CronTime and conditions should be added to the Trigger reason section in the Rules section. Thus, the job related to certain periods is triggered and if the conditions are met, the expected job is performed later. The aim here is to filter some issues related to data at certain times and run a job if the relevant conditions are met. If the Condition section has advanced script writing capabilities, something much more advanced can be offered.
-
The History section on the Dashboard page is useful. But it deserves more details. A separate page can be created for History and a link can be given from here to go to the relevant page, and it is very important for the user to filter people on this page with small filters, especially people, and also to provide links to the work done. For example, when a person says that they created a schema, the schema statement here should be clicked to reach it, or when a content is updated, the relevant content should be clicked to go to it.
-
Quick Nav Search This area should definitely be improved. When desired, a separate page should be opened for Search, and the search results should be displayed in pagination on this page. When a text is used in many places, it will be very useful to easily detect them and update them one by one.
-
In GraphQL sorting features, the ordering feature ç, ş, ğ, ö, ü does not work in Latin alphabet characters (for example: Turkish). I believe this should be improved and corrected.
-
A field in the schema area can be used in the creation screen, but cannot be used in the update screen (disabled in ui or hide in ui) should be added. There are many places where the feature can be created but cannot be changed is required. This can be done from the script field, but it would be more useful if we disabled the field in terms of user experience.
-
One of the most needed things in the dedicated hosting option is index creation. By making this dynamic, it should be possible to create a dynamic index for fields within a schema. In this way, very useful and fast systems can be produced.
-
An API leg where schema and event data can be permanently deleted. When a schema is deleted optionally, the data belonging to that schema can be permanently deleted. This may be specific to the dedicated hosting option. When a schema is requested to be deleted, a popup appears and all data and events (EventStore) belonging to that schema are cleared. In this way, garbage data is prevented from remaining in the database.
-
When a field is created as a string in the schema and the display type is selected as dropdown, it may be much more useful to be able to enter not only values but also a title and value for that field. An option can be developed for this. Perhaps this string data type can be KeyValue-style data instead.
-
When you want to pull content data from a schema field to the API calls section in ClientLibrary, you can fill the relevant model with a fluent parameter or with the data related to its relationships with an attribute.
For example: by adding an attribute to the relevant property in the data model class, you can specify that this is a reference field and
[ReferenceField(Resolve=true)]
public Blabla TestData {get;set;}
When xContentClient.GetAsnyc() is called, the reference data can be loaded.
Another alternative is to fill these reference fields with the use of xContentClient.WithReference(m => m.TestData, m.XData).GetAsnyc();
-
If an Asset field is added to the schema and the type of this asset data is selected as Image, an additional feature appears and the Add Watermark option appears. A text written here can be written directly on the assets. A feature that includes the asset writing position would be nice. For example, Left Down, Right Up, Diagonal etc.
-
When the contents are selected with the help of a checkbox on the content listing screen, adding the export data feature on the menu that opens and automatic synchronization with import from json data on the listing screen on another project would be a very nice feature. It can be very useful especially for test and prod environment data transfers in dedicated installations.
-
Backup feature can be added with options excluding and including Assets. In other words, a new dimension can be added to the Backup feature. Backup the schemas I want, backup assets, backup all, etc. Because sometimes there is a need for features that facilitate the need to move only a schema and the content belonging to that schema.
-
When the Asset field is created in the schema, a very large field is added to the view. Another view option may be to choose a simpler view and a view that takes up less space on the screen. We often need this.
-
I know it will be a difficult development, but an advanced workflow structure plugin can bring the product to a great point. What I am talking about is actually a structure like Zapier, but it can be matched with the data inside… There is an interface structure etc. in the Elsa-Workflow project, but it is very open-ended how creative development can be done with Squidex. I wanted to add a note in case something comes to mind for you.
If you need details about any request or if there are points you do not understand, please write and I will try to answer quickly.
These are the needs and suggestions that arise from our long-term experience in our work.
Thank you for everything.