You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 12, 2024. It is now read-only.
I am thinking it could be useful to host all of the translations within the hydra-docs repo (or possibly somewhere else), and then load them directly as raw json from github, such as in the i18next extended example: https://jsfiddle.net/jamuhl/ferfywyf/525/
Pros:
possible to edit text and translations without rebuilding and recompiling editor and website, as it would dynamically load each time
could possibly be easier to preview translations within various contexts.. i.e. using a url parameter pointing to a specific translation file could make it possible to load the page using that translation file
Cons:
might be a little bit slower?
in some cases might be harder to preview in context(?)
The text was updated successfully, but these errors were encountered:
would it be like checking the URI and if it's localhost, load json locally and otherwise (i.e., hydra.ojack.xyz), load from github?
but it might not work for hydra-docs because docsify has to load markdown files. maybe - we can point docsify source to raw github and docsify will load files from there... I need to test it
Maybe for docsify it is okay to keep it as is, I was more thinking about storing the json translations for hydra-functions and the web editor here, as it is much more complicated to build and run those repos (requires compilation, etc).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am thinking it could be useful to host all of the translations within the hydra-docs repo (or possibly somewhere else), and then load them directly as raw json from github, such as in the i18next extended example: https://jsfiddle.net/jamuhl/ferfywyf/525/
Pros:
Cons:
The text was updated successfully, but these errors were encountered: