Website SEO updates

Author: fgatti675

CHANGELOG.md

@@ -371,7 +371,7 @@ const userManagement = useBuildUserManagement({
 
 The first beta release of FireCMS v3.0.0.
 Check all the new features and improvements in the [documentation](./what_is_new_v3)
-and the [migration guide](./docs/migrating_from_v2).
+and the [migration guide](./cloud/migrating_from_v2).
 
 ## [2.2.0] - 2023-11-09
 

website/blog/2021-10-09-exciting_times.md

@@ -62,7 +62,7 @@ We have also added a lot of minor performance tweaks as well as design tweaks
 and improvements, including a very awesome new **dark mode**!
 
 If you are using `FirebaseCMSApp` (previously `CMSApp`), so FireCMS as a
-standalone app, you will need to update some APIs (see the [Migrating from alpha versions](../docs/1.0.0/migrating_from_alpha_versions)).
+standalone app, you will need to update some APIs.
 
 But, but, but...
 If you need more customisation you can now completely
@@ -84,18 +84,18 @@ behind their respective interfaces. This means you can replace any of those
 parts with your custom implementation!
 
 We have three new types that abstract away the services provided by Firebase:
-- [`AuthDelegate`](/docs/1.0.0/api/types/authdelegate), in charge of handling
+- AuthDelegate, in charge of handling
   the auth operation such as login or sign out, and build the logged-in user.
-- [`DataSource`](/docs/1.0.0/api/interfaces/datasource), in charge of handling data
+- DataSource, in charge of handling data
   operation (fetch, listen, save, delete).
-- [`StorageSource`](/docs/1.0.0/api/interfaces/storagesource), in charge of dealing
+- StorageSource, in charge of dealing
   with file storage operations.
 
 We provide implementation for using Firebase Auth, Firestore and Firebase Storage,
 assigned by default if you use `FirebaseCMSApp`.
 
 This means that you are now able to use FireCMS with any backend, auth or storage
-solution. If you want to go this way, you can check an [example implementation](../docs/1.0.0/custom_cms_app)
+solution. If you want to go this way, you can check an example implementation
 of FireCMS that uses the internal components instead of `FirebaseCMSApp`
 
 :::note How did it go?

website/blog/2024-01-31-beta_launch_3_0.md

@@ -185,7 +185,7 @@ provide support, and a live web app where you can find your projects.
 
 ### How to get started?
 
-Go to [app.firecms.co](http://app.firecms.co/) and create your project.
+Go to [app.firecms.co](https://app.firecms.co/) and create your project.
 
 ### What are you going to build?
 

website/docs/CHANGELOG.md

@@ -375,7 +375,7 @@ const userManagement = useBuildUserManagement({
 
 The first beta release of FireCMS v3.0.0.
 Check all the new features and improvements in the [documentation](./what_is_new_v3)
-and the [migration guide](./docs/migrating_from_v2).
+and the [migration guide](./cloud/migrating_from_v2).
 
 ## [2.2.0] - 2023-11-09
 

website/docs/api_index.md

@@ -1,5 +1,3 @@
 In this section you will find all the possible configurations and types
 related to FireCMS.
 
-For a general overview of the library it's better to start in the [docs](./index.mdx)
-section

website/docs/cloud/cloud_quickstart.mdx

@@ -65,7 +65,7 @@ have already created in the Cloud version... Awesome!
 
 If you want to deploy to FireCMS Cloud your module must export a
 `FireCMSAppConfig` object. You can find more information about this object
-in the [App config section](./cloud/app_config) reference.
+in the [App config section](./app_config) reference.
 
 :::important
 Vite uses the default url `http://127.0.0.1:5173` for the development server

website/docs/cloud/index.mdx

@@ -39,5 +39,5 @@ Just sign up and start using it!
 <DocsCloudCTA/>
 
 After you have created your FireCMS project, you can either use it directly or [customize it
-by uploading your own code](./cloud/quickstart).
+by uploading your own code](./quickstart).
 

website/docs/index.mdx

@@ -26,7 +26,7 @@ FireCMS imposes **no data structure restrictions**, allowing seamless integratio
 FireCMS **3.0** is the latest version of FireCMS. It can be used in different ways:
 - As a managed service in the Cloud: [**FireCMS Cloud**](https://app.firecms.co). In this version you can create and
 manage your content in a user-friendly interface, and use it as a no-code tool, or extend its functionality with code.
-- You also have self-hosted options in the [**PRO**](/docs/pro) plan and community plan. In this versions, you need to deploy FireCMS to
+- You also have self-hosted options in the [**PRO**](/pro) plan and community plan. In this versions, you need to deploy FireCMS to
 your server, and you have full control over the code, with many customization options.
 
 ### Navigation
@@ -43,5 +43,5 @@ for more information.
 
 You have two main ways of creating the top-level views in FireCMS, either creating **entity collections** that get
 mapped to CMS views, or create your own top-level **React views**:
-- Check all the possible configurations for defining [**collections**](./collections/collections)
+- Check all the possible configurations for defining [**collections**](./collections)
 - Otherwise, you can define your own [**custom top-level views**](./custom_top_level_views.mdx).

website/docs/pro/entity_history.mdx

@@ -29,10 +29,15 @@ import React from "react";
 import { FirebaseCMSApp } from "@firecms/core";
 import { useEntityHistoryPlugin } from "@firecms/entity_history";
 
-// Basic setup with default options
-const entityHistoryPlugin = useEntityHistoryPlugin();
 
 export default function App() {
+
+    // Basic setup with default options
+    const entityHistoryPlugin = useEntityHistoryPlugin({
+        // This can be overridden by setting `history: false` in a specific collection
+        defaultEnabled: true
+    });
+
     return <FirebaseCMSApp
         name={"My Online Shop"}
         plugins={[entityHistoryPlugin]}
@@ -64,34 +69,34 @@ const productsCollection = buildCollection({
 
 ## Advanced Configuration
 
-You can customize the plugin's behavior by passing props to `useEntityHistoryPlugin`:
+You can customize the plugin's behavior by passing props to `useEntityHistoryPlugin`.
+If you are using the user management plugin, you can provide a function to resolve user details from a UID.
+You can also pass your own custom `getUser` function to fetch user details.
 
 ```tsx
 import { useEntityHistoryPlugin } from "@firecms/entity_history";
 import { User } from "@firecms/core";
 
-// Example function to fetch user details
-const myGetUserFunction = (uid: string): User | null => {
-    // Replace with your actual user fetching logic
-    if (uid === "user123") {
-        return {
-            uid: "user123",
-            displayName: "John Doe",
-            email: "john.doe@example.com",
-            photoURL: "url_to_photo"
-        } as User;
-    }
-    return null;
-};
-
-const entityHistoryPlugin = useEntityHistoryPlugin({
-    // Enable history for all collections by default
-    // This can be overridden by setting `history: false` in a specific collection
-    defaultEnabled: true,
-
-    // Provide a function to resolve user details from a UID
-    getUser: myGetUserFunction
-});
+export function App() {
+
+    // ...
+
+    const userManagement = useBuildUserManagement({
+        dataSourceDelegate: firestoreDelegate,
+        authController: authController
+    });
+
+    const entityHistoryPlugin = useEntityHistoryPlugin({
+        // Enable history for all collections by default
+        // This can be overridden by setting `history: false` in a specific collection
+        defaultEnabled: true,
+
+        // Provide a function to resolve user details from a UID
+        getUser: userManagement.getUser
+    });
+
+    // ...
+}
 ```
 
 ## Configuration Options

website/docs/pro/sample_pro.mdx

@@ -285,4 +285,4 @@ the routing, but you are free to replace it with your own routing system.
 ```
 
 
-Find more details about the main components in the [Main Components](main_components) section.
+Find more details about the main components in the [Main Components](../self/main_components) section.