💄 Update website

- Add a few changes to the landing
- Hide test integrations
- Update doc of Anyquery limitations

Author: julien040

website/public/icons/logs.svg

@@ -44,7 +44,8 @@ If you encounter a `no query solution` error, it means that the table requires p
 Anyquery has several limitations that you should be aware of:
 
 - Anyquery is based on SQLite, which doesn't support concurrent writes. You can run multiple read queries at the same time, but only one write query at a time.
-- You cannot run `DESCRIBE` or `SHOW CREATE TABLE` on file tables. This is due to the way anyquery handles file tables. To observe the schema, you need to create a virtual table as specified in the MySQL server section.
+- You cannot run `DESCRIBE`, `WITH`, or `SHOW CREATE TABLE` on file tables. This is due to the way anyquery handles file tables. To observe the schema, you need to create a virtual table as specified in the MySQL server section.
 - Concurrent anyquery processes with the same configuration database may lead to unexpected behavior. It's recommended to run only one instance of anyquery at a time for a given configuration database (pass the `-c` flag to specify a different configuration database).
 - Dot and slash commands don't work when `PRQL` or `PQL` is enabled. You need to switch to `SQL` mode to run dot and slash commands.
 - Anyquery is slow on `ORDER BY` and `GROUP BY` operations. It's due to the need of requesting all the data from the source and then applying the operation. It's recommended to use `LIMIT`, `OFFSET` and `WITH` clauses to reduce the amount of data to process.
+- DDL statement on integration tables is not supported. You can only run DML statements on integration tables. The schema must always be defined beforehand (it can be fetched on the fly though).