On the contact page there is contact form, and small button "Send".
Below is huge CTA button.

It can be misleading.
When a user fills out a form, they may accidentally click a larger button and lose the entered data.

CTA button should be moved or "Send" button should be more visible

Similar like in Api Docs generated from editor.flotiq.com

It seems that there is no documentation on the Flotiq Mobile Expo - this should be fixed.

Hi,

I found a typo in the code example on this page https://flotiq.com/docs/API/content-type/creating-ctd/

curl -X POST "https://api.flotiq.com/api/v1/internal/contenttype" -H 'accept: */*' -H 'X-AUTH-TOKEN: YOUR_API_KEY' -H 'Content-Type: application/json' --data-binary '{"name":"blogposts","label":"Blog Posts","schemaDefinition":{"type":"object","allOf":[{"$ref":"#/components/schemas/AbstractContentTypeSchemaDefinition"},{"type":"object","properties":{"title":{"type":"string"},"postContent":{"type":"string"}}}],"required":["title","postContent"],"additionalProperties":false},"metaDefinition":{"propertiesConfig":{"title":{"label":"Title",inputType":"text","unique":true},"postContent":{"label":"Post content","inputType":"richtext","unique":false}},"order":["title","postContent"]}}'

Missing " before the first occurrence of inputType property.

I think the error description returned from the API is quite misleading: Invalid json message received.

Issue Summary

Typo in code example.

The explanation of hydration in the Getting single Content Object section would be much easier to understand if, instead of showing a very long GET result with hydration level 2, you would present an example of a hydrated and non-hydrated object, as you did in Listing Content Objects section.

Hi,

I wanted to see the documentation you're talking about, but there is an error. Link comes from predefined-content-types

The description of filters for content object listing is chaotic and hard to read due to the sheer amount of filters and descriptions for each and every one of them. Also, examples are not clear enough, so it's harder to translate them into a project.

https://flotiq.com/docs/API/content-type/listing-co/#listing-content-through-the-api

The whole part of the page describing filters is wordy and takes up the majority of the page content.

Please consider creating a selecting list for every filter type as you do with response examples and overall make the page more user-friendly.

Hi,

there is a 404 error when I click on the link Zapier & integrations.

Issue Summary

The description of filters param in the search API is not clear as to how the request should actually look. Additionally, the field is declared without brackets, as opposed to other fields which can take multiple values.

the documentation should be improved to clearly state how a developer can use the filters.

Issue Summary

Flotiq dashboard documentation mentions that Number fields only accepts integers, while the How to handle Content Type Definitions page properly mentions Any number, integer, float and double.

Issue Summary

We are still providing examples with ID field being set, which may suggest it is still required, which it is not.

Please add documentation on the "Custom links" plugin. It's a really useful tool!

I suggest some additional informations which should help users to easier get SDK packages working for them:

• Information about needed Java installed to run command
• Information about possibly problem with plugin versions and how to solve it
• Information that user should have create new file with configuration and requests. It's showed on the video below, but for me it wasn't obvious.
• Information that user should copy example request to check if it work, he just should use request from sdk docs.
• Information how to call the code from app.js (file with conf and request)

Search API is based on ElasticSearch, but ES knowledge should not be necessary to use standard search functions.

Search docs: https://flotiq.com/docs/API/search/

Example request with order_by, according to docs:

1. Search all [works] https://api.flotiq.com/api/v1/search?q=*&auth_token=__TOKEN__
2. Search all ordered by created [error]: https://api.flotiq.com/api/v1/search?q=*&order_by=created&auth_token=__TOKEN__

Search all ordered by causes error:

        "q": [
            "Malformed query"
        ]
    }

We should use created.keyword (notice "keyword", that is not mentioned in docs)
https://api.flotiq.com/api/v1/search?q=*&order_by=created.keyword&auth_token=__TOKEN__
And it works fine.

Please add info on when should I use .keyword or refer to ES docs

Current left menu scroll is hidden and only appear when we hover over the menu.
Will be better to allways show that scroll that there is more to see on that page.

Current scroll is not allways visible.
Is hidden when we are in the middle of the page and we scroll to top.
Jump to top of the page.

Current behavior:

Example feature:

Hi, it's me. Again.

I'm trying to aggregate data according to the Search Api Deepdive article. I can't make it work with rate property which is a numeric type.

This is how schema looks like:

{
            "id": "",
            "name": "blogposts",
            "label": "Blog Posts",
            "internal": false,
            "schemaDefinition": {
                "type": "object",
                "allOf": [
                    {
                        "$ref": "#/components/schemas/AbstractContentTypeSchemaDefinition"
                    },
                    {
                        "type": "object",
                        "properties": {
                            "rate": {
                                "type": "number"
                            },
                            "title": {
                                "type": "string",
                                "minLength": 1
                            },
                            "postContent": {
                                "type": "string"
                            }
                        }
                    }
                ],
                "required": [
                    "title"
                ],
                "additionalProperties": false
            },
            "metaDefinition": {
                "order": [
                    "title",
                    "postContent",
                    "rate"
                ],
                "propertiesConfig": {
                    "rate": {
                        "label": "Rate",
                        "unique": false,
                        "helpText": "",
                        "inputType": "number"
                    },
                    "title": {
                        "label": "Title",
                        "unique": true,
                        "helpText": "",
                        "inputType": "text"
                    },
                    "postContent": {
                        "label": "Post content",
                        "unique": false,
                        "helpText": "",
                        "inputType": "richtext"
                    }
                }
            },
            "deletedAt": null,
            "createdAt": "2021-03-23T14:36:47.000000+0000",
            "updatedAt": "2021-03-25T10:33:53.000000+0000"
        }

Is it a bug or am I doing something wrong?

Issue Summary

Data cannot be aggregated if you are using numeric type property.

Issue Summary

The documentation for workflows is missing, and since this feature is particularly interesting to our enterprise customers - we should provide a brief description.

Old copyright on page:

Copyright © 2019 onwards Flotiq

Suggestion:
Copyright © 2019 - [current year] Flotiq

During installation on wsl2, I follow instructions:

Without docker:
pip install -r requirements.txt
To start server use: mkdocs serve

Then I get

$ mkdocs serve
Command 'mkdocs' not found, but can be installed with:
sudo apt install mkdocs

After I type

$ sudo apt install mkdocs

it works as expected

Should it be added to the readme, or did I miss something?

I had a little issue trying to follow your instructions. In CTD section you show how to create CTD blogposts.

In the first example on https://flotiq.com/docs/API/content-type/creating-co/ you use blogposts, then the code examples have blogpost which has a different schema, so the examples do not work.

So I think you wanted to use blogsposts.

Current behavior:

Prototype fix:

Missing image on Gatsby plugin docs

Hi,

I've read the article about Banner rotator
It seems cool and very easy to use, but I have some problems with the example.

In your example in js code, you're using banners object's properties. The keys are lowercased, not such like in your example, so you should use f.eg. {rotator.width}x${rotator.height} instead of {rotator.Width}x${rotator.Height}.

I also have a problem with hydration, but only when using fetch in the browser. Curl and postman's responses are ok.

It doesn't work, so I cannot use additional properties like id or extension., but I've changed my scoped API key, which has all permissions to a global one and it started works.

Do you have any idea why is that?

(I'm working in local env).

Issue Summary

Hydration does not work with scoped API key.

The https://flotiq.com/docs/API/ page is significant to users.
Examples should be eye-catching and consistent. This is example without "example box", and can be omitted.

This example should be marked as other examples in box: