Restructure Lab docs

[katarinasupe]

Memgraph Lab documentation has been fully restructured with the goal of providing better readability and developer experience. Also, this eases the process for future contributions to the Memgraph Lab docs. The changes involve flow updates, as well as adding new content and updating the existing one.
Redirects have been updated as well.

• Is it okay to call this page section Memgraph Lab and where should it live on the left-hand side menu?
• Add new images from design

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
documentation	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 10, 2025 11:39am

[tonilastre]

I like the new structure and the main page name being "Memgraph Lab". You did a great job in structuring the docs and filling out missing information (e.g. run history, collections, streams, ...).

I've added some comments as additional context to the existing content.

I was also thinking if users would benefit with some sort of F.A.Q that would have a lot of Callouts from these pages, e.g.:

• A note about host.docker.internal
• Netoworking around docker-compose and service naming
• Copy/paste allow list in the browser
• ...
• (other common issues)

[tonilastre]

Suggested change

	Once you've added the enterprise license key and organization name, and if everything is configured correctly, you should see the following log message from Memgraph Lab:
	\`\`\`
	INFO: Enterprise license applied successfully. Enjoy the premium features.
	\`\`\`

[tonilastre]

Not sure how to add backtick in the suggestion so that it doesn't close the suggestion.

[tonilastre]

Suggested change

	By selecting a certain node or relationship type, Memgraph Lab will provide
	information about the current number of nodes or relationships of that type, as
	well as the percentage of existence of each property across the nodes and
	relationships of that type.
	By selecting a certain node or relationship type, Memgraph Lab will provide
	information about the current number of nodes or relationships of that type, as
	well as the percentage of existence of each property across the nodes and
	relationships of that type.
	If you're connected to a Memgraph instance running with the `--schema-info-enabled` configuration flag, you'll see the types for each node and relationship property.

[tonilastre]

Not anymore. This is from the app:

To give you the best possible results, GraphChat requires Memgraph procedures to generate graph schema. Memgraph v2.16.0 or above is required

We removed the llm_util dependency and GraphChat will use:

• SHOW SCHEMA INFO if available
• schema procedure if exists (e.g. schema.rel_type_properties)
• Cypher queries as a last resort

[tonilastre]

Do we want to mention somewhere on this page that the run history is saved locally in the browser, so any new browser instance will have a fresh state?

[tonilastre]

I am thinking if SSL and BASE_PATH should be subpages of the installation and deployment, especially now when we will be adding CONFIG for settings, node actions, datasets, etc.

[tonilastre]

Suggested change

	Once you **Run** a query (by clicking a button or pressing **CTRL** +
	Once you **Run** a query (by clicking a button or pressing **CTRL/CMD** +

[tonilastre]

We could also add:

---

If latitude and longitude data are not stored in the default lat and lng properties, you can use a Graph Style Script (GSS) to map alternative fields for location tracking. For example:

// nodes have .latitude and .longitude fields
Define(LATITUDE_FIELD, "latitude")
Define(LONGITUDE_FIELD, "longitude")

// In the case of numeric latitude and longitude properties, set them up for a switch to a map view
@NodeStyle And(IsNumber(Property(node, LATITUDE_FIELD)), IsNumber(Property(node, LONGITUDE_FIELD))) {
  latitude: Property(node, LATITUDE_FIELD)
  longitude: Property(node, LONGITUDE_FIELD)
}