Dragonfly Cloud and community docs have the same style and it's confusing

[romange]

Whether we inspect a page for Dragonfly Cloud or other sections here https://www.dragonflydb.io/docs/
it looks the same so it may be confusing if a user lands on a community page when searching for cloud questions or vice versa.

We should make both properties distinguishable via differrent style and color themes

[Niennienzz]

We might need some design for this.

@AnzeKop Is it configurable in Docusaurus such that different sections have different "global" CSS?

[AnzeKop]

I don't think it is, it might be worth it to start thinking about moving the docs over to the CMS to have more granular control over this and also unify the header and footer styles

[romange]

We won't migrate docs.

Gemini says there are two options to achieve it:

1. Swizzle the DocPage Component (Recommended for Doc-Specific Styling)
2. Multi-Instance Docs Plugin

// docusaurus.config.js
export default {
  // ...
  plugins: [
    [
      '@docusaurus/plugin-content-docs',
      {
        id: 'default', // The default docs instance
        path: 'docs', // Path to your main docs folder
        routeBasePath: 'docs',
        sidebarPath: './sidebars.js',
        // ... other options for default docs
      },
    ],
    [
      '@docusaurus/plugin-content-docs',
      {
        id: 'cloud', // A unique ID for your cloud docs
        path: 'cloud-docs', // Path to your cloud docs folder (e.g., docs/cloud)
        routeBasePath: 'docs/cloud', // The URL path for cloud docs
        sidebarPath: './sidebarsCloud.js', // Separate sidebar for cloud docs
        // You can also add a `className` to the `versions` config if you want a top-level class for these docs
        versions: {
          current: {
            className: 'cloud-docs-section', // This class will be added to the html element
          },
        },
        // ... other options for cloud docs
      },
    ],
  ],
  // ...
};

is it correct @AnzeKop ?

[AnzeKop]

You would want the entire theme to shift to light when we go on the cloud tab?

I think the multi-instance doc plugin would work but not sure if we can then have the navigation of both be present at the same time

[romange]

what do you mean by navigation of both?
in general I am also open to split the cloud docs from the "community" docs and have a separate repo for each,

and reorganise the navigation header differently, so that "docs" would go under community,
and we would have a new "Cloud" drop-down, with its own "Docs" underneath, the "pricing" will also go under the "cloud" menu.

Docs content must stay in github, be open and accessible to engineers.

@ashotland @odedponcz @worldsoup thoughts?

[AnzeKop]

If the issue is the UI we can keep the docs content as md files and just do a custom UI instead of docasaurus.

For the navigation if we use the multi-instance plugin I'm not sure how it would then work with the auto-generated sidebar if it would only take the md files pertaining to that instance or if there is a way to solve for that. I haven't worked with docasaurus too much so I'd need to test and see

[romange]

I understand. I do think that ideally we wound want to have separate silos for cloud docs and community docs, and what we have now was an easy way to move forward in order to add cloud related docs. right @ashotland ?

[ashotland]

I think we should follow others e.g.
https://grafana.com/docs/grafana-cloud/
https://redis.io/docs/latest/operate/rc/

[odedponcz]

We do not need to change the technology just because we would like things to be more clear.

1. We should have 3 top level entities: Cloud, Community, K8s
2. Default and top should be cloud
3. Add an indication on every page if its a Cloud, Community, K8s with a visible icon at the top of the page.

[romange]

ok, so have a distinct colored PATCH in EACH document
like this

@AnzeKop is it something we can do cross board?

[AnzeKop]

so same as redis has 3 top level items we do a similar thing and then just make sure we have the tag in place for if its a cloud/k8/community product?

I can see if its also possible to do an automatic theme shift if they are on the k8/cloud docs, would be a cool effect

Also is there any reason we aren't on docasarus 3? https://docusaurus.io/docs/migration/v3

[romange]

I will start working with agents for this repo @Niennienzz @AnzeKop as I see it's not being actively maintained.