handbook
handbook copied to clipboard
jitsi
Not an issue, but a feature!
The feature is to add a multi-language selection option on the jitsi-handbooks page, very similar to the way docusaurus's website. Docusaurus Website: https://docusaurus.io/
Image for reference:
It should be possible indeed, but nobody has made the effort to start adding a second language.
If you are willing to start adding one, that would be most welcome.
It should be possible indeed, but nobody has made the effort to start adding a second language.
If you are willing to start adding one, that would be most welcome.
I was just watching a tutorial for this, and there the person was adding Italiano as a second language which is I guess not yet added in Docusaurus's API but I believe there are some other foreign languages that are already present in the API so I will try to add the pre-existing ones first and then will try to add my national language( Hindi ).
@saghul Hi, can you please help me with the error I am facing here? The image below shows the error that I am facing. This error comes when I am running the command "npm run build". I am trying to run this command because earlier when I requested a PR( PR: #411 ) there I faced the issue of " All checks have failed", and this error is the reason why I faced the " All checks have failed" problem.
After trying multiple times, I made another folder and cloned the handbook repo, then also without editing any file, I ran "npm i" and after doing this I did "npm run build" then also the same above error is thrown at me. I even tried changing the version of docusaurus from 2.1.0 to 2.2.0 the also same error is shown to me. Help me, please.
The Environment I am using: MacBook m1 air, macOS 13.0.1 node version 16.19.0
Seems related to the internationalization changes, because some links are broken.
Sorry I have no experience with it so I don't know how to fix it :-/
hey is that issue is still open, I can try of adding muitple languages,
We are still considering adding multi la gauge support or not.
Plus, there a pr open already.
can't maintainers review that pr and give judgemental, I don't want to create clash/conflict of developers working on same issue