I'm making a Docusaurus site with two separate sets of documentation. One set of documents is for our website content creators and the other is for site development documentation.
I followed instructions on the Docusaurus site for implementing Docs Multi-instance: https://docusaurus.io/docs/docs-multi-instance
I already have a /docs folder. I created a new /dev folder on the same level. Screenshot: two documentation directories
I installed the docs plugin according to instructions here: https://docusaurus.io/docs/api/plugins/#docusaurus/plugin-content-docs
I have the original docs instance from preset-classic. Screenshot: preset-classic code
I added a line for the additional docs by adding plugin info to the docusaurus.config.js file. Screenshot: plugin code
Both /docs and /dev have a markdown file called intro.md. The site loads but the two nav items both point to the intro.md file that's in /docs.
I changed the name of the intro.md file in /dev to devintro.md. After that change, I don't get an error in terminal, but the content isn't visible on the docusaurus site anymore. I just see the favicon and nothing else.
Here's a screenshot from inspector: inspector view of nav links
Has anyone else successfully gotten a multidocs instance running in Docusaurus? How can I have my nav items point to the landing page within each directory? Am I missing a step?
Related
From node_modules\docusaurus\lib\publish-gh-pages.js:
const websiteURL =
GITHUB_HOST === GITHUB_DOMAIN
? `https://${ORGANIZATION_NAME}.github.io/${PROJECT_NAME}` // gh-pages hosted repo
: `https://${GITHUB_HOST}/pages/${ORGANIZATION_NAME}/${PROJECT_NAME}`; // GitHub enterprise hosting.
My question is... why is the documentation being uploaded to a subdirectory? What if I wanted it uploaded to the root directory? How might I do that?
The front page of a docusaurus v1 website is more of a splash page with sections like "feature callouts", etc. Overall, it seems best suited to be a root page as it appears to be for https://hermesengine.dev/ , https://hydra.cc/ and pretty much every other facebook open source project.
Also, the HTML that docusaurus generates has <link rel="stylesheet" href="/css/main.css"/> in it, which works great when you're building your site with npm run start (which results in the files living in web root), but not so much when using publish-gh-pages.js since main.css then lives at /${PROJECT_NAME}/css/main.css.
So how can I do the same - make it so my docusaurus built website gets uploaded to web root instead of a subdirectory?
The repo was that the repo wasn't named project_name.github.io - it was named docs. That this would result in docusaurus doing the build process is evident from the build script BUT apparently github.com itself will default to a subdirectory for github.io unless your repo name is project_name.github.io. This can be seen by scrolling to the bottom of the page that Settings brings up.
how i can add a vue template like this :
vue-paper-dashboard
in my vue cli project
i want just add it in specify route like :
/admin/
in documentaion just write about run demo
but its folder like a complete project and i dont know how i can add it to specify part of my project
If I understood you correctly what you can do to is right click on the vue-pager-dashboard and inspect so the developer tools shows up. When the developer tools shows up click on the sources like the picture below
After that you will see webpack you can go in there and see how they made their files and designed the dashboard so you can from there work your way and copy the important parts that you want in your project. In the (. dot) folder you can see the routes plugins etc.. and in the src folder you can see pages components well in both folders you can see the components. So this is the way you can do it but if it isn't as you asked or didn't help you out be more specific with your question.
I'm new to Pelican and am trying to modify the default theme (called simple) so suit my tastes. So I started by trying to get rid of the footer that says "Proudly powered by Pelican, which takes great advantage of Python".
So I looked things up online and went through the following steps:
Uncommented the footer section from the file ./venv/lib/python3.6/site-packages/pelican/themes/simple/templates/base.html.
Ran the command pelican content -s pelicanconf.py -t venv/lib/python3.6/site-packages/pelican/themes/simple
Tried make html as well
Viewed the site using pelican --autoreload --listen and reloaded the page
Also viewed the site using make devserver abd reloaded the page.
However, the footer stays. Yes, I can just hide it through CSS, but that's not my goal; my goal is to learn how to modify Pelican themes.
Not sure what else I need to do!
I have created a vue-cli project.
After I run build it, it works in the http-server. I'd like to push it to my github.io, and I build it as what I found on the Internet. However, at https://tsunaou.github.io/VueJiaogaiFront/dist/index.html I can only see a blank page and it show like this,nothing in the div whose id is app.
enter image description here
It looks like you're building Github Pages from master. To make this work you'll either need to build into a directory called docs (instead of dist) and change the settings on your repo to point to docs, or move the built files up to the project root.
It's in the documentation:
deployment to github pages
We are working on a project which involves custom branding. We are using a tool called Splunk. We need to add a label along with Splunk logo. We investigated with firebug and we could see that there is a references to that splunk logo in common.js and common.min.js file. We are using splunk version6.2. We located the common.js file in the below path.
(Path :home dir\Splunk\share\splunk\search_mrsparkle\exposed\js\build\bundles\common.js ). When we changed the logo in common.js file, we were able to see the changes, refelected.
So we tried to searched for the common.min.js file, we were not able to locate that file.
Can some one throw some light on where this common.min.js file will be located. If we are able to locate it, we will be able to make our branding changes.
From the Firebug, we are able to see that that common.min.js file is located in the http://domainname/static/#245427/js path. We are not able to locate that file in our server.
Any help on this is appreciated.