on mobile browser navigation bar not easily visible

[Oxygenxx]

i am using docs only mode with multi-docs-plugin (@docusaurus/plugin-content-docs)
that's why have removed blog directory and default homepage

i have two docs. example :

1. linux_docs
2. devops_docs

the only reason to use multi-docs-plugin is : i want both docs should have it's on separate sidebar.
so when i click on "linux_docs" on the navigation bar only the content of it should be visible not other. same goes with devops_docs

it's working perfectly on the desktop browser BUT
but on the mobile browser navigation bar is not easily visible in the front. it's hidden two street back.
you click on ☰ (hamburger menu) then click on (<-- back to main menu) then you can access the navigation bar. also putting navigation links on the footer is not good idea.

i have two docs at this link
mywebsite.com/linux_docs with routeBasePath: '/' this link will become website.com/
mywebsite.com/devops_docs

so if i will send someone link of mywebsite.com/ on mobile browser. it would be difficult to discover the navigation bar where other docs links are present

the solution i can think of is to just use single-docs-plugin and both docs would be visible on the same sidebar as regular docs and remove the need to navigation bar but it doesn't feel quite right way

is it possible to show navigation bar first on the sidebar and when i click on one docs then sidebar of that docs would be visible. this way navigation bar will come in visibility first

i don't necessarily need multi-docs-plugin i just need two different docs with their own separate sidebar and navigation bar should be visible in front at first on mobile

what would be the best way to configure this. i would really appreciate your willingness to help or any inside possible..

how i configured multi-docs plugin
i replaced docs/ directory with projects/ directory
projects -----------------------

├── linux
│   ├── bashrc.md
│   ├── intro.md
│   ├── kitty.md
│   └── zshrc.md
└── devops
    ├── docker
    │   └── mydocker.md
    ├── git
    │   └── mygit.md
    ├── intro.md
    └── linux
        └── mylinux.md

docusaurus.config.js ---------------------------------

  presets: [
    [
      'classic',
      /** @type {import('@docusaurus/preset-classic').Options} */
      ({
        docs: {
          path: 'projects/linux',
	  routeBasePath: '/',
          sidebarPath: './sidebars.js',
        },
      }),
    ],
  ],


plugins: [
    [
      '@docusaurus/plugin-content-docs',
      {
        id: 'devopsPluginId',
        path: 'projects/devops',
        routeBasePath: 'devops',
        sidebarPath: require.resolve('./sidebars.js'),
      },
    ],
  ],

 navbar: {
        title: 'My Site',
        logo: {
          alt: 'My Site Logo',
          src: 'img/logo.svg',
        },
        items: [
          {
            type: 'docSidebar',
            sidebarId: 'tutorialSidebar',
            position: 'left',
            label: 'Linux',
          },
	  {
            type: 'docSidebar',
            sidebarId: 'devopsSidebar',
            position: 'left',
            label: 'DevOps',
            docsPluginId: 'devopsPluginId',
          },
        ],
      },

sidebar.js ---------------------------------------

const sidebars = {
  tutorialSidebar: [{type: 'autogenerated', dirName: '.'}],
    devopsSidebar: [{type: 'autogenerated', dirName: '.'}],
};
export default sidebars;

[slorber]

the only reason to use multi-docs-plugin is : i want both docs should have it's on separate sidebar.

You can have one docs plugin instance and still have separate sidebars: https://docusaurus.io/docs/sidebar/multiple-sidebars

is it possible to show navigation bar first on the sidebar and when i click on one docs then sidebar of that docs would be visible. this way navigation bar will come in visibility first

We do display the navigation bar first:

If you first see a sidebar, this is because you are on a docs, so in that case we display first that specific doc sidebar

---

Remember that you can swizzle and override any theme component you want.
We can't expose every possible UX through config options, and sometimes you need to code.

It's hard to parse your wall of text, and would be better to show mockups or screenshots of the problem and the expected UX.

It would be even better of you implemented the UX you want by swizzling to show us exactly how it should behave. An example is worth a thousand words.