![]() I’m avoiding/postponing going down the rabbit hole with obsidian as the graphing of all my txt notes looks scary! Like a lot of my excited posts, I’ve only been using Zettlr for a week (it has an inbuilt pomodoro timer ppl! and it reads \LaTeX, but that’s a me thing). They proport to be knowledge management tools and my experience so far is positive: currently swishing through my files trying to make sense of why I have so many ideas, and so few outputs? This documentation is licensed via the GNU GPL v3 license.Has anybody else here had much experience with Zettlr and/or Obsidian? config/.yml-configuration file as appropriate. assets/index.html-file and add your language to the bottom (simply copy one of the existing list items, the changes necessary should be self-explanatory). ![]() This is important so that changes to the master file are propagated to all languages, keeping it DRY. Inside this directory, create an assets-subdirectory and create a symbolic link to the. ![]() Create a new directory corresponding to the same ISO-code in.es for Spanish, fr for French, and so on). Rename it to the corresponding ISO-code (e.g. Copy any of the configuration files in.Want to add a language? Perfect, here's how you do it: yml-configuration file located in the config-directory. It will scan the docs-directory and run the corresponding. The build.sh-scripts builds the full documentation. If you omit this, it will simply spin up the English language server. Simply run:Īnd replace "en" with an existing language code to spin up the development server. The serve.sh-script serves a specific language for testing. Most of the default commands won't work with our setup, so please use the custom scripts: serve.sh ![]() Please follow the instructions by the creators of MkDocs on how to set up the software on your computer. MkDocs is a comprehensive library that allows for easy building of whole documentations. To locally test how your changes work out, you'll need to install MkDocs. gitignore file will not commit this directory. You can create a resources directory on the root level to store additional files that you may need, as the. The rest of the files are independent and unique for each language. Inside these, you will find one assets-folder, which contains a symbolic link to the top-level assets's app.css-file. Inside the docs-subdirectory, you'll find all languages inside ISO-coded directories. If you have an idea on how to structure the documentation, please start a thread in the discussions tab of the main repository or join the discord server. New pages in our documentation will require some structural adjustments, which you need to discuss beforehand.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |