├── static ├── .nojekyll ├── img │ ├── favicon.ico │ ├── favicon-32x32.png │ └── favicon-192x192.png └── en │ └── img │ ├── api_flowchart.png │ ├── home_screenshot.png │ ├── install-extension.png │ ├── update-extension.png │ ├── config-repositories.png │ ├── uninstall-extension.png │ └── extension-manager-queue.png ├── docs ├── extend │ ├── post-types.md │ ├── slugging.md │ ├── update-2_x.md │ ├── assets.md │ └── theme.md ├── assets │ ├── home_screenshot.png │ ├── install-extension.png │ ├── update-extension.png │ ├── config-repositories.png │ ├── global_search_modal.png │ ├── uninstall-extension.png │ ├── extension-manager-page.png │ ├── extension-manager-queue.png │ └── gambit_autocomplete_dropdown.png ├── internal │ └── README.md ├── releases.md ├── extenders.md ├── queue.md ├── admin.md └── contributing-docs-translations.md ├── versions.json ├── versioned_docs └── version-1.x │ ├── extend │ ├── post-types.md │ ├── slugging.md │ ├── cli.md │ ├── assets.md │ └── theme.md │ ├── internal │ └── README.md │ ├── releases.md │ ├── extenders.md │ ├── admin.md │ └── themes.md ├── i18n ├── zh │ ├── docusaurus-plugin-content-docs │ │ ├── current │ │ │ ├── extend │ │ │ │ ├── post-types.md │ │ │ │ ├── slugging.md │ │ │ │ ├── cli.md │ │ │ │ ├── assets.md │ │ │ │ ├── theme.md │ │ │ │ └── README.md │ │ │ ├── appearance.md │ │ │ ├── permissions.md │ │ │ ├── tags.md │ │ │ ├── internal │ │ │ │ ├── README.md │ │ │ │ ├── merging-policy.md │ │ │ │ └── merging.md │ │ │ ├── releases.md │ │ │ ├── admin.md │ │ │ ├── themes.md │ │ │ ├── mail.md │ │ │ ├── contributing-docs-translations.md │ │ │ ├── languages.md │ │ │ ├── extenders.md │ │ │ ├── config.md │ │ │ ├── bugs.md │ │ │ ├── faq.md │ │ │ └── scheduler.md │ │ ├── version-1.x │ │ │ ├── extend │ │ │ │ ├── post-types.md │ │ │ │ ├── slugging.md │ │ │ │ ├── cli.md │ │ │ │ ├── assets.md │ │ │ │ ├── theme.md │ │ │ │ └── README.md │ │ │ ├── tags.md │ │ │ ├── appearance.md │ │ │ ├── permissions.md │ │ │ ├── internal │ │ │ │ ├── README.md │ │ │ │ ├── merging-policy.md │ │ │ │ └── merging.md │ │ │ ├── releases.md │ │ │ ├── admin.md │ │ │ ├── themes.md │ │ │ ├── mail.md │ │ │ ├── contributing-docs-translations.md │ │ │ ├── languages.md │ │ │ ├── extenders.md │ │ │ ├── config.md │ │ │ ├── bugs.md │ │ │ ├── faq.md │ │ │ └── scheduler.md │ │ └── current.json │ ├── docusaurus-theme-classic │ │ ├── footer.json │ │ └── navbar.json │ └── code.json ├── vi │ ├── docusaurus-plugin-content-docs │ │ ├── current │ │ │ ├── extend │ │ │ │ ├── post-types.md │ │ │ │ ├── slugging.md │ │ │ │ ├── cli.md │ │ │ │ ├── assets.md │ │ │ │ └── theme.md │ │ │ ├── internal │ │ │ │ └── README.md │ │ │ ├── releases.md │ │ │ ├── extenders.md │ │ │ ├── admin.md │ │ │ ├── config.md │ │ │ └── themes.md │ │ ├── version-1.x │ │ │ ├── extend │ │ │ │ ├── post-types.md │ │ │ │ ├── slugging.md │ │ │ │ ├── cli.md │ │ │ │ ├── assets.md │ │ │ │ └── theme.md │ │ │ ├── internal │ │ │ │ └── README.md │ │ │ ├── releases.md │ │ │ ├── extenders.md │ │ │ ├── admin.md │ │ │ ├── config.md │ │ │ └── themes.md │ │ └── current.json │ ├── docusaurus-theme-classic │ │ ├── footer.json │ │ └── navbar.json │ └── code.json ├── de │ ├── docusaurus-plugin-content-docs │ │ ├── current │ │ │ ├── extend │ │ │ │ ├── post-types.md │ │ │ │ ├── slugging.md │ │ │ │ ├── cli.md │ │ │ │ ├── assets.md │ │ │ │ └── theme.md │ │ │ ├── releases.md │ │ │ ├── internal │ │ │ │ └── README.md │ │ │ ├── extenders.md │ │ │ └── admin.md │ │ └── version-1.x │ │ │ ├── extend │ │ │ ├── post-types.md │ │ │ ├── slugging.md │ │ │ ├── cli.md │ │ │ ├── assets.md │ │ │ └── theme.md │ │ │ ├── releases.md │ │ │ ├── internal │ │ │ └── README.md │ │ │ ├── extenders.md │ │ │ └── admin.md │ ├── docusaurus-theme-classic │ │ ├── footer.json │ │ └── navbar.json │ └── code.json ├── es │ ├── docusaurus-plugin-content-docs │ │ ├── current │ │ │ ├── extend │ │ │ │ ├── post-types.md │ │ │ │ ├── slugging.md │ │ │ │ ├── cli.md │ │ │ │ ├── assets.md │ │ │ │ ├── theme.md │ │ │ │ └── translate.md │ │ │ ├── internal │ │ │ │ └── README.md │ │ │ ├── releases.md │ │ │ ├── extenders.md │ │ │ ├── admin.md │ │ │ ├── themes.md │ │ │ └── current.json │ │ ├── version-1.x │ │ │ ├── extend │ │ │ │ ├── post-types.md │ │ │ │ ├── slugging.md │ │ │ │ ├── cli.md │ │ │ │ ├── assets.md │ │ │ │ ├── theme.md │ │ │ │ └── translate.md │ │ │ ├── internal │ │ │ │ └── README.md │ │ │ ├── releases.md │ │ │ ├── extenders.md │ │ │ ├── admin.md │ │ │ ├── themes.md │ │ │ └── current.json │ │ └── current.json │ ├── docusaurus-theme-classic │ │ ├── footer.json │ │ └── navbar.json │ └── code.json ├── it │ ├── docusaurus-plugin-content-docs │ │ ├── current │ │ │ ├── extend │ │ │ │ ├── post-types.md │ │ │ │ ├── slugging.md │ │ │ │ ├── cli.md │ │ │ │ ├── theme.md │ │ │ │ ├── assets.md │ │ │ │ └── translate.md │ │ │ ├── internal │ │ │ │ └── README.md │ │ │ ├── releases.md │ │ │ ├── extenders.md │ │ │ ├── admin.md │ │ │ └── current.json │ │ ├── version-1.x │ │ │ ├── extend │ │ │ │ ├── post-types.md │ │ │ │ ├── slugging.md │ │ │ │ ├── cli.md │ │ │ │ ├── theme.md │ │ │ │ ├── assets.md │ │ │ │ └── translate.md │ │ │ ├── internal │ │ │ │ └── README.md │ │ │ ├── releases.md │ │ │ ├── extenders.md │ │ │ ├── admin.md │ │ │ └── current.json │ │ └── current.json │ ├── docusaurus-theme-classic │ │ ├── footer.json │ │ └── navbar.json │ └── code.json ├── tr │ ├── docusaurus-plugin-content-docs │ │ ├── current │ │ │ ├── extend │ │ │ │ ├── post-types.md │ │ │ │ ├── slugging.md │ │ │ │ ├── data.md │ │ │ │ ├── translate.md │ │ │ │ ├── cli.md │ │ │ │ ├── assets.md │ │ │ │ └── theme.md │ │ │ ├── releases.md │ │ │ ├── internal │ │ │ │ └── README.md │ │ │ ├── extenders.md │ │ │ ├── admin.md │ │ │ ├── themes.md │ │ │ └── current.json │ │ ├── version-1.x │ │ │ ├── extend │ │ │ │ ├── post-types.md │ │ │ │ ├── slugging.md │ │ │ │ ├── data.md │ │ │ │ ├── translate.md │ │ │ │ ├── cli.md │ │ │ │ ├── assets.md │ │ │ │ └── theme.md │ │ │ ├── internal │ │ │ │ └── README.md │ │ │ ├── releases.md │ │ │ ├── extenders.md │ │ │ ├── admin.md │ │ │ ├── themes.md │ │ │ └── current.json │ │ └── current.json │ ├── docusaurus-theme-classic │ │ ├── footer.json │ │ └── navbar.json │ └── code.json └── en │ ├── docusaurus-theme-classic │ ├── footer.json │ └── navbar.json │ ├── code.json │ └── docusaurus-plugin-content-docs │ └── current.json ├── babel.config.js ├── deploy.sh ├── src └── assets │ ├── cube.svg │ ├── arrow-down-tray.svg │ ├── adjustments-vertical.svg │ ├── book-open.svg │ ├── light-bulb.svg │ ├── document-arrow-up.svg │ ├── lifebuoy.svg │ └── cog-6-tooth.svg ├── .github ├── PULL_REQUEST_TEMPLATE.md └── workflows │ └── deploy.yml ├── .editorconfig ├── .gitignore ├── crowdin.yml ├── README.md ├── srxDefault.xml ├── package.json └── LICENSE /static/.nojekyll: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /docs/extend/post-types.md: -------------------------------------------------------------------------------- 1 | # Post Types -------------------------------------------------------------------------------- /versions.json: -------------------------------------------------------------------------------- 1 | [ 2 | "1.x" 3 | ] 4 | -------------------------------------------------------------------------------- /docs/extend/slugging.md: -------------------------------------------------------------------------------- 1 | # Model Slugging 2 | -------------------------------------------------------------------------------- /versioned_docs/version-1.x/extend/post-types.md: -------------------------------------------------------------------------------- 1 | # Post Types -------------------------------------------------------------------------------- /versioned_docs/version-1.x/extend/slugging.md: -------------------------------------------------------------------------------- 1 | # Model Slugging 2 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/current/extend/post-types.md: -------------------------------------------------------------------------------- 1 | # 帖子类型 -------------------------------------------------------------------------------- /i18n/vi/docusaurus-plugin-content-docs/current/extend/post-types.md: -------------------------------------------------------------------------------- 1 | # Kiểu Post -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/version-1.x/extend/post-types.md: -------------------------------------------------------------------------------- 1 | # 帖子类型 -------------------------------------------------------------------------------- /i18n/de/docusaurus-plugin-content-docs/current/extend/post-types.md: -------------------------------------------------------------------------------- 1 | # Post Types -------------------------------------------------------------------------------- /i18n/de/docusaurus-plugin-content-docs/version-1.x/extend/post-types.md: -------------------------------------------------------------------------------- 1 | # Post Types -------------------------------------------------------------------------------- /i18n/es/docusaurus-plugin-content-docs/current/extend/post-types.md: -------------------------------------------------------------------------------- 1 | # Post Types -------------------------------------------------------------------------------- /i18n/es/docusaurus-plugin-content-docs/version-1.x/extend/post-types.md: -------------------------------------------------------------------------------- 1 | # Post Types -------------------------------------------------------------------------------- /i18n/it/docusaurus-plugin-content-docs/current/extend/post-types.md: -------------------------------------------------------------------------------- 1 | # Tipi di post -------------------------------------------------------------------------------- /i18n/vi/docusaurus-plugin-content-docs/version-1.x/extend/post-types.md: -------------------------------------------------------------------------------- 1 | # Kiểu Post -------------------------------------------------------------------------------- /i18n/de/docusaurus-plugin-content-docs/current/extend/slugging.md: -------------------------------------------------------------------------------- 1 | # Model Slugging 2 | -------------------------------------------------------------------------------- /i18n/es/docusaurus-plugin-content-docs/current/extend/slugging.md: -------------------------------------------------------------------------------- 1 | # Model Slugging 2 | -------------------------------------------------------------------------------- /i18n/it/docusaurus-plugin-content-docs/current/extend/slugging.md: -------------------------------------------------------------------------------- 1 | # Modello Slugging 2 | -------------------------------------------------------------------------------- /i18n/it/docusaurus-plugin-content-docs/version-1.x/extend/post-types.md: -------------------------------------------------------------------------------- 1 | # Tipi di post -------------------------------------------------------------------------------- /i18n/tr/docusaurus-plugin-content-docs/current/extend/post-types.md: -------------------------------------------------------------------------------- 1 | # Gönderi Türleri -------------------------------------------------------------------------------- /i18n/tr/docusaurus-plugin-content-docs/current/extend/slugging.md: -------------------------------------------------------------------------------- 1 | # Model Yavaşlatma 2 | -------------------------------------------------------------------------------- /i18n/tr/docusaurus-plugin-content-docs/version-1.x/extend/post-types.md: -------------------------------------------------------------------------------- 1 | # Gönderi Türleri -------------------------------------------------------------------------------- /i18n/vi/docusaurus-plugin-content-docs/current/extend/slugging.md: -------------------------------------------------------------------------------- 1 | # Model Slugging 2 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/current/extend/slugging.md: -------------------------------------------------------------------------------- 1 | # Model Slugging 2 | -------------------------------------------------------------------------------- /i18n/de/docusaurus-plugin-content-docs/version-1.x/extend/slugging.md: -------------------------------------------------------------------------------- 1 | # Model Slugging 2 | -------------------------------------------------------------------------------- /i18n/es/docusaurus-plugin-content-docs/version-1.x/extend/slugging.md: -------------------------------------------------------------------------------- 1 | # Model Slugging 2 | -------------------------------------------------------------------------------- /i18n/it/docusaurus-plugin-content-docs/version-1.x/extend/slugging.md: -------------------------------------------------------------------------------- 1 | # Modello Slugging 2 | -------------------------------------------------------------------------------- /i18n/tr/docusaurus-plugin-content-docs/version-1.x/extend/slugging.md: -------------------------------------------------------------------------------- 1 | # Model Yavaşlatma 2 | -------------------------------------------------------------------------------- /i18n/vi/docusaurus-plugin-content-docs/version-1.x/extend/slugging.md: -------------------------------------------------------------------------------- 1 | # Model Slugging 2 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/version-1.x/extend/slugging.md: -------------------------------------------------------------------------------- 1 | # Model Slugging 2 | -------------------------------------------------------------------------------- /static/img/favicon.ico: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/flarum/docs/HEAD/static/img/favicon.ico -------------------------------------------------------------------------------- /static/img/favicon-32x32.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/flarum/docs/HEAD/static/img/favicon-32x32.png -------------------------------------------------------------------------------- /static/img/favicon-192x192.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/flarum/docs/HEAD/static/img/favicon-192x192.png -------------------------------------------------------------------------------- /docs/assets/home_screenshot.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/flarum/docs/HEAD/docs/assets/home_screenshot.png -------------------------------------------------------------------------------- /docs/assets/install-extension.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/flarum/docs/HEAD/docs/assets/install-extension.png -------------------------------------------------------------------------------- /docs/assets/update-extension.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/flarum/docs/HEAD/docs/assets/update-extension.png -------------------------------------------------------------------------------- /static/en/img/api_flowchart.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/flarum/docs/HEAD/static/en/img/api_flowchart.png -------------------------------------------------------------------------------- /static/en/img/home_screenshot.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/flarum/docs/HEAD/static/en/img/home_screenshot.png -------------------------------------------------------------------------------- /babel.config.js: -------------------------------------------------------------------------------- 1 | module.exports = { 2 | presets: [require.resolve('@docusaurus/core/lib/babel/preset')], 3 | }; 4 | -------------------------------------------------------------------------------- /docs/assets/config-repositories.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/flarum/docs/HEAD/docs/assets/config-repositories.png -------------------------------------------------------------------------------- /docs/assets/global_search_modal.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/flarum/docs/HEAD/docs/assets/global_search_modal.png -------------------------------------------------------------------------------- /docs/assets/uninstall-extension.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/flarum/docs/HEAD/docs/assets/uninstall-extension.png -------------------------------------------------------------------------------- /static/en/img/install-extension.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/flarum/docs/HEAD/static/en/img/install-extension.png -------------------------------------------------------------------------------- /static/en/img/update-extension.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/flarum/docs/HEAD/static/en/img/update-extension.png -------------------------------------------------------------------------------- /docs/assets/extension-manager-page.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/flarum/docs/HEAD/docs/assets/extension-manager-page.png -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/current/appearance.md: -------------------------------------------------------------------------------- 1 | # 外观 2 | 此页面正在建设中。 3 | This page is under construction. 4 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/current/permissions.md: -------------------------------------------------------------------------------- 1 | # 权限 2 | 此页面正在建设中。 3 | This page is under construction. 4 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/current/tags.md: -------------------------------------------------------------------------------- 1 | # 分类目录和标签 2 | 此页面正在建设中。 3 | This page is under construction. 4 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/version-1.x/tags.md: -------------------------------------------------------------------------------- 1 | # 分类目录和标签 2 | 此页面正在建设中。 3 | This page is under construction. 4 | -------------------------------------------------------------------------------- /static/en/img/config-repositories.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/flarum/docs/HEAD/static/en/img/config-repositories.png -------------------------------------------------------------------------------- /static/en/img/uninstall-extension.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/flarum/docs/HEAD/static/en/img/uninstall-extension.png -------------------------------------------------------------------------------- /docs/assets/extension-manager-queue.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/flarum/docs/HEAD/docs/assets/extension-manager-queue.png -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/version-1.x/appearance.md: -------------------------------------------------------------------------------- 1 | # 外观 2 | 此页面正在建设中。 3 | This page is under construction. 4 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/version-1.x/permissions.md: -------------------------------------------------------------------------------- 1 | # 权限 2 | 此页面正在建设中。 3 | This page is under construction. 4 | -------------------------------------------------------------------------------- /i18n/tr/docusaurus-plugin-content-docs/current/extend/data.md: -------------------------------------------------------------------------------- 1 | # Verilerle Çalışma 2 | 3 | **Yakında Türkçe belgeler eklenecektir.** -------------------------------------------------------------------------------- /i18n/tr/docusaurus-plugin-content-docs/current/extend/translate.md: -------------------------------------------------------------------------------- 1 | # Flarum Çeviri 2 | 3 | **Yakında Türkçe belgeler eklenecektir.** -------------------------------------------------------------------------------- /static/en/img/extension-manager-queue.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/flarum/docs/HEAD/static/en/img/extension-manager-queue.png -------------------------------------------------------------------------------- /docs/assets/gambit_autocomplete_dropdown.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/flarum/docs/HEAD/docs/assets/gambit_autocomplete_dropdown.png -------------------------------------------------------------------------------- /i18n/tr/docusaurus-plugin-content-docs/version-1.x/extend/data.md: -------------------------------------------------------------------------------- 1 | # Verilerle Çalışma 2 | 3 | **Yakında Türkçe belgeler eklenecektir.** -------------------------------------------------------------------------------- /i18n/tr/docusaurus-plugin-content-docs/version-1.x/extend/translate.md: -------------------------------------------------------------------------------- 1 | # Flarum Çeviri 2 | 3 | **Yakında Türkçe belgeler eklenecektir.** -------------------------------------------------------------------------------- /i18n/zh/docusaurus-theme-classic/footer.json: -------------------------------------------------------------------------------- 1 | { 2 | "copyright": { 3 | "message": "版权所有 © 2021 Flarum，此网站使用 Docusaurus 构建。", 4 | "description": "The footer copyright" 5 | } 6 | } -------------------------------------------------------------------------------- /i18n/de/docusaurus-theme-classic/footer.json: -------------------------------------------------------------------------------- 1 | { 2 | "copyright": { 3 | "message": "Copyright © 2021 Flarum. Erstellt mit Docusaurus.", 4 | "description": "The footer copyright" 5 | } 6 | } -------------------------------------------------------------------------------- /i18n/en/docusaurus-theme-classic/footer.json: -------------------------------------------------------------------------------- 1 | { 2 | "copyright": { 3 | "message": "Copyright © 2021 Flarum. Built with Docusaurus.", 4 | "description": "The footer copyright" 5 | } 6 | } -------------------------------------------------------------------------------- /i18n/es/docusaurus-theme-classic/footer.json: -------------------------------------------------------------------------------- 1 | { 2 | "copyright": { 3 | "message": "Copyright © 2021 Flarum. Built with Docusaurus.", 4 | "description": "The footer copyright" 5 | } 6 | } -------------------------------------------------------------------------------- /i18n/it/docusaurus-theme-classic/footer.json: -------------------------------------------------------------------------------- 1 | { 2 | "copyright": { 3 | "message": "Copyright © 2021 Flarum. Built with Docusaurus.", 4 | "description": "The footer copyright" 5 | } 6 | } -------------------------------------------------------------------------------- /i18n/tr/docusaurus-theme-classic/footer.json: -------------------------------------------------------------------------------- 1 | { 2 | "copyright": { 3 | "message": "Telif Hakkı © 2021 Flarum. Docusaurus ile yapılmıştır.", 4 | "description": "The footer copyright" 5 | } 6 | } -------------------------------------------------------------------------------- /i18n/vi/docusaurus-theme-classic/footer.json: -------------------------------------------------------------------------------- 1 | { 2 | "copyright": { 3 | "message": "Bản quyền © 2021 Flarum. Được xây dựng bằng Docusaurus.", 4 | "description": "The footer copyright" 5 | } 6 | } -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/current/internal/README.md: -------------------------------------------------------------------------------- 1 | --- 2 | slug: '/internal' 3 | --- 4 | 5 | # 团队内部文档 6 | 7 | 这是一个全新的部分，我们将在这里发布一些 Flarum 团队内部使用的文档。 我们开始此部分以向我们的社区提供有关 Flarum 如何运作的透明度，与帮助想要为 Flarum 贡献的人们。 -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/version-1.x/internal/README.md: -------------------------------------------------------------------------------- 1 | --- 2 | slug: '/internal' 3 | --- 4 | 5 | # 团队内部文档 6 | 7 | 这是一个全新的部分，我们将在这里发布一些 Flarum 团队内部使用的文档。 我们开始此部分以向我们的社区提供有关 Flarum 如何运作的透明度，与帮助想要为 Flarum 贡献的人们。 -------------------------------------------------------------------------------- /deploy.sh: -------------------------------------------------------------------------------- 1 | #!/bin/sh 2 | 3 | export NVM_DIR="$HOME/.nvm" 4 | [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" # This loads nvm 5 | [ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion" # This loads nvm bash_completion 6 | 7 | git pull 8 | 9 | npm i 10 | 11 | npm run build 12 | -------------------------------------------------------------------------------- /src/assets/cube.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | -------------------------------------------------------------------------------- /.github/PULL_REQUEST_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | 5 | -------------------------------------------------------------------------------- /docs/extend/update-2_x.md: -------------------------------------------------------------------------------- 1 | # Updating For 2.x 2 | 3 | :::tip 4 | 5 | If you need help applying these changes or using new features, please start a discussion on the [community forum](https://discuss.flarum.org/t/extensibility) or [Discord chat](https://flarum.org/discord/). 6 | 7 | ::: 8 | 9 | ## 2.1 Changes 10 | 11 | -------------------------------------------------------------------------------- /.editorconfig: -------------------------------------------------------------------------------- 1 | # Please make sure your IDE takes this editorconfig into consideration 2 | 3 | root = true 4 | 5 | [*] 6 | end_of_line = lf 7 | charset = utf-8 8 | trim_trailing_whitespace = true 9 | insert_final_newline = true 10 | indent_style = space 11 | indent_size = 2 12 | 13 | [*.md] 14 | trim_trailing_whitespace = false -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | # Dependencies 2 | /node_modules 3 | 4 | # Production 5 | /build 6 | 7 | # Generated files 8 | .docusaurus 9 | .cache-loader 10 | 11 | # Misc 12 | .DS_Store 13 | .env.local 14 | .env.development.local 15 | .env.test.local 16 | .env.production.local 17 | 18 | npm-debug.log* 19 | yarn-debug.log* 20 | yarn-error.log* 21 | -------------------------------------------------------------------------------- /docs/internal/README.md: -------------------------------------------------------------------------------- 1 | --- 2 | slug: '/internal' 3 | --- 4 | 5 | # Internal Team Docs 6 | 7 | This is a new documentation section, where we will be posting some docs used internally by the Flarum team. We are starting this section to provide our community with transparency as to how Flarum is run, and to help those hoping to contribute to Flarum. -------------------------------------------------------------------------------- /docs/releases.md: -------------------------------------------------------------------------------- 1 | # Release Notes 2 | 3 | 13 | 14 | Release notes can be found in the [Flarum Community](https://discuss.flarum.org/t/blog?sort=newest). 15 | -------------------------------------------------------------------------------- /src/assets/arrow-down-tray.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/current/releases.md: -------------------------------------------------------------------------------- 1 | # 发布说明 2 | 3 | 4 | 14 | 15 | 发布说明可以在 [Flarum 社区](https://discuss.flarum.org/t/blog?sort=newest) 找到。 16 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/version-1.x/releases.md: -------------------------------------------------------------------------------- 1 | # 发布说明 2 | 3 | 4 | 14 | 15 | 发布说明可以在 [Flarum 社区](https://discuss.flarum.org/t/blog?sort=newest) 找到。 16 | -------------------------------------------------------------------------------- /versioned_docs/version-1.x/internal/README.md: -------------------------------------------------------------------------------- 1 | --- 2 | slug: '/internal' 3 | --- 4 | 5 | # Internal Team Docs 6 | 7 | This is a new documentation section, where we will be posting some docs used internally by the Flarum team. We are starting this section to provide our community with transparency as to how Flarum is run, and to help those hoping to contribute to Flarum. -------------------------------------------------------------------------------- /versioned_docs/version-1.x/releases.md: -------------------------------------------------------------------------------- 1 | # Release Notes 2 | 3 | 13 | 14 | Release notes can be found in the [Flarum Community](https://discuss.flarum.org/t/blog?sort=newest). 15 | -------------------------------------------------------------------------------- /i18n/es/docusaurus-plugin-content-docs/current/internal/README.md: -------------------------------------------------------------------------------- 1 | --- 2 | slug: '/internal' 3 | --- 4 | 5 | # Internal Team Docs 6 | 7 | This is a new documentation section, where we will be posting some docs used internally by the Flarum team. We are starting this section to provide our community with transparency as to how Flarum is run, and to help those hoping to contribute to Flarum. -------------------------------------------------------------------------------- /i18n/it/docusaurus-plugin-content-docs/current/internal/README.md: -------------------------------------------------------------------------------- 1 | --- 2 | slug: '/internal' 3 | --- 4 | 5 | # Internal Team Docs 6 | 7 | This is a new documentation section, where we will be posting some docs used internally by the Flarum team. We are starting this section to provide our community with transparency as to how Flarum is run, and to help those hoping to contribute to Flarum. -------------------------------------------------------------------------------- /i18n/vi/docusaurus-plugin-content-docs/current/internal/README.md: -------------------------------------------------------------------------------- 1 | --- 2 | slug: '/internal' 3 | --- 4 | 5 | # Tài liệu nhóm nội bộ 6 | 7 | Đây là phần tài liệu mới, nơi chúng tôi sẽ đăng một số tài liệu được nhóm Flarum sử dụng nội bộ. Chúng tôi đang bắt đầu phần này để cung cấp cho cộng đồng sự minh bạch về cách thức hoạt động của Flarum và giúp những người hy vọng đóng góp cho Flarum. -------------------------------------------------------------------------------- /i18n/es/docusaurus-plugin-content-docs/version-1.x/internal/README.md: -------------------------------------------------------------------------------- 1 | --- 2 | slug: '/internal' 3 | --- 4 | 5 | # Internal Team Docs 6 | 7 | This is a new documentation section, where we will be posting some docs used internally by the Flarum team. We are starting this section to provide our community with transparency as to how Flarum is run, and to help those hoping to contribute to Flarum. -------------------------------------------------------------------------------- /i18n/it/docusaurus-plugin-content-docs/version-1.x/internal/README.md: -------------------------------------------------------------------------------- 1 | --- 2 | slug: '/internal' 3 | --- 4 | 5 | # Internal Team Docs 6 | 7 | This is a new documentation section, where we will be posting some docs used internally by the Flarum team. We are starting this section to provide our community with transparency as to how Flarum is run, and to help those hoping to contribute to Flarum. -------------------------------------------------------------------------------- /i18n/tr/docusaurus-plugin-content-docs/current/releases.md: -------------------------------------------------------------------------------- 1 | # Sürüm Notları 2 | 3 | 4 | 14 | 15 | Sürüm notları [Flarum Topluluğu](https://discuss.flarum.org/t/blog?sort=newest)'nda bulunabilir. 16 | -------------------------------------------------------------------------------- /i18n/vi/docusaurus-plugin-content-docs/version-1.x/internal/README.md: -------------------------------------------------------------------------------- 1 | --- 2 | slug: '/internal' 3 | --- 4 | 5 | # Tài liệu nhóm nội bộ 6 | 7 | Đây là phần tài liệu mới, nơi chúng tôi sẽ đăng một số tài liệu được nhóm Flarum sử dụng nội bộ. Chúng tôi đang bắt đầu phần này để cung cấp cho cộng đồng sự minh bạch về cách thức hoạt động của Flarum và giúp những người hy vọng đóng góp cho Flarum. -------------------------------------------------------------------------------- /i18n/tr/docusaurus-plugin-content-docs/current/internal/README.md: -------------------------------------------------------------------------------- 1 | --- 2 | slug: '/internal' 3 | --- 4 | 5 | # Internal Team Docs 6 | 7 | Bu, Flarum ekibi tarafından dahili olarak kullanılan bazı belgeleri yayınlayacağımız yeni bir belgeleme bölümüdür. We are starting this section to provide our community with transparency as to how Flarum is run, and to help those hoping to contribute to Flarum. -------------------------------------------------------------------------------- /i18n/tr/docusaurus-plugin-content-docs/version-1.x/internal/README.md: -------------------------------------------------------------------------------- 1 | --- 2 | slug: '/internal' 3 | --- 4 | 5 | # Internal Team Docs 6 | 7 | Bu, Flarum ekibi tarafından dahili olarak kullanılan bazı belgeleri yayınlayacağımız yeni bir belgeleme bölümüdür. We are starting this section to provide our community with transparency as to how Flarum is run, and to help those hoping to contribute to Flarum. -------------------------------------------------------------------------------- /i18n/tr/docusaurus-plugin-content-docs/version-1.x/releases.md: -------------------------------------------------------------------------------- 1 | # Sürüm Notları 2 | 3 | 4 | 14 | 15 | Sürüm notları [Flarum Topluluğu](https://discuss.flarum.org/t/blog?sort=newest)'nda bulunabilir. 16 | -------------------------------------------------------------------------------- /i18n/de/docusaurus-plugin-content-docs/current/releases.md: -------------------------------------------------------------------------------- 1 | # Versionshinweise 2 | 3 | 4 | 14 | 15 | Versionshinweise sind in der [Flarum Community](https://discuss.flarum.org/t/blog?sort=newest) zu finden. 16 | -------------------------------------------------------------------------------- /i18n/de/docusaurus-plugin-content-docs/version-1.x/releases.md: -------------------------------------------------------------------------------- 1 | # Versionshinweise 2 | 3 | 4 | 14 | 15 | Versionshinweise sind in der [Flarum Community](https://discuss.flarum.org/t/blog?sort=newest) zu finden. 16 | -------------------------------------------------------------------------------- /i18n/vi/docusaurus-plugin-content-docs/current/releases.md: -------------------------------------------------------------------------------- 1 | # Ghi chú phát hành 2 | 3 | 4 | 14 | 15 | Các ghi chú phát hành để thể tìm thấy trong [Cộng đồng Flarum](https://discuss.flarum.org/t/blog?sort=newest). 16 | -------------------------------------------------------------------------------- /crowdin.yml: -------------------------------------------------------------------------------- 1 | files: 2 | - source: /i18n/en/**/* 3 | translation: /i18n/%two_letters_code%/**/%original_file_name% 4 | - source: /docs/**/* 5 | translation: /i18n/%two_letters_code%/docusaurus-plugin-content-docs/current/**/%original_file_name% 6 | - source: /versioned_docs/version-1.x/**/* 7 | translation: /i18n/%two_letters_code%/docusaurus-plugin-content-docs/version-1.x/**/%original_file_name% 8 | -------------------------------------------------------------------------------- /i18n/vi/docusaurus-plugin-content-docs/version-1.x/releases.md: -------------------------------------------------------------------------------- 1 | # Ghi chú phát hành 2 | 3 | 4 | 14 | 15 | Các ghi chú phát hành để thể tìm thấy trong [Cộng đồng Flarum](https://discuss.flarum.org/t/blog?sort=newest). 16 | -------------------------------------------------------------------------------- /i18n/es/docusaurus-plugin-content-docs/current/releases.md: -------------------------------------------------------------------------------- 1 | # Notas de la versión 2 | 3 | 4 | 14 | 15 | Las notas de la versión se pueden encontrar en la [Comunidad de Flarum](https://discuss.flarum.org/t/blog?sort=newest). 16 | -------------------------------------------------------------------------------- /i18n/it/docusaurus-plugin-content-docs/current/releases.md: -------------------------------------------------------------------------------- 1 | # Note di rilascio 2 | 3 | 4 | 14 | 15 | Le note di rilascio possono essere trovate facilmente nel [Forum di Flarum](https://discuss.flarum.org/t/blog?sort=newest). 16 | -------------------------------------------------------------------------------- /i18n/es/docusaurus-plugin-content-docs/version-1.x/releases.md: -------------------------------------------------------------------------------- 1 | # Notas de la versión 2 | 3 | 4 | 14 | 15 | Las notas de la versión se pueden encontrar en la [Comunidad de Flarum](https://discuss.flarum.org/t/blog?sort=newest). 16 | -------------------------------------------------------------------------------- /i18n/it/docusaurus-plugin-content-docs/version-1.x/releases.md: -------------------------------------------------------------------------------- 1 | # Note di rilascio 2 | 3 | 4 | 14 | 15 | Le note di rilascio possono essere trovate facilmente nel [Forum di Flarum](https://discuss.flarum.org/t/blog?sort=newest). 16 | -------------------------------------------------------------------------------- /src/assets/adjustments-vertical.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | -------------------------------------------------------------------------------- /i18n/de/docusaurus-plugin-content-docs/current/internal/README.md: -------------------------------------------------------------------------------- 1 | --- 2 | slug: '/internal' 3 | --- 4 | 5 | # Interne Team Dokumentation 6 | 7 | Dies ist ein neuer Dokumentationsbereich, in dem wir einige Dokumente veröffentlichen werden, die intern vom Flarum-Team verwendet werden. Wir starten diesen Abschnitt, um unserer Community Transparenz darüber zu verschaffen, wie Flarum betrieben wird, und um denjenigen zu helfen, die zu Flarum beitragen möchten. -------------------------------------------------------------------------------- /i18n/de/docusaurus-plugin-content-docs/version-1.x/internal/README.md: -------------------------------------------------------------------------------- 1 | --- 2 | slug: '/internal' 3 | --- 4 | 5 | # Interne Team Dokumentation 6 | 7 | Dies ist ein neuer Dokumentationsbereich, in dem wir einige Dokumente veröffentlichen werden, die intern vom Flarum-Team verwendet werden. Wir starten diesen Abschnitt, um unserer Community Transparenz darüber zu verschaffen, wie Flarum betrieben wird, und um denjenigen zu helfen, die zu Flarum beitragen möchten. -------------------------------------------------------------------------------- /src/assets/book-open.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | -------------------------------------------------------------------------------- /src/assets/light-bulb.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | -------------------------------------------------------------------------------- /src/assets/document-arrow-up.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/current/admin.md: -------------------------------------------------------------------------------- 1 | # 后台管理面板 2 | 3 | Flarum 管理面板是一个友好的论坛管理界面。 且只对「管理组」成员可见。 点击论坛右上角您的 **用户名**, 选择 **后台管理** 即可进入管理面板。 4 | 5 | 管理员控制面板有如下部分，具体是： 6 | - **仪表盘** - 显示主要的管理员控制面板，包含统计信息和其他相关信息。 7 | - [常规](https://docs.flarum.org/mail) - 设置论坛名称、简介以及其他基础设置。 8 | - **邮箱** - 允许您配置论坛邮件服务。 更多信息请 [点击此处](https://docs.flarum.org/mail)。 9 | - **权限** - 显示每个用户组的权限，并允许您配置全站和特定范围。 10 | - **外观** - 允许您自定义论坛的颜色、图标和添加额外的 CSS 以自定义论坛样式。 11 | - **用户** - 为您提供论坛中所有用户的分页列表，可以在此编辑或管理用户。 12 | 13 | 除了以上提到的这些部分，主管理面板还通过_扩展_部分来允许你管理安装的扩展，这也包括 Flarum 的核心扩展，例如 Tags。 在 _主题 _ 和 _语言_ 模块下，您可以修改论坛主题或使用扩展以适应多语言。 14 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/version-1.x/admin.md: -------------------------------------------------------------------------------- 1 | # 后台管理面板 2 | 3 | Flarum 管理面板是一个友好的论坛管理界面。 且只对「管理组」成员可见。 点击论坛右上角您的 **用户名**, 选择 **后台管理** 即可进入管理面板。 4 | 5 | 管理员控制面板有如下部分，具体是： 6 | - **仪表盘** - 显示主要的管理员控制面板，包含统计信息和其他相关信息。 7 | - [常规](https://docs.flarum.org/mail) - 设置论坛名称、简介以及其他基础设置。 8 | - **邮箱** - 允许您配置论坛邮件服务。 更多信息请 [点击此处](https://docs.flarum.org/mail)。 9 | - **权限** - 显示每个用户组的权限，并允许您配置全站和特定范围。 10 | - **外观** - 允许您自定义论坛的颜色、图标和添加额外的 CSS 以自定义论坛样式。 11 | - **用户** - 为您提供论坛中所有用户的分页列表，可以在此编辑或管理用户。 12 | 13 | 除了以上提到的这些部分，主管理面板还通过_扩展_部分来允许你管理安装的扩展，这也包括 Flarum 的核心扩展，例如 Tags。 在 _主题 _ 和 _语言_ 模块下，您可以修改论坛主题或使用扩展以适应多语言。 14 | -------------------------------------------------------------------------------- /i18n/zh/code.json: -------------------------------------------------------------------------------- 1 | { 2 | "customtheme.docs.lang.nonDefaultLangLabel": { 3 | "message": "此页面的翻译可能更新不及时，最新信息请以{defaultLocaleLink} 为准。如果您想贡献翻译，请前往 {crowdinLink}。", 4 | "description": "The label used to tell the user that they're browsing translated docs that might be out of sync" 5 | }, 6 | "customtheme.docs.lang.defaultLocaleLinkLabel": { 7 | "message": "英文文档", 8 | "description": "The label used for the latest version suggestion link label" 9 | }, 10 | "customtheme.docs.versions.crowdinLinkLabel": { 11 | "message": "Crowdin", 12 | "description": "The label used for Crowdin link label" 13 | } 14 | } -------------------------------------------------------------------------------- /i18n/de/code.json: -------------------------------------------------------------------------------- 1 | { 2 | "customtheme.docs.lang.nonDefaultLangLabel": { 3 | "message": "The translation of this page may not be up to date, please refer to the {defaultLocaleLink} for the latest information. If you would like to contribute, you can do so {crowdinLink}, where we coordinate the translations.", 4 | "description": "The label used to tell the user that they're browsing translated docs that might be out of sync" 5 | }, 6 | "customtheme.docs.lang.defaultLocaleLinkLabel": { 7 | "message": "standardsprachversion", 8 | "description": "The label used for the latest version suggestion link label" 9 | }, 10 | "customtheme.docs.versions.crowdinLinkLabel": { 11 | "message": "via Crowdin", 12 | "description": "The label used for Crowdin link label" 13 | } 14 | } -------------------------------------------------------------------------------- /i18n/en/code.json: -------------------------------------------------------------------------------- 1 | { 2 | "customtheme.docs.lang.nonDefaultLangLabel": { 3 | "message": "The translation of this page may not be up to date, please refer to the {defaultLocaleLink} for the latest information. If you would like to contribute, you can do so {crowdinLink}, where we coordinate the translations.", 4 | "description": "The label used to tell the user that they're browsing translated docs that might be out of sync" 5 | }, 6 | "customtheme.docs.lang.defaultLocaleLinkLabel": { 7 | "message": "default locale version", 8 | "description": "The label used for the latest version suggestion link label" 9 | }, 10 | "customtheme.docs.versions.crowdinLinkLabel": { 11 | "message": "via Crowdin", 12 | "description": "The label used for Crowdin link label" 13 | } 14 | } -------------------------------------------------------------------------------- /i18n/es/code.json: -------------------------------------------------------------------------------- 1 | { 2 | "customtheme.docs.lang.nonDefaultLangLabel": { 3 | "message": "The translation of this page may not be up to date, please refer to the {defaultLocaleLink} for the latest information. If you would like to contribute, you can do so {crowdinLink}, where we coordinate the translations.", 4 | "description": "The label used to tell the user that they're browsing translated docs that might be out of sync" 5 | }, 6 | "customtheme.docs.lang.defaultLocaleLinkLabel": { 7 | "message": "documento en Inglés", 8 | "description": "The label used for the latest version suggestion link label" 9 | }, 10 | "customtheme.docs.versions.crowdinLinkLabel": { 11 | "message": "usa Crowdin", 12 | "description": "The label used for Crowdin link label" 13 | } 14 | } -------------------------------------------------------------------------------- /i18n/it/code.json: -------------------------------------------------------------------------------- 1 | { 2 | "customtheme.docs.lang.nonDefaultLangLabel": { 3 | "message": "The translation of this page may not be up to date, please refer to the {defaultLocaleLink} for the latest information. If you would like to contribute, you can do so {crowdinLink}, where we coordinate the translations.", 4 | "description": "The label used to tell the user that they're browsing translated docs that might be out of sync" 5 | }, 6 | "customtheme.docs.lang.defaultLocaleLinkLabel": { 7 | "message": "default locale version", 8 | "description": "The label used for the latest version suggestion link label" 9 | }, 10 | "customtheme.docs.versions.crowdinLinkLabel": { 11 | "message": "via Crowdin", 12 | "description": "The label used for Crowdin link label" 13 | } 14 | } -------------------------------------------------------------------------------- /i18n/tr/code.json: -------------------------------------------------------------------------------- 1 | { 2 | "customtheme.docs.lang.nonDefaultLangLabel": { 3 | "message": "The translation of this page may not be up to date, please refer to the {defaultLocaleLink} for the latest information. If you would like to contribute, you can do so {crowdinLink}, where we coordinate the translations.", 4 | "description": "The label used to tell the user that they're browsing translated docs that might be out of sync" 5 | }, 6 | "customtheme.docs.lang.defaultLocaleLinkLabel": { 7 | "message": "default locale version", 8 | "description": "The label used for the latest version suggestion link label" 9 | }, 10 | "customtheme.docs.versions.crowdinLinkLabel": { 11 | "message": "via Crowdin", 12 | "description": "The label used for Crowdin link label" 13 | } 14 | } -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/current/themes.md: -------------------------------------------------------------------------------- 1 | # 样式主题 2 | 3 | 尽管我们一直在努力使 Flarum 变得尽可能美丽，但每个社区可能都希望进行一些调整/修改，以适合他们所需的风格。 4 | 5 | ## 管理面板 6 | 7 | [管理面板](admin.md) 的「外观」页面是自定义论坛的绝佳起点。 在这里，您可以： 8 | 9 | - 选择主题颜色 10 | - 切换夜间模式和彩色导航栏。 11 | - 上传标志和站点图标（浏览器标签中显示的图标）。 12 | - 在自定义页眉和页脚添加 HTML。 13 | - 添加 [自定义LESS/CSS](#css-主题) 来改变元素的显示方式。 14 | 15 | ## CSS 主题 16 | 17 | CSS 是一种样式表语言，它告诉浏览器如何显示网页的元素。 它允许我们修改所有的东西，从颜色到字体到元素的大小，从定位到动画等等。 添加自定义 CSS 是修改您的 Flarum 默认主题的好方法。 18 | 19 | CSS 教程不在本文档的讨论范围之内，但是有大量的优质在线资源可供您学习 CSS 的基础知识。 20 | 21 | :::tip 22 | 23 | Flarum 其实使用了 LESS，它支持变量、条件和函数，可以让您更轻松地编写 CSS。 24 | 25 | ::: 26 | 27 | ## 扩展 28 | 29 | Flarum 灵活的 [扩展系统](extensions.md) 允许您添加、删除或修改 Flarum 的任何部分。 如果您想做实质性的主题修改，除了改变颜色/大小/样式之外，一个自定义的扩展绝对是您的最佳选择。 要学习如何制作扩展，请查看我们的 [扩展文档](extension/README.md)！ 30 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/version-1.x/themes.md: -------------------------------------------------------------------------------- 1 | # 样式主题 2 | 3 | 尽管我们一直在努力使 Flarum 变得尽可能美丽，但每个社区可能都希望进行一些调整/修改，以适合他们所需的风格。 4 | 5 | ## 管理面板 6 | 7 | [管理面板](admin.md) 的「外观」页面是自定义论坛的绝佳起点。 在这里，您可以： 8 | 9 | - 选择主题颜色 10 | - 切换夜间模式和彩色导航栏。 11 | - 上传标志和站点图标（浏览器标签中显示的图标）。 12 | - 在自定义页眉和页脚添加 HTML。 13 | - 添加 [自定义LESS/CSS](#css-主题) 来改变元素的显示方式。 14 | 15 | ## CSS 主题 16 | 17 | CSS 是一种样式表语言，它告诉浏览器如何显示网页的元素。 它允许我们修改所有的东西，从颜色到字体到元素的大小，从定位到动画等等。 添加自定义 CSS 是修改您的 Flarum 默认主题的好方法。 18 | 19 | CSS 教程不在本文档的讨论范围之内，但是有大量的优质在线资源可供您学习 CSS 的基础知识。 20 | 21 | :::tip 22 | 23 | Flarum 其实使用了 LESS，它支持变量、条件和函数，可以让您更轻松地编写 CSS。 24 | 25 | ::: 26 | 27 | ## 扩展 28 | 29 | Flarum 灵活的 [扩展系统](extensions.md) 允许您添加、删除或修改 Flarum 的任何部分。 如果您想做实质性的主题修改，除了改变颜色/大小/样式之外，一个自定义的扩展绝对是您的最佳选择。 要学习如何制作扩展，请查看我们的 [扩展文档](extension/README.md)！ 30 | -------------------------------------------------------------------------------- /i18n/vi/code.json: -------------------------------------------------------------------------------- 1 | { 2 | "customtheme.docs.lang.nonDefaultLangLabel": { 3 | "message": "The translation of this page may not be up to date, please refer to the {defaultLocaleLink} for the latest information. If you would like to contribute, you can do so {crowdinLink}, where we coordinate the translations.", 4 | "description": "The label used to tell the user that they're browsing translated docs that might be out of sync" 5 | }, 6 | "customtheme.docs.lang.defaultLocaleLinkLabel": { 7 | "message": "phiên bản ngôn ngữ mặc định", 8 | "description": "The label used for the latest version suggestion link label" 9 | }, 10 | "customtheme.docs.versions.crowdinLinkLabel": { 11 | "message": "thông qua Crowdin", 12 | "description": "The label used for Crowdin link label" 13 | } 14 | } -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Flarum Docs 2 | 3 | This repository contains the source code for [Flarum's docs site](https://docs.flarum.org). 4 | 5 | In order to avoid conflicts and corruption during translation synchronization, we only currently accept content contributions in English, and translations are only accepted through [crowdin](https://crowdin.com/project/flarum-docs). We really appreciate all contributions, and these measures help ensure that documentation is up to date and avoids breaking unexpectedly. See [our docs](https://docs.flarum.org/contributing-docs-translations) for more information. 6 | 7 | ## Testing locally 8 | 9 | Our documentation is generated with [Docusaurus](https://docusaurus.io/docs). 10 | Use Yarn to install the dependencies and start Docusaurus in a local webserver: 11 | 12 | ```bash 13 | yarn install 14 | yarn run start 15 | ``` -------------------------------------------------------------------------------- /versioned_docs/version-1.x/extend/cli.md: -------------------------------------------------------------------------------- 1 | # Flarum CLI 2 | 3 | The Flarum development ecosystem is oriented around many small, modules, interacting extensions. 4 | This is a very powerful and flexible paradigm, but it also brings the maintenance cost of creating and maintaining all these extensions. 5 | 6 | We've created the Flarum CLI (command line interface) as a tool to help developers by automating some repetitive and menial tasks, and allow them to get into the actual work without much hassle. 7 | 8 | Major updates about Flarum CLI will be published [on this discussion](https://discuss.flarum.org/d/28427-flarum-cli-v10). 9 | 10 | See the [package's readme](https://github.com/flarum/cli#readme) for information on: 11 | 12 | - Installation 13 | - Usage 14 | - Upgrading 15 | - Available commands 16 | - Some implementation details, if you're interested 17 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/current/extend/cli.md: -------------------------------------------------------------------------------- 1 | # 开发者讲解：扩展开发的工作流程 2 | 3 | The Flarum development ecosystem is oriented around many small, modules, interacting extensions. This is a very powerful and flexible paradigm, but it also brings the maintenance cost of creating and maintaining all these extensions. 4 | 5 | We've created the Flarum CLI (command line interface) as a tool to help developers by automating some repetitive and menial tasks, and allow them to get into the actual work without much hassle. 6 | 7 | Major updates about Flarum CLI will be published [on this discussion](https://discuss.flarum.org/d/28427-flarum-cli-v10). 8 | 9 | See the [package's readme](https://github.com/flarum/cli#readme) for information on: 10 | 11 | - 安装 12 | - Usage 13 | - Upgrading 14 | - Available commands 15 | - Some implementation details, if you're interested 16 | -------------------------------------------------------------------------------- /i18n/de/docusaurus-plugin-content-docs/current/extend/cli.md: -------------------------------------------------------------------------------- 1 | # Flarum CLI 2 | 3 | The Flarum development ecosystem is oriented around many small, modules, interacting extensions. This is a very powerful and flexible paradigm, but it also brings the maintenance cost of creating and maintaining all these extensions. 4 | 5 | We've created the Flarum CLI (command line interface) as a tool to help developers by automating some repetitive and menial tasks, and allow them to get into the actual work without much hassle. 6 | 7 | Major updates about Flarum CLI will be published [on this discussion](https://discuss.flarum.org/d/28427-flarum-cli-v10). 8 | 9 | See the [package's readme](https://github.com/flarum/cli#readme) for information on: 10 | 11 | - Installation 12 | - Usage 13 | - Upgrading 14 | - Available commands 15 | - Some implementation details, if you're interested 16 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/version-1.x/extend/cli.md: -------------------------------------------------------------------------------- 1 | # 开发者讲解：扩展开发的工作流程 2 | 3 | The Flarum development ecosystem is oriented around many small, modules, interacting extensions. This is a very powerful and flexible paradigm, but it also brings the maintenance cost of creating and maintaining all these extensions. 4 | 5 | We've created the Flarum CLI (command line interface) as a tool to help developers by automating some repetitive and menial tasks, and allow them to get into the actual work without much hassle. 6 | 7 | Major updates about Flarum CLI will be published [on this discussion](https://discuss.flarum.org/d/28427-flarum-cli-v10). 8 | 9 | See the [package's readme](https://github.com/flarum/cli#readme) for information on: 10 | 11 | - 安装 12 | - Usage 13 | - Upgrading 14 | - Available commands 15 | - Some implementation details, if you're interested 16 | -------------------------------------------------------------------------------- /i18n/de/docusaurus-plugin-content-docs/version-1.x/extend/cli.md: -------------------------------------------------------------------------------- 1 | # Flarum CLI 2 | 3 | The Flarum development ecosystem is oriented around many small, modules, interacting extensions. This is a very powerful and flexible paradigm, but it also brings the maintenance cost of creating and maintaining all these extensions. 4 | 5 | We've created the Flarum CLI (command line interface) as a tool to help developers by automating some repetitive and menial tasks, and allow them to get into the actual work without much hassle. 6 | 7 | Major updates about Flarum CLI will be published [on this discussion](https://discuss.flarum.org/d/28427-flarum-cli-v10). 8 | 9 | See the [package's readme](https://github.com/flarum/cli#readme) for information on: 10 | 11 | - Installation 12 | - Usage 13 | - Upgrading 14 | - Available commands 15 | - Some implementation details, if you're interested 16 | -------------------------------------------------------------------------------- /i18n/tr/docusaurus-plugin-content-docs/current/extend/cli.md: -------------------------------------------------------------------------------- 1 | # Flarum CLI 2 | 3 | The Flarum development ecosystem is oriented around many small, modules, interacting extensions. This is a very powerful and flexible paradigm, but it also brings the maintenance cost of creating and maintaining all these extensions. 4 | 5 | We've created the Flarum CLI (command line interface) as a tool to help developers by automating some repetitive and menial tasks, and allow them to get into the actual work without much hassle. 6 | 7 | Major updates about Flarum CLI will be published [on this discussion](https://discuss.flarum.org/d/28427-flarum-cli-v10). 8 | 9 | See the [package's readme](https://github.com/flarum/cli#readme) for information on: 10 | 11 | - Kurulum Belgeleri 12 | - Usage 13 | - Upgrading 14 | - Available commands 15 | - Some implementation details, if you're interested 16 | -------------------------------------------------------------------------------- /i18n/tr/docusaurus-plugin-content-docs/version-1.x/extend/cli.md: -------------------------------------------------------------------------------- 1 | # Flarum CLI 2 | 3 | The Flarum development ecosystem is oriented around many small, modules, interacting extensions. This is a very powerful and flexible paradigm, but it also brings the maintenance cost of creating and maintaining all these extensions. 4 | 5 | We've created the Flarum CLI (command line interface) as a tool to help developers by automating some repetitive and menial tasks, and allow them to get into the actual work without much hassle. 6 | 7 | Major updates about Flarum CLI will be published [on this discussion](https://discuss.flarum.org/d/28427-flarum-cli-v10). 8 | 9 | See the [package's readme](https://github.com/flarum/cli#readme) for information on: 10 | 11 | - Kurulum Belgeleri 12 | - Usage 13 | - Upgrading 14 | - Available commands 15 | - Some implementation details, if you're interested 16 | -------------------------------------------------------------------------------- /.github/workflows/deploy.yml: -------------------------------------------------------------------------------- 1 | name: Deploy to production 2 | 3 | on: 4 | workflow_dispatch: 5 | push: 6 | branches: 7 | - main 8 | 9 | jobs: 10 | deploy: 11 | runs-on: ubuntu-latest 12 | 13 | steps: 14 | - uses: actions/checkout@master 15 | 16 | - name: Use Node.js 17 | uses: actions/setup-node@v4 18 | with: 19 | node-version: '20.x' 20 | - run: npm i 21 | - run: npm run build --if-present 22 | 23 | - name: copy compiled assets to remote 24 | uses: appleboy/scp-action@v1 25 | with: 26 | host: ${{ secrets.DEPLOY_HOST }} 27 | username: ${{ secrets.DEPLOY_USERNAME }} 28 | key: ${{ secrets.DEPLOY_SSH_KEY }} 29 | port: ${{ secrets.DEPLOY_PORT }} 30 | source: build 31 | target: public_html/docs.flarum.org 32 | -------------------------------------------------------------------------------- /i18n/vi/docusaurus-plugin-content-docs/current/extend/cli.md: -------------------------------------------------------------------------------- 1 | # Flarum CLI 2 | 3 | Hệ sinh thái phát triển Flarum được định hướng xung quanh nhiều mô-đun nhỏ, phần mở rộng tương tác. Đây là một mô hình rất mạnh mẽ và linh hoạt, nhưng nó cũng mang lại chi phí bảo trì cho việc tạo và duy trì tất cả các phần mở rộng này. 4 | 5 | Chúng tôi đã tạo Flarum CLI (giao diện dòng lệnh) như một công cụ để trợ giúp các nhà phát triển bằng cách tự động hóa một số tác vụ lặp đi lặp lại và thường xuyên, đồng thời cho phép họ tham gia vào công việc thực tế mà không gặp nhiều rắc rối. 6 | 7 | Các cập nhật chính về Flarum CLI sẽ được công bố [trong cuộc thảo luận này](https://discuss.flarum.org/d/28427-flarum-cli-v10). 8 | 9 | Xem [readme của gói](https://github.com/flarum/cli#readme) để biết thông tin về: 10 | 11 | - Cài đặt 12 | - Sử dụng 13 | - Nâng cấp 14 | - Các lệnh có sẵn 15 | - Một số chi tiết triển khai, nếu bạn quan tâm 16 | -------------------------------------------------------------------------------- /i18n/vi/docusaurus-plugin-content-docs/version-1.x/extend/cli.md: -------------------------------------------------------------------------------- 1 | # Flarum CLI 2 | 3 | Hệ sinh thái phát triển Flarum được định hướng xung quanh nhiều mô-đun nhỏ, phần mở rộng tương tác. Đây là một mô hình rất mạnh mẽ và linh hoạt, nhưng nó cũng mang lại chi phí bảo trì cho việc tạo và duy trì tất cả các phần mở rộng này. 4 | 5 | Chúng tôi đã tạo Flarum CLI (giao diện dòng lệnh) như một công cụ để trợ giúp các nhà phát triển bằng cách tự động hóa một số tác vụ lặp đi lặp lại và thường xuyên, đồng thời cho phép họ tham gia vào công việc thực tế mà không gặp nhiều rắc rối. 6 | 7 | Các cập nhật chính về Flarum CLI sẽ được công bố [trong cuộc thảo luận này](https://discuss.flarum.org/d/28427-flarum-cli-v10). 8 | 9 | Xem [readme của gói](https://github.com/flarum/cli#readme) để biết thông tin về: 10 | 11 | - Cài đặt 12 | - Sử dụng 13 | - Nâng cấp 14 | - Các lệnh có sẵn 15 | - Một số chi tiết triển khai, nếu bạn quan tâm 16 | -------------------------------------------------------------------------------- /i18n/es/docusaurus-plugin-content-docs/current/extend/cli.md: -------------------------------------------------------------------------------- 1 | # Desarrolladores explicando su flujo de trabajo para el desarrollo de extensiones 2 | 3 | The Flarum development ecosystem is oriented around many small, modules, interacting extensions. This is a very powerful and flexible paradigm, but it also brings the maintenance cost of creating and maintaining all these extensions. 4 | 5 | We've created the Flarum CLI (command line interface) as a tool to help developers by automating some repetitive and menial tasks, and allow them to get into the actual work without much hassle. 6 | 7 | Major updates about Flarum CLI will be published [on this discussion](https://discuss.flarum.org/d/28427-flarum-cli-v10). 8 | 9 | See the [package's readme](https://github.com/flarum/cli#readme) for information on: 10 | 11 | - Instalación 12 | - Usage 13 | - Upgrading 14 | - Available commands 15 | - Some implementation details, if you're interested 16 | -------------------------------------------------------------------------------- /i18n/es/docusaurus-plugin-content-docs/version-1.x/extend/cli.md: -------------------------------------------------------------------------------- 1 | # Desarrolladores explicando su flujo de trabajo para el desarrollo de extensiones 2 | 3 | The Flarum development ecosystem is oriented around many small, modules, interacting extensions. This is a very powerful and flexible paradigm, but it also brings the maintenance cost of creating and maintaining all these extensions. 4 | 5 | We've created the Flarum CLI (command line interface) as a tool to help developers by automating some repetitive and menial tasks, and allow them to get into the actual work without much hassle. 6 | 7 | Major updates about Flarum CLI will be published [on this discussion](https://discuss.flarum.org/d/28427-flarum-cli-v10). 8 | 9 | See the [package's readme](https://github.com/flarum/cli#readme) for information on: 10 | 11 | - Instalación 12 | - Usage 13 | - Upgrading 14 | - Available commands 15 | - Some implementation details, if you're interested 16 | -------------------------------------------------------------------------------- /i18n/it/docusaurus-plugin-content-docs/current/extend/cli.md: -------------------------------------------------------------------------------- 1 | # Sviluppatori che spiegano il loro flusso di lavoro per lo sviluppo di estensioni 2 | 3 | The Flarum development ecosystem is oriented around many small, modules, interacting extensions. This is a very powerful and flexible paradigm, but it also brings the maintenance cost of creating and maintaining all these extensions. 4 | 5 | We've created the Flarum CLI (command line interface) as a tool to help developers by automating some repetitive and menial tasks, and allow them to get into the actual work without much hassle. 6 | 7 | Major updates about Flarum CLI will be published [on this discussion](https://discuss.flarum.org/d/28427-flarum-cli-v10). 8 | 9 | See the [package's readme](https://github.com/flarum/cli#readme) for information on: 10 | 11 | - Installazione 12 | - Usage 13 | - Upgrading 14 | - Available commands 15 | - Some implementation details, if you're interested 16 | -------------------------------------------------------------------------------- /i18n/it/docusaurus-plugin-content-docs/version-1.x/extend/cli.md: -------------------------------------------------------------------------------- 1 | # Sviluppatori che spiegano il loro flusso di lavoro per lo sviluppo di estensioni 2 | 3 | The Flarum development ecosystem is oriented around many small, modules, interacting extensions. This is a very powerful and flexible paradigm, but it also brings the maintenance cost of creating and maintaining all these extensions. 4 | 5 | We've created the Flarum CLI (command line interface) as a tool to help developers by automating some repetitive and menial tasks, and allow them to get into the actual work without much hassle. 6 | 7 | Major updates about Flarum CLI will be published [on this discussion](https://discuss.flarum.org/d/28427-flarum-cli-v10). 8 | 9 | See the [package's readme](https://github.com/flarum/cli#readme) for information on: 10 | 11 | - Installazione 12 | - Usage 13 | - Upgrading 14 | - Available commands 15 | - Some implementation details, if you're interested 16 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/current/mail.md: -------------------------------------------------------------------------------- 1 | # 电子邮件配置 2 | 3 | 社区需要发送邮箱验证、密码重置、消息，以及其他与用户交流的邮件。 作为论坛管理员，您首先要做的几件事之一就是配置好论坛的邮件服务！ 配置错误的话，用户在注册时会收到报错。 4 | 5 | ## 支持的邮件驱动 6 | 7 | Flarum 默认提供以下所列驱动。 若有需要，开发者可自行开发插件添加 [自定义邮件驱动](extend/mail.md)。 8 | 9 | ### SMTP 10 | 11 | 这是最常用的邮件驱动，需要您配置主机地址、端口、加密方式、用户名和密码，以使用外部 SMTP 服务。 请注意，加密方式必须为小写的 `ssl` 或 `tls`。 12 | 13 | ### Mail 14 | 15 | `mail` 会用到许多托管服务器上都有的 sendmail / postfix 邮件系统。 您必须在服务器上正确安装并配置好 sendmail 才能正常工作。 16 | 17 | ### Mailgun 18 | 19 | 通过您的 [Mailgun](https://www.mailgun.com/) 来发送邮件。 您需要填写 secret key，以及您在 Mailgun 配置的域名、区域。 20 | 21 | 要使用 Mailgun 驱动，您需要安装 Guzzle composer 包 (一个 PHP HTTP 客户端)。 在您的 Flarum 根目录下运行 `composer require guzzlehttp/guzzle:^6.0|^7.0` 。 22 | 23 | ### Log 24 | 25 | 邮件驱动 log 不会发送邮件，主要由开发者使用。 它会在在`FLARUM_ROOT_DIRECTORY/storage/logs`中的日志文件写入所有邮件的内容。 26 | 27 | ## 测试邮件 28 | 29 | 在您保存邮件配置后，您可以在后台管理面板的邮件配置页面点击「发送测试邮件」发送一封邮件以检测您的配置是否可用。 如果提示错误，或者您没有收到测试邮件，那就意味着配置有误，请检查配置然后重试。 如果没有任何报错，邮件也发送出去了，但是您在收件箱中找不到测试邮件，请去垃圾箱看看，它很可能在那边。 30 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/version-1.x/mail.md: -------------------------------------------------------------------------------- 1 | # 电子邮件配置 2 | 3 | 社区需要发送邮箱验证、密码重置、消息，以及其他与用户交流的邮件。 作为论坛管理员，您首先要做的几件事之一就是配置好论坛的邮件服务！ 配置错误的话，用户在注册时会收到报错。 4 | 5 | ## 支持的邮件驱动 6 | 7 | Flarum 默认提供以下所列驱动。 若有需要，开发者可自行开发插件添加 [自定义邮件驱动](extend/mail.md)。 8 | 9 | ### SMTP 10 | 11 | 这是最常用的邮件驱动，需要您配置主机地址、端口、加密方式、用户名和密码，以使用外部 SMTP 服务。 请注意，加密方式必须为小写的 `ssl` 或 `tls`。 12 | 13 | ### Mail 14 | 15 | `mail` 会用到许多托管服务器上都有的 sendmail / postfix 邮件系统。 您必须在服务器上正确安装并配置好 sendmail 才能正常工作。 16 | 17 | ### Mailgun 18 | 19 | 通过您的 [Mailgun](https://www.mailgun.com/) 来发送邮件。 您需要填写 secret key，以及您在 Mailgun 配置的域名、区域。 20 | 21 | 要使用 Mailgun 驱动，您需要安装 Guzzle composer 包 (一个 PHP HTTP 客户端)。 在您的 Flarum 根目录下运行 `composer require guzzlehttp/guzzle:^6.0|^7.0` 。 22 | 23 | ### Log 24 | 25 | 邮件驱动 log 不会发送邮件，主要由开发者使用。 它会在在`FLARUM_ROOT_DIRECTORY/storage/logs`中的日志文件写入所有邮件的内容。 26 | 27 | ## 测试邮件 28 | 29 | 在您保存邮件配置后，您可以在后台管理面板的邮件配置页面点击「发送测试邮件」发送一封邮件以检测您的配置是否可用。 如果提示错误，或者您没有收到测试邮件，那就意味着配置有误，请检查配置然后重试。 如果没有任何报错，邮件也发送出去了，但是您在收件箱中找不到测试邮件，请去垃圾箱看看，它很可能在那边。 30 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/current/contributing-docs-translations.md: -------------------------------------------------------------------------------- 1 | # 文档与翻译 2 | 3 | ## 补充文档 4 | 5 | 补充文档可以帮助无数未来的Flarum用户。 你可以在以下几点上下功夫： 6 | 7 | - 帮助Flarum最终用户使用一些高级Flarum功能的用户指南。 8 | - 更多 [常见问题](faq.md)。 9 | - 更加详细的 [故障排除](troubleshoot.md) 的步骤。 10 | - Flarum 开发或安装的逐步教程。 11 | - 扩展开发者的[技术参考指南](extend/README.md)。 12 | - 帮助我们提升你认为我们应该进一步阐述或更好地解释的其他事物。 13 | 14 | 找到相关主题的好方法是在我们社区的 [支持标签](https://discuss.flarum.org/t/support) 中寻找常见问题。 15 | 16 | ## 翻译Flarum 17 | 18 | 我们希望每个人都能使用Flarum，不论其掌握的语言种类！ 通过提供翻译，您可以让更多的人享受Flarum。 最好的是，我们使用方便用户的用户界面进行翻译，所以如果您想提供帮助，不需要硬性技术要求！ 19 | 20 | Flarum Core的翻译、捆绑扩展和社区扩展是通过 [Weblate](https://weblate.rob006.net/projects/flarum/) 管理的。 21 | 22 | 此文档的翻译通过 [Crowdin](https://crowdin.com/project/flarum-docs) 管理。 23 | 24 | Flarum基金会设立了“flarum-lang”组织，以支助笔译员以确保各种语言包的可用性。 您可以通过 [访问 GitHub 仓库](https://github.com/flarum-lang/about) 了解更多信息。 25 | 26 | 如果你想要支持现有的语言包，开始一项新的翻译，或者在使用weblate或crowdin时出现问题，您 [最好与 `flarum-lang` 团队](https://discuss.flarum.org/d/27519-the-flarum-language-project) 取得联系。 27 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/version-1.x/contributing-docs-translations.md: -------------------------------------------------------------------------------- 1 | # 文档与翻译 2 | 3 | ## 补充文档 4 | 5 | 补充文档可以帮助无数未来的Flarum用户。 你可以在以下几点上下功夫： 6 | 7 | - 帮助Flarum最终用户使用一些高级Flarum功能的用户指南。 8 | - 更多 [常见问题](faq.md)。 9 | - 更加详细的 [故障排除](troubleshoot.md) 的步骤。 10 | - Flarum 开发或安装的逐步教程。 11 | - 扩展开发者的[技术参考指南](extend/README.md)。 12 | - 帮助我们提升你认为我们应该进一步阐述或更好地解释的其他事物。 13 | 14 | 找到相关主题的好方法是在我们社区的 [支持标签](https://discuss.flarum.org/t/support) 中寻找常见问题。 15 | 16 | ## 翻译Flarum 17 | 18 | 我们希望每个人都能使用Flarum，不论其掌握的语言种类！ 通过提供翻译，您可以让更多的人享受Flarum。 最好的是，我们使用方便用户的用户界面进行翻译，所以如果您想提供帮助，不需要硬性技术要求！ 19 | 20 | Flarum Core的翻译、捆绑扩展和社区扩展是通过 [Weblate](https://weblate.rob006.net/projects/flarum/) 管理的。 21 | 22 | 此文档的翻译通过 [Crowdin](https://crowdin.com/project/flarum-docs) 管理。 23 | 24 | Flarum基金会设立了“flarum-lang”组织，以支助笔译员以确保各种语言包的可用性。 您可以通过 [访问 GitHub 仓库](https://github.com/flarum-lang/about) 了解更多信息。 25 | 26 | 如果你想要支持现有的语言包，开始一项新的翻译，或者在使用weblate或crowdin时出现问题，您 [最好与 `flarum-lang` 团队](https://discuss.flarum.org/d/27519-the-flarum-language-project) 取得联系。 27 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-theme-classic/navbar.json: -------------------------------------------------------------------------------- 1 | { 2 | "item.label.Guide": { 3 | "message": "指南", 4 | "description": "Navbar item with label Guide" 5 | }, 6 | "item.label.Extend": { 7 | "message": "扩展", 8 | "description": "Navbar item with label Extend" 9 | }, 10 | "item.label.Internal": { 11 | "message": "内部", 12 | "description": "Navbar item with label Internal" 13 | }, 14 | "item.label.API Reference": { 15 | "message": "API 参考", 16 | "description": "Navbar item with label API Reference" 17 | }, 18 | "item.label.Flarum": { 19 | "message": "Flarum", 20 | "description": "Navbar item with label Flarum" 21 | }, 22 | "item.label.Home": { 23 | "message": "首页", 24 | "description": "Navbar item with label Home" 25 | }, 26 | "item.label.Community": { 27 | "message": "社区", 28 | "description": "Navbar item with label Community" 29 | }, 30 | "item.label.GitHub": { 31 | "message": "GitHub", 32 | "description": "Navbar item with label GitHub" 33 | } 34 | } -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/current/languages.md: -------------------------------------------------------------------------------- 1 | # 多语言支持 2 | 3 | 为您的 Flarum 添加新的界面语言很简单。 按照下面的说明，下载并安装语言包即可。 4 | 5 | 在您安装并启用一个语言包后，您可以将其 [设置为您论坛的默认语言](#设置默认语言)。 当您可以 [随时禁用](#禁用语言包) 用不到的语言。 如果您有使用任何第三方扩展，请务必在开始前 [阅读社区扩展说明](#社区扩展)。 6 | 7 | ## 安装语言包 8 | 9 | 欲开始，请访问 Flarum 社区上的 [Extensions > Languages](https://discuss.flarum.org/t/languages) 标签，并找到您想要安装的语言包。 10 | 11 | 语言包的安装方式与 [扩展](extensions.md) 相同。 语言包安装成功后会出现在后台管理界面的 **Extensions（插件）** 页面中，您可以在该页面启用语言包。 12 | 13 | 完成！ 您现在应该可以点击论坛顶部导航栏的语言选择器，将界面切换到新语言。 14 | 15 | ## 设置默认语言 16 | 17 | 如果安装的语言包能正常工作，您可能会想要将该语言设置为新用户和访客的默认语言。 您可以在后台管理面板的 **Basics（常规）** 页面中进行设置。 18 | 19 | ## 禁用语言包 20 | 21 | 当您不需要某种语言时，您可以选择关闭该语言。 只需在后台管理面板的 **Extensions（插件）** 页面中找到该语言包，然后将其关闭该语言包。 22 | 23 | 如果您的网站是单语网站，并且不希望语言选择器出现在论坛顶部的导航栏中，您可以禁用其他语言包。 当只有一种语言包处于启用状态时，语言选择器会自动隐藏。 24 | 25 | ## 社区扩展 26 | 27 | 虽然从 Flarum 社区中下载的语言包通常是包含所有 Flarum 原生捆绑扩展的翻译的，但是 _并没有规定说_ 语言包必须翻译了所有您安装的社区扩展。 是否提供、更新维护这些扩展的翻译取决于开发者的个人意愿。 28 | 29 | 因此，在您安装一个社区扩展前，请检查您使用的语言包是否包含了该扩展的翻译。 如果您发现了一个不支持您所需要语言的社区扩展，请直接联系开发者，让他/她添加翻译。 30 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/version-1.x/languages.md: -------------------------------------------------------------------------------- 1 | # 多语言支持 2 | 3 | 为您的 Flarum 添加新的界面语言很简单。 按照下面的说明，下载并安装语言包即可。 4 | 5 | 在您安装并启用一个语言包后，您可以将其 [设置为您论坛的默认语言](#设置默认语言)。 当您可以 [随时禁用](#禁用语言包) 用不到的语言。 如果您有使用任何第三方扩展，请务必在开始前 [阅读社区扩展说明](#社区扩展)。 6 | 7 | ## 安装语言包 8 | 9 | 欲开始，请访问 Flarum 社区上的 [Extensions > Languages](https://discuss.flarum.org/t/languages) 标签，并找到您想要安装的语言包。 10 | 11 | 语言包的安装方式与 [扩展](extensions.md) 相同。 语言包安装成功后会出现在后台管理界面的 **Extensions（插件）** 页面中，您可以在该页面启用语言包。 12 | 13 | 完成！ 您现在应该可以点击论坛顶部导航栏的语言选择器，将界面切换到新语言。 14 | 15 | ## 设置默认语言 16 | 17 | 如果安装的语言包能正常工作，您可能会想要将该语言设置为新用户和访客的默认语言。 您可以在后台管理面板的 **Basics（常规）** 页面中进行设置。 18 | 19 | ## 禁用语言包 20 | 21 | 当您不需要某种语言时，您可以选择关闭该语言。 只需在后台管理面板的 **Extensions（插件）** 页面中找到该语言包，然后将其关闭该语言包。 22 | 23 | 如果您的网站是单语网站，并且不希望语言选择器出现在论坛顶部的导航栏中，您可以禁用其他语言包。 当只有一种语言包处于启用状态时，语言选择器会自动隐藏。 24 | 25 | ## 社区扩展 26 | 27 | 虽然从 Flarum 社区中下载的语言包通常是包含所有 Flarum 原生捆绑扩展的翻译的，但是 _并没有规定说_ 语言包必须翻译了所有您安装的社区扩展。 是否提供、更新维护这些扩展的翻译取决于开发者的个人意愿。 28 | 29 | 因此，在您安装一个社区扩展前，请检查您使用的语言包是否包含了该扩展的翻译。 如果您发现了一个不支持您所需要语言的社区扩展，请直接联系开发者，让他/她添加翻译。 30 | -------------------------------------------------------------------------------- /i18n/en/docusaurus-theme-classic/navbar.json: -------------------------------------------------------------------------------- 1 | { 2 | "item.label.Guide": { 3 | "message": "Guide", 4 | "description": "Navbar item with label Guide" 5 | }, 6 | "item.label.Extend": { 7 | "message": "Extend", 8 | "description": "Navbar item with label Extend" 9 | }, 10 | "item.label.Internal": { 11 | "message": "Internal", 12 | "description": "Navbar item with label Internal" 13 | }, 14 | "item.label.API Reference": { 15 | "message": "API Reference", 16 | "description": "Navbar item with label API Reference" 17 | }, 18 | "item.label.Flarum": { 19 | "message": "Flarum", 20 | "description": "Navbar item with label Flarum" 21 | }, 22 | "item.label.Home": { 23 | "message": "Home", 24 | "description": "Navbar item with label Home" 25 | }, 26 | "item.label.Community": { 27 | "message": "Community", 28 | "description": "Navbar item with label Community" 29 | }, 30 | "item.label.GitHub": { 31 | "message": "GitHub", 32 | "description": "Navbar item with label GitHub" 33 | } 34 | } -------------------------------------------------------------------------------- /i18n/it/docusaurus-theme-classic/navbar.json: -------------------------------------------------------------------------------- 1 | { 2 | "item.label.Guide": { 3 | "message": "Guida", 4 | "description": "Navbar item with label Guide" 5 | }, 6 | "item.label.Extend": { 7 | "message": "Estendi", 8 | "description": "Navbar item with label Extend" 9 | }, 10 | "item.label.Internal": { 11 | "message": "Internal", 12 | "description": "Navbar item with label Internal" 13 | }, 14 | "item.label.API Reference": { 15 | "message": "Referenze API", 16 | "description": "Navbar item with label API Reference" 17 | }, 18 | "item.label.Flarum": { 19 | "message": "Flarum", 20 | "description": "Navbar item with label Flarum" 21 | }, 22 | "item.label.Home": { 23 | "message": "Home", 24 | "description": "Navbar item with label Home" 25 | }, 26 | "item.label.Community": { 27 | "message": "Community", 28 | "description": "Navbar item with label Community" 29 | }, 30 | "item.label.GitHub": { 31 | "message": "GitHub", 32 | "description": "Navbar item with label GitHub" 33 | } 34 | } -------------------------------------------------------------------------------- /i18n/de/docusaurus-theme-classic/navbar.json: -------------------------------------------------------------------------------- 1 | { 2 | "item.label.Guide": { 3 | "message": "Anleitung", 4 | "description": "Navbar item with label Guide" 5 | }, 6 | "item.label.Extend": { 7 | "message": "Erweitern", 8 | "description": "Navbar item with label Extend" 9 | }, 10 | "item.label.Internal": { 11 | "message": "Intern", 12 | "description": "Navbar item with label Internal" 13 | }, 14 | "item.label.API Reference": { 15 | "message": "API-Referenz", 16 | "description": "Navbar item with label API Reference" 17 | }, 18 | "item.label.Flarum": { 19 | "message": "Flarum", 20 | "description": "Navbar item with label Flarum" 21 | }, 22 | "item.label.Home": { 23 | "message": "Startseite", 24 | "description": "Navbar item with label Home" 25 | }, 26 | "item.label.Community": { 27 | "message": "Community", 28 | "description": "Navbar item with label Community" 29 | }, 30 | "item.label.GitHub": { 31 | "message": "GitHub", 32 | "description": "Navbar item with label GitHub" 33 | } 34 | } -------------------------------------------------------------------------------- /i18n/es/docusaurus-theme-classic/navbar.json: -------------------------------------------------------------------------------- 1 | { 2 | "item.label.Guide": { 3 | "message": "Guía", 4 | "description": "Navbar item with label Guide" 5 | }, 6 | "item.label.Extend": { 7 | "message": "Extender", 8 | "description": "Navbar item with label Extend" 9 | }, 10 | "item.label.Internal": { 11 | "message": "Internal", 12 | "description": "Navbar item with label Internal" 13 | }, 14 | "item.label.API Reference": { 15 | "message": "Referencia de la API", 16 | "description": "Navbar item with label API Reference" 17 | }, 18 | "item.label.Flarum": { 19 | "message": "Flarum", 20 | "description": "Navbar item with label Flarum" 21 | }, 22 | "item.label.Home": { 23 | "message": "Inicio", 24 | "description": "Navbar item with label Home" 25 | }, 26 | "item.label.Community": { 27 | "message": "Comunidad", 28 | "description": "Navbar item with label Community" 29 | }, 30 | "item.label.GitHub": { 31 | "message": "GitHub", 32 | "description": "Navbar item with label GitHub" 33 | } 34 | } -------------------------------------------------------------------------------- /i18n/tr/docusaurus-theme-classic/navbar.json: -------------------------------------------------------------------------------- 1 | { 2 | "item.label.Guide": { 3 | "message": "Kılavuz", 4 | "description": "Navbar item with label Guide" 5 | }, 6 | "item.label.Extend": { 7 | "message": "Genişletme", 8 | "description": "Navbar item with label Extend" 9 | }, 10 | "item.label.Internal": { 11 | "message": "Dahili", 12 | "description": "Navbar item with label Internal" 13 | }, 14 | "item.label.API Reference": { 15 | "message": "API Referansı", 16 | "description": "Navbar item with label API Reference" 17 | }, 18 | "item.label.Flarum": { 19 | "message": "Flarum", 20 | "description": "Navbar item with label Flarum" 21 | }, 22 | "item.label.Home": { 23 | "message": "Anasayfa", 24 | "description": "Navbar item with label Home" 25 | }, 26 | "item.label.Community": { 27 | "message": "Topluluk", 28 | "description": "Navbar item with label Community" 29 | }, 30 | "item.label.GitHub": { 31 | "message": "GitHub", 32 | "description": "Navbar item with label GitHub" 33 | } 34 | } -------------------------------------------------------------------------------- /i18n/vi/docusaurus-theme-classic/navbar.json: -------------------------------------------------------------------------------- 1 | { 2 | "item.label.Guide": { 3 | "message": "Hướng dẫn", 4 | "description": "Navbar item with label Guide" 5 | }, 6 | "item.label.Extend": { 7 | "message": "Mở rộng", 8 | "description": "Navbar item with label Extend" 9 | }, 10 | "item.label.Internal": { 11 | "message": "Nội bộ", 12 | "description": "Navbar item with label Internal" 13 | }, 14 | "item.label.API Reference": { 15 | "message": "Tham chiếu API", 16 | "description": "Navbar item with label API Reference" 17 | }, 18 | "item.label.Flarum": { 19 | "message": "Flarum", 20 | "description": "Navbar item with label Flarum" 21 | }, 22 | "item.label.Home": { 23 | "message": "Trang chủ", 24 | "description": "Navbar item with label Home" 25 | }, 26 | "item.label.Community": { 27 | "message": "Cộng đồng", 28 | "description": "Navbar item with label Community" 29 | }, 30 | "item.label.GitHub": { 31 | "message": "GitHub", 32 | "description": "Navbar item with label GitHub" 33 | } 34 | } -------------------------------------------------------------------------------- /docs/extend/assets.md: -------------------------------------------------------------------------------- 1 | # Extension Assets 2 | 3 | Some extensions might want to include assets like images or JSON files in their source code (note that this is not the same as uploads, which would probably require a [filesystem disk](filesystem.md)). 4 | 5 | This is actually very easy to do. Just create an `assets` folder at the root of your extension, and place any asset files there. 6 | Flarum will then automatically copy those files to its own `assets` directory (or other storage location if [one is offered by extensions](filesystem.md)) every time the extension is enabled or [`php flarum assets:publish`](../console.md) is executed. 7 | 8 | If using the default storage driver, assets will be available at `https://FORUM_URL/assets/extensions/EXTENSION_ID/file.path`. However, since other extensions might use remote filesystems, we recommend serializing the url to assets you need in the backend. See [Flarum's serialization of the logo and favicon URLs](https://github.com/flarum/framework/blob/80ded88692242e9656a1c399fa58f35f79ad9d3c/framework/core/src/Api/Resource/ForumResource.php#L104-L107) for an example. 9 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/current/extenders.md: -------------------------------------------------------------------------------- 1 | # 本地扩展 2 | 3 | 如果您想要在没有分发整个扩展的情况下自定义您的站点， 您可以通过使用 **本地扩展** 来做到这一点。 Each Flarum installation comes with an `extend.php` file where you can add extender instances, just like in a full extension. 4 | 5 | See our [extension documentation](extend/start.md) for more information about extenders (and even an [example of a local extender](extend/start.md#hello-world)). 6 | 7 | If you need to create new files (when adding a custom class to be imported for extenders), you'll need to adjust your composer.json a bit. Add the following: 8 | 9 | ```json 10 | "autoload": { 11 | "psr-4": { 12 | "App\\": "app/" 13 | } 14 | }, 15 | ``` 16 | 17 | Now you can create new PHP files in an `app` subdirectory using the `App\...` namespace. 18 | 19 | :::tip Local Extenders vs Extensions 20 | 21 | Local extenders can be good for small tweaks, but if you need large customizations, an extension might be a better choice: a separate codebase, cleaner handling of many files, developer tooling, and the ability to easily open source are big benefits. 22 | 23 | ::: 24 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/version-1.x/extenders.md: -------------------------------------------------------------------------------- 1 | # 本地扩展 2 | 3 | 如果您想要在没有分发整个扩展的情况下自定义您的站点， 您可以通过使用 **本地扩展** 来做到这一点。 Each Flarum installation comes with an `extend.php` file where you can add extender instances, just like in a full extension. 4 | 5 | See our [extension documentation](extend/start.md) for more information about extenders (and even an [example of a local extender](extend/start.md#hello-world)). 6 | 7 | If you need to create new files (when adding a custom class to be imported for extenders), you'll need to adjust your composer.json a bit. Add the following: 8 | 9 | ```json 10 | "autoload": { 11 | "psr-4": { 12 | "App\\": "app/" 13 | } 14 | }, 15 | ``` 16 | 17 | Now you can create new PHP files in an `app` subdirectory using the `App\...` namespace. 18 | 19 | :::tip Local Extenders vs Extensions 20 | 21 | Local extenders can be good for small tweaks, but if you need large customizations, an extension might be a better choice: a separate codebase, cleaner handling of many files, developer tooling, and the ability to easily open source are big benefits. 22 | 23 | ::: 24 | -------------------------------------------------------------------------------- /versioned_docs/version-1.x/extend/assets.md: -------------------------------------------------------------------------------- 1 | # Extension Assets 2 | 3 | Some extensions might want to include assets like images or JSON files in their source code (note that this is not the same as uploads, which would probably require a [filesystem disk](filesystem.md)). 4 | 5 | This is actually very easy to do. Just create an `assets` folder at the root of your extension, and place any asset files there. 6 | Flarum will then automatically copy those files to its own `assets` directory (or other storage location if [one is offered by extensions](filesystem.md)) every time the extension is enabled or [`php flarum assets:publish`](../console.md) is executed. 7 | 8 | If using the default storage driver, assets will be available at `https://FORUM_URL/assets/extensions/EXTENSION_ID/file.path`. However, since other extensions might use remote filesystems, we recommend serializing the url to assets you need in the backend. See [Flarum's serialization of the logo and favicon URLs](https://github.com/flarum/framework/blob/4ecd9a9b2ff0e9ba42bb158f3f83bb3ddfc10853/framework/core/src/Api/Serializer/ForumSerializer.php#L85-L86) for an example. 9 | -------------------------------------------------------------------------------- /i18n/de/docusaurus-plugin-content-docs/current/extend/assets.md: -------------------------------------------------------------------------------- 1 | # Extension Assets 2 | 3 | Some extensions might want to include assets like images or JSON files in their source code (note that this is not the same as uploads, which would probably require a [filesystem disk](filesystem.md)). 4 | 5 | This is actually very easy to do. Just create an `assets` folder at the root of your extension, and place any asset files there. Flarum will then automatically copy those files to its own `assets` directory (or other storage location if [one is offered by extensions](filesystem.md)) every time the extension is enabled or [`php flarum assets:publish`](../console.md) is executed. 6 | 7 | If using the default storage driver, assets will be available at `https://FORUM_URL/assets/extensions/EXTENSION_ID/file.path`. However, since other extensions might use remote filesystems, we recommend serializing the url to assets you need in the backend. See [Flarum's serialization of the logo and favicon URLs](https://github.com/flarum/framework/blob/4ecd9a9b2ff0e9ba42bb158f3f83bb3ddfc10853/framework/core/src/Api/Serializer/ForumSerializer.php#L85-L86) for an example. 8 | -------------------------------------------------------------------------------- /i18n/es/docusaurus-plugin-content-docs/current/extend/assets.md: -------------------------------------------------------------------------------- 1 | # Extension Assets 2 | 3 | Some extensions might want to include assets like images or JSON files in their source code (note that this is not the same as uploads, which would probably require a [filesystem disk](filesystem.md)). 4 | 5 | This is actually very easy to do. Just create an `assets` folder at the root of your extension, and place any asset files there. Flarum will then automatically copy those files to its own `assets` directory (or other storage location if [one is offered by extensions](filesystem.md)) every time the extension is enabled or [`php flarum assets:publish`](../console.md) is executed. 6 | 7 | If using the default storage driver, assets will be available at `https://FORUM_URL/assets/extensions/EXTENSION_ID/file.path`. However, since other extensions might use remote filesystems, we recommend serializing the url to assets you need in the backend. See [Flarum's serialization of the logo and favicon URLs](https://github.com/flarum/framework/blob/4ecd9a9b2ff0e9ba42bb158f3f83bb3ddfc10853/framework/core/src/Api/Serializer/ForumSerializer.php#L85-L86) for an example. 8 | -------------------------------------------------------------------------------- /i18n/tr/docusaurus-plugin-content-docs/current/extend/assets.md: -------------------------------------------------------------------------------- 1 | # Extension Assets 2 | 3 | Some extensions might want to include assets like images or JSON files in their source code (note that this is not the same as uploads, which would probably require a [filesystem disk](filesystem.md)). 4 | 5 | This is actually very easy to do. Just create an `assets` folder at the root of your extension, and place any asset files there. Flarum will then automatically copy those files to its own `assets` directory (or other storage location if [one is offered by extensions](filesystem.md)) every time the extension is enabled or [`php flarum assets:publish`](../console.md) is executed. 6 | 7 | If using the default storage driver, assets will be available at `https://FORUM_URL/assets/extensions/EXTENSION_ID/file.path`. However, since other extensions might use remote filesystems, we recommend serializing the url to assets you need in the backend. See [Flarum's serialization of the logo and favicon URLs](https://github.com/flarum/framework/blob/4ecd9a9b2ff0e9ba42bb158f3f83bb3ddfc10853/framework/core/src/Api/Serializer/ForumSerializer.php#L85-L86) for an example. 8 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/current/extend/assets.md: -------------------------------------------------------------------------------- 1 | # Extension Assets 2 | 3 | Some extensions might want to include assets like images or JSON files in their source code (note that this is not the same as uploads, which would probably require a [filesystem disk](filesystem.md)). 4 | 5 | This is actually very easy to do. Just create an `assets` folder at the root of your extension, and place any asset files there. Flarum will then automatically copy those files to its own `assets` directory (or other storage location if [one is offered by extensions](filesystem.md)) every time the extension is enabled or [`php flarum assets:publish`](../console.md) is executed. 6 | 7 | If using the default storage driver, assets will be available at `https://FORUM_URL/assets/extensions/EXTENSION_ID/file.path`. However, since other extensions might use remote filesystems, we recommend serializing the url to assets you need in the backend. See [Flarum's serialization of the logo and favicon URLs](https://github.com/flarum/framework/blob/4ecd9a9b2ff0e9ba42bb158f3f83bb3ddfc10853/framework/core/src/Api/Serializer/ForumSerializer.php#L85-L86) for an example. 8 | -------------------------------------------------------------------------------- /i18n/de/docusaurus-plugin-content-docs/version-1.x/extend/assets.md: -------------------------------------------------------------------------------- 1 | # Extension Assets 2 | 3 | Some extensions might want to include assets like images or JSON files in their source code (note that this is not the same as uploads, which would probably require a [filesystem disk](filesystem.md)). 4 | 5 | This is actually very easy to do. Just create an `assets` folder at the root of your extension, and place any asset files there. Flarum will then automatically copy those files to its own `assets` directory (or other storage location if [one is offered by extensions](filesystem.md)) every time the extension is enabled or [`php flarum assets:publish`](../console.md) is executed. 6 | 7 | If using the default storage driver, assets will be available at `https://FORUM_URL/assets/extensions/EXTENSION_ID/file.path`. However, since other extensions might use remote filesystems, we recommend serializing the url to assets you need in the backend. See [Flarum's serialization of the logo and favicon URLs](https://github.com/flarum/framework/blob/4ecd9a9b2ff0e9ba42bb158f3f83bb3ddfc10853/framework/core/src/Api/Serializer/ForumSerializer.php#L85-L86) for an example. 8 | -------------------------------------------------------------------------------- /i18n/es/docusaurus-plugin-content-docs/version-1.x/extend/assets.md: -------------------------------------------------------------------------------- 1 | # Extension Assets 2 | 3 | Some extensions might want to include assets like images or JSON files in their source code (note that this is not the same as uploads, which would probably require a [filesystem disk](filesystem.md)). 4 | 5 | This is actually very easy to do. Just create an `assets` folder at the root of your extension, and place any asset files there. Flarum will then automatically copy those files to its own `assets` directory (or other storage location if [one is offered by extensions](filesystem.md)) every time the extension is enabled or [`php flarum assets:publish`](../console.md) is executed. 6 | 7 | If using the default storage driver, assets will be available at `https://FORUM_URL/assets/extensions/EXTENSION_ID/file.path`. However, since other extensions might use remote filesystems, we recommend serializing the url to assets you need in the backend. See [Flarum's serialization of the logo and favicon URLs](https://github.com/flarum/framework/blob/4ecd9a9b2ff0e9ba42bb158f3f83bb3ddfc10853/framework/core/src/Api/Serializer/ForumSerializer.php#L85-L86) for an example. 8 | -------------------------------------------------------------------------------- /i18n/tr/docusaurus-plugin-content-docs/version-1.x/extend/assets.md: -------------------------------------------------------------------------------- 1 | # Extension Assets 2 | 3 | Some extensions might want to include assets like images or JSON files in their source code (note that this is not the same as uploads, which would probably require a [filesystem disk](filesystem.md)). 4 | 5 | This is actually very easy to do. Just create an `assets` folder at the root of your extension, and place any asset files there. Flarum will then automatically copy those files to its own `assets` directory (or other storage location if [one is offered by extensions](filesystem.md)) every time the extension is enabled or [`php flarum assets:publish`](../console.md) is executed. 6 | 7 | If using the default storage driver, assets will be available at `https://FORUM_URL/assets/extensions/EXTENSION_ID/file.path`. However, since other extensions might use remote filesystems, we recommend serializing the url to assets you need in the backend. See [Flarum's serialization of the logo and favicon URLs](https://github.com/flarum/framework/blob/4ecd9a9b2ff0e9ba42bb158f3f83bb3ddfc10853/framework/core/src/Api/Serializer/ForumSerializer.php#L85-L86) for an example. 8 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/version-1.x/extend/assets.md: -------------------------------------------------------------------------------- 1 | # Extension Assets 2 | 3 | Some extensions might want to include assets like images or JSON files in their source code (note that this is not the same as uploads, which would probably require a [filesystem disk](filesystem.md)). 4 | 5 | This is actually very easy to do. Just create an `assets` folder at the root of your extension, and place any asset files there. Flarum will then automatically copy those files to its own `assets` directory (or other storage location if [one is offered by extensions](filesystem.md)) every time the extension is enabled or [`php flarum assets:publish`](../console.md) is executed. 6 | 7 | If using the default storage driver, assets will be available at `https://FORUM_URL/assets/extensions/EXTENSION_ID/file.path`. However, since other extensions might use remote filesystems, we recommend serializing the url to assets you need in the backend. See [Flarum's serialization of the logo and favicon URLs](https://github.com/flarum/framework/blob/4ecd9a9b2ff0e9ba42bb158f3f83bb3ddfc10853/framework/core/src/Api/Serializer/ForumSerializer.php#L85-L86) for an example. 8 | -------------------------------------------------------------------------------- /i18n/vi/docusaurus-plugin-content-docs/current/extend/assets.md: -------------------------------------------------------------------------------- 1 | # Assets Tiện ích mở rộng 2 | 3 | Một số tiện ích mở rộng có thể muốn bao gồm các nội dung như hình ảnh hoặc tệp JSON trong mã nguồn của chúng (lưu ý rằng điều này không giống với tệp tải lên, có thể sẽ yêu cầu [đĩa filesystem](filesystem.md)). 4 | 5 | This is actually very easy to do. Just create an `assets` folder at the root of your extension, and place any asset files there. Flarum will then automatically copy those files to its own `assets` directory (or other storage location if [one is offered by extensions](filesystem.md)) every time the extension is enabled or [`php flarum assets:publish`](../console.md) is executed. 6 | 7 | If using the default storage driver, assets will be available at `https://FORUM_URL/assets/extensions/EXTENSION_ID/file.path`. However, since other extensions might use remote filesystems, we recommend serializing the url to assets you need in the backend. See [Flarum's serialization of the logo and favicon URLs](https://github.com/flarum/framework/blob/4ecd9a9b2ff0e9ba42bb158f3f83bb3ddfc10853/framework/core/src/Api/Serializer/ForumSerializer.php#L85-L86) for an example. 8 | -------------------------------------------------------------------------------- /i18n/vi/docusaurus-plugin-content-docs/version-1.x/extend/assets.md: -------------------------------------------------------------------------------- 1 | # Assets Tiện ích mở rộng 2 | 3 | Một số tiện ích mở rộng có thể muốn bao gồm các nội dung như hình ảnh hoặc tệp JSON trong mã nguồn của chúng (lưu ý rằng điều này không giống với tệp tải lên, có thể sẽ yêu cầu [đĩa filesystem](filesystem.md)). 4 | 5 | This is actually very easy to do. Just create an `assets` folder at the root of your extension, and place any asset files there. Flarum will then automatically copy those files to its own `assets` directory (or other storage location if [one is offered by extensions](filesystem.md)) every time the extension is enabled or [`php flarum assets:publish`](../console.md) is executed. 6 | 7 | If using the default storage driver, assets will be available at `https://FORUM_URL/assets/extensions/EXTENSION_ID/file.path`. However, since other extensions might use remote filesystems, we recommend serializing the url to assets you need in the backend. See [Flarum's serialization of the logo and favicon URLs](https://github.com/flarum/framework/blob/4ecd9a9b2ff0e9ba42bb158f3f83bb3ddfc10853/framework/core/src/Api/Serializer/ForumSerializer.php#L85-L86) for an example. 8 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/current/config.md: -------------------------------------------------------------------------------- 1 | # 配置文件 2 | 3 | 除数据库外，只有一处配置是无法通过后台管理面板修改的，那就是位于 Flarum 安装根目录下的 `config.php` 文件。 4 | 5 | 虽然这个文件很小，但包含了 Flarum 安装时至关重要的信息。 6 | 7 | 如果存在这个文件，Flarum 就知道它自己已经被安装了。 另外这个文件还为 Flarum 提供数据库信息等内容。 8 | 9 | 下面是一个示例文件，我们来了解一下所有内容的含义： 10 | 11 | ```php 12 | false, // 启用或禁用调试模式，用于排查问题 14 | 'offline' => false, // 启用或禁用网站维护模式。这使得所有用户(包括管理员)无法访问您的网站。 15 | 'database' => 16 | array ( 17 | 'driver' => 'mysql', // 数据库驱动，例如 MySQL, MariaDB …… 18 | 'host' => 'localhost', // 连接的主机，除非使用外部服务，否则多数情况下是 localhost 19 | 'database' => 'flarum', // 数据库实例名 20 | 'username' => 'root', // 数据库用户名 21 | 'password' => '', // 数据库密码 22 | 'charset' => 'utf8mb4', 23 | 'collation' => 'utf8mb4_unicode_ci', 24 | 'prefix' => '', // 数据表的前缀，如果您和其他服务共享一个数据库，那么添加前缀会很有用 25 | 'port' => '3306', // 连接数据库的端口，MySQL 默认为 3306 26 | 'strict' => false, 27 | ), 28 | 'url' => 'https://flarum.localhost', // URL 配置，如果您改变了域名，您需要变更这个 29 | 'paths' => 30 | array ( 31 | 'api' => 'api', // /api 跳转到 API 32 | 'admin' => 'admin', // /admin 跳转到 admin 33 | ), 34 | ); 35 | ``` 36 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/version-1.x/config.md: -------------------------------------------------------------------------------- 1 | # 配置文件 2 | 3 | 除数据库外，只有一处配置是无法通过后台管理面板修改的，那就是位于 Flarum 安装根目录下的 `config.php` 文件。 4 | 5 | 虽然这个文件很小，但包含了 Flarum 安装时至关重要的信息。 6 | 7 | 如果存在这个文件，Flarum 就知道它自己已经被安装了。 另外这个文件还为 Flarum 提供数据库信息等内容。 8 | 9 | 下面是一个示例文件，我们来了解一下所有内容的含义： 10 | 11 | ```php 12 | false, // 启用或禁用调试模式，用于排查问题 14 | 'offline' => false, // 启用或禁用网站维护模式。这使得所有用户(包括管理员)无法访问您的网站。 15 | 'database' => 16 | array ( 17 | 'driver' => 'mysql', // 数据库驱动，例如 MySQL, MariaDB …… 18 | 'host' => 'localhost', // 连接的主机，除非使用外部服务，否则多数情况下是 localhost 19 | 'database' => 'flarum', // 数据库实例名 20 | 'username' => 'root', // 数据库用户名 21 | 'password' => '', // 数据库密码 22 | 'charset' => 'utf8mb4', 23 | 'collation' => 'utf8mb4_unicode_ci', 24 | 'prefix' => '', // 数据表的前缀，如果您和其他服务共享一个数据库，那么添加前缀会很有用 25 | 'port' => '3306', // 连接数据库的端口，MySQL 默认为 3306 26 | 'strict' => false, 27 | ), 28 | 'url' => 'https://flarum.localhost', // URL 配置，如果您改变了域名，您需要变更这个 29 | 'paths' => 30 | array ( 31 | 'api' => 'api', // /api 跳转到 API 32 | 'admin' => 'admin', // /admin 跳转到 admin 33 | ), 34 | ); 35 | ``` 36 | -------------------------------------------------------------------------------- /docs/extenders.md: -------------------------------------------------------------------------------- 1 | # Local Extenders 2 | 3 | If there are customizations you want to make to your site without distributing an entire extension, you can do so by using **local extenders**. Each Flarum installation comes with an `extend.php` file where you can add extender instances, just like in a full extension. 4 | 5 | See our [extension documentation](extend/start.md) for more information about extenders (and even an [example of a local extender](extend/start.md#hello-world)). 6 | 7 | If you need to create new files (when adding a custom class to be imported for extenders), you'll need to adjust your composer.json a bit. 8 | Add the following: 9 | 10 | ```json 11 | "autoload": { 12 | "psr-4": { 13 | "App\\": "app/" 14 | } 15 | }, 16 | ``` 17 | 18 | Now you can create new PHP files in an `app` subdirectory using the `App\...` namespace. 19 | 20 | :::tip Local Extenders vs Extensions 21 | 22 | Local extenders can be good for small tweaks, but if you need large customizations, an extension might be a better choice: 23 | a separate codebase, cleaner handling of many files, developer tooling, and the ability to easily open source are big benefits. 24 | 25 | ::: 26 | -------------------------------------------------------------------------------- /docs/extend/theme.md: -------------------------------------------------------------------------------- 1 | # Themes 2 | 3 | Flarum "themes" are just extensions. Typically, you'll want to use the `Frontend` extender to register custom [Less](https://lesscss.org/#overview) and JS. 4 | Of course, you can use other extenders too: for example, you might want to support settings to allow configuring your theme. 5 | 6 | You can indicate that your extension is a theme by setting the "extra.flarum-extension.category" key to "theme". For example: 7 | 8 | ```json 9 | { 10 | // other fields 11 | "extra": { 12 | "flarum-extension": { 13 | "category": "theme" 14 | } 15 | } 16 | // other fields 17 | } 18 | ``` 19 | 20 | All this will do is show your extension in the "theme" section in the admin dashboard extension list. 21 | 22 | ## Less Variable Customization 23 | 24 | You can define new Less variables in your extension's Less files. There currently isn't an extender to modify Less variable values in the PHP layer, but this is planned for future releases. 25 | 26 | ## Switching Between Themes 27 | 28 | Flarum doesn't currently have a comprehensive system that would support switching between themes. This is planned for future releases. 29 | -------------------------------------------------------------------------------- /srxDefault.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 |
4 | 5 | 6 | 7 |
8 | 9 | 10 | 11 | 12 | 13 | //.*\n 14 | 15 | 16 | 17 | 18 | 19 | // 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | -------------------------------------------------------------------------------- /src/assets/lifebuoy.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | -------------------------------------------------------------------------------- /versioned_docs/version-1.x/extenders.md: -------------------------------------------------------------------------------- 1 | # Local Extenders 2 | 3 | If there are customizations you want to make to your site without distributing an entire extension, you can do so by using **local extenders**. Each Flarum installation comes with an `extend.php` file where you can add extender instances, just like in a full extension. 4 | 5 | See our [extension documentation](extend/start.md) for more information about extenders (and even an [example of a local extender](extend/start.md#hello-world)). 6 | 7 | If you need to create new files (when adding a custom class to be imported for extenders), you'll need to adjust your composer.json a bit. 8 | Add the following: 9 | 10 | ```json 11 | "autoload": { 12 | "psr-4": { 13 | "App\\": "app/" 14 | } 15 | }, 16 | ``` 17 | 18 | Now you can create new PHP files in an `app` subdirectory using the `App\...` namespace. 19 | 20 | :::tip Local Extenders vs Extensions 21 | 22 | Local extenders can be good for small tweaks, but if you need large customizations, an extension might be a better choice: 23 | a separate codebase, cleaner handling of many files, developer tooling, and the ability to easily open source are big benefits. 24 | 25 | ::: 26 | -------------------------------------------------------------------------------- /versioned_docs/version-1.x/extend/theme.md: -------------------------------------------------------------------------------- 1 | # Themes 2 | 3 | Flarum "themes" are just extensions. Typically, you'll want to use the `Frontend` extender to register custom [Less](https://lesscss.org/#overview) and JS. 4 | Of course, you can use other extenders too: for example, you might want to support settings to allow configuring your theme. 5 | 6 | You can indicate that your extension is a theme by setting the "extra.flarum-extension.category" key to "theme". For example: 7 | 8 | ```json 9 | { 10 | // other fields 11 | "extra": { 12 | "flarum-extension": { 13 | "category": "theme" 14 | } 15 | } 16 | // other fields 17 | } 18 | ``` 19 | 20 | All this will do is show your extension in the "theme" section in the admin dashboard extension list. 21 | 22 | ## Less Variable Customization 23 | 24 | You can define new Less variables in your extension's Less files. There currently isn't an extender to modify Less variable values in the PHP layer, but this is planned for future releases. 25 | 26 | ## Switching Between Themes 27 | 28 | Flarum doesn't currently have a comprehensive system that would support switching between themes. This is planned for future releases. 29 | -------------------------------------------------------------------------------- /i18n/es/docusaurus-plugin-content-docs/current/extenders.md: -------------------------------------------------------------------------------- 1 | # Local Extenders 2 | 3 | If there are customizations you want to make to your site without distributing an entire extension, you can do so by using **local extenders**. Each Flarum installation comes with an `extend.php` file where you can add extender instances, just like in a full extension. 4 | 5 | See our [extension documentation](extend/start.md) for more information about extenders (and even an [example of a local extender](extend/start.md#hello-world)). 6 | 7 | If you need to create new files (when adding a custom class to be imported for extenders), you'll need to adjust your composer.json a bit. Add the following: 8 | 9 | ```json 10 | "autoload": { 11 | "psr-4": { 12 | "App\\": "app/" 13 | } 14 | }, 15 | ``` 16 | 17 | Now you can create new PHP files in an `app` subdirectory using the `App\...` namespace. 18 | 19 | :::tip Local Extenders vs Extensions 20 | 21 | Local extenders can be good for small tweaks, but if you need large customizations, an extension might be a better choice: a separate codebase, cleaner handling of many files, developer tooling, and the ability to easily open source are big benefits. 22 | 23 | ::: 24 | -------------------------------------------------------------------------------- /i18n/it/docusaurus-plugin-content-docs/current/extenders.md: -------------------------------------------------------------------------------- 1 | # Local Extenders 2 | 3 | If there are customizations you want to make to your site without distributing an entire extension, you can do so by using **local extenders**. Each Flarum installation comes with an `extend.php` file where you can add extender instances, just like in a full extension. 4 | 5 | See our [extension documentation](extend/start.md) for more information about extenders (and even an [example of a local extender](extend/start.md#hello-world)). 6 | 7 | If you need to create new files (when adding a custom class to be imported for extenders), you'll need to adjust your composer.json a bit. Add the following: 8 | 9 | ```json 10 | "autoload": { 11 | "psr-4": { 12 | "App\\": "app/" 13 | } 14 | }, 15 | ``` 16 | 17 | Now you can create new PHP files in an `app` subdirectory using the `App\...` namespace. 18 | 19 | :::tip Local Extenders vs Extensions 20 | 21 | Local extenders can be good for small tweaks, but if you need large customizations, an extension might be a better choice: a separate codebase, cleaner handling of many files, developer tooling, and the ability to easily open source are big benefits. 22 | 23 | ::: 24 | -------------------------------------------------------------------------------- /i18n/es/docusaurus-plugin-content-docs/version-1.x/extenders.md: -------------------------------------------------------------------------------- 1 | # Local Extenders 2 | 3 | If there are customizations you want to make to your site without distributing an entire extension, you can do so by using **local extenders**. Each Flarum installation comes with an `extend.php` file where you can add extender instances, just like in a full extension. 4 | 5 | See our [extension documentation](extend/start.md) for more information about extenders (and even an [example of a local extender](extend/start.md#hello-world)). 6 | 7 | If you need to create new files (when adding a custom class to be imported for extenders), you'll need to adjust your composer.json a bit. Add the following: 8 | 9 | ```json 10 | "autoload": { 11 | "psr-4": { 12 | "App\\": "app/" 13 | } 14 | }, 15 | ``` 16 | 17 | Now you can create new PHP files in an `app` subdirectory using the `App\...` namespace. 18 | 19 | :::tip Local Extenders vs Extensions 20 | 21 | Local extenders can be good for small tweaks, but if you need large customizations, an extension might be a better choice: a separate codebase, cleaner handling of many files, developer tooling, and the ability to easily open source are big benefits. 22 | 23 | ::: 24 | -------------------------------------------------------------------------------- /i18n/it/docusaurus-plugin-content-docs/version-1.x/extenders.md: -------------------------------------------------------------------------------- 1 | # Local Extenders 2 | 3 | If there are customizations you want to make to your site without distributing an entire extension, you can do so by using **local extenders**. Each Flarum installation comes with an `extend.php` file where you can add extender instances, just like in a full extension. 4 | 5 | See our [extension documentation](extend/start.md) for more information about extenders (and even an [example of a local extender](extend/start.md#hello-world)). 6 | 7 | If you need to create new files (when adding a custom class to be imported for extenders), you'll need to adjust your composer.json a bit. Add the following: 8 | 9 | ```json 10 | "autoload": { 11 | "psr-4": { 12 | "App\\": "app/" 13 | } 14 | }, 15 | ``` 16 | 17 | Now you can create new PHP files in an `app` subdirectory using the `App\...` namespace. 18 | 19 | :::tip Local Extenders vs Extensions 20 | 21 | Local extenders can be good for small tweaks, but if you need large customizations, an extension might be a better choice: a separate codebase, cleaner handling of many files, developer tooling, and the ability to easily open source are big benefits. 22 | 23 | ::: 24 | -------------------------------------------------------------------------------- /i18n/tr/docusaurus-plugin-content-docs/current/extenders.md: -------------------------------------------------------------------------------- 1 | # Yerel Genişleticiler 2 | 3 | If there are customizations you want to make to your site without distributing an entire extension, you can do so by using **local extenders**. Each Flarum installation comes with an `extend.php` file where you can add extender instances, just like in a full extension. 4 | 5 | See our [extension documentation](extend/start.md) for more information about extenders (and even an [example of a local extender](extend/start.md#hello-world)). 6 | 7 | If you need to create new files (when adding a custom class to be imported for extenders), you'll need to adjust your composer.json a bit. Add the following: 8 | 9 | ```json 10 | "autoload": { 11 | "psr-4": { 12 | "App\\": "app/" 13 | } 14 | }, 15 | ``` 16 | 17 | Now you can create new PHP files in an `app` subdirectory using the `App\...` namespace. 18 | 19 | :::tip Local Extenders vs Extensions 20 | 21 | Local extenders can be good for small tweaks, but if you need large customizations, an extension might be a better choice: a separate codebase, cleaner handling of many files, developer tooling, and the ability to easily open source are big benefits. 22 | 23 | ::: 24 | -------------------------------------------------------------------------------- /i18n/de/docusaurus-plugin-content-docs/current/extend/theme.md: -------------------------------------------------------------------------------- 1 | # Themes 2 | 3 | Flarum "themes" are just extensions. Typically, you'll want to use the `Frontend` extender to register custom [Less](https://lesscss.org/#overview) and JS. Of course, you can use other extenders too: for example, you might want to support settings to allow configuring your theme. 4 | 5 | You can indicate that your extension is a theme by setting the "extra.flarum-extension.category" key to "theme". For example: 6 | 7 | ```json 8 | { 9 | // other fields 10 | "extra": { 11 | "flarum-extension": { 12 | "category": "theme" 13 | } 14 | } 15 | // other fields 16 | } 17 | ``` 18 | 19 | All this will do is show your extension in the "theme" section in the admin dashboard extension list. 20 | 21 | ## Less Variable Customization 22 | 23 | You can define new Less variables in your extension's Less files. There currently isn't an extender to modify Less variable values in the PHP layer, but this is planned for future releases. 24 | 25 | ## Switching Between Themes 26 | 27 | Flarum doesn't currently have a comprehensive system that would support switching between themes. This is planned for future releases. 28 | -------------------------------------------------------------------------------- /i18n/tr/docusaurus-plugin-content-docs/version-1.x/extenders.md: -------------------------------------------------------------------------------- 1 | # Yerel Genişleticiler 2 | 3 | If there are customizations you want to make to your site without distributing an entire extension, you can do so by using **local extenders**. Each Flarum installation comes with an `extend.php` file where you can add extender instances, just like in a full extension. 4 | 5 | See our [extension documentation](extend/start.md) for more information about extenders (and even an [example of a local extender](extend/start.md#hello-world)). 6 | 7 | If you need to create new files (when adding a custom class to be imported for extenders), you'll need to adjust your composer.json a bit. Add the following: 8 | 9 | ```json 10 | "autoload": { 11 | "psr-4": { 12 | "App\\": "app/" 13 | } 14 | }, 15 | ``` 16 | 17 | Now you can create new PHP files in an `app` subdirectory using the `App\...` namespace. 18 | 19 | :::tip Local Extenders vs Extensions 20 | 21 | Local extenders can be good for small tweaks, but if you need large customizations, an extension might be a better choice: a separate codebase, cleaner handling of many files, developer tooling, and the ability to easily open source are big benefits. 22 | 23 | ::: 24 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/current/extend/theme.md: -------------------------------------------------------------------------------- 1 | # Themes 2 | 3 | Flarum "themes" are just extensions. Typically, you'll want to use the `Frontend` extender to register custom [Less](https://lesscss.org/#overview) and JS. Of course, you can use other extenders too: for example, you might want to support settings to allow configuring your theme. 4 | 5 | You can indicate that your extension is a theme by setting the "extra.flarum-extension.category" key to "theme". For example: 6 | 7 | ```json 8 | { 9 | // other fields 10 | "extra": { 11 | "flarum-extension": { 12 | "category": "theme" 13 | } 14 | } 15 | // other fields 16 | } 17 | ``` 18 | 19 | All this will do is show your extension in the "theme" section in the admin dashboard extension list. 20 | 21 | ## Less Variable Customization 22 | 23 | You can define new Less variables in your extension's Less files. There currently isn't an extender to modify Less variable values in the PHP layer, but this is planned for future releases. 24 | 25 | ## Switching Between Themes 26 | 27 | Flarum doesn't currently have a comprehensive system that would support switching between themes. This is planned for future releases. 28 | -------------------------------------------------------------------------------- /i18n/de/docusaurus-plugin-content-docs/version-1.x/extend/theme.md: -------------------------------------------------------------------------------- 1 | # Themes 2 | 3 | Flarum "themes" are just extensions. Typically, you'll want to use the `Frontend` extender to register custom [Less](https://lesscss.org/#overview) and JS. Of course, you can use other extenders too: for example, you might want to support settings to allow configuring your theme. 4 | 5 | You can indicate that your extension is a theme by setting the "extra.flarum-extension.category" key to "theme". For example: 6 | 7 | ```json 8 | { 9 | // other fields 10 | "extra": { 11 | "flarum-extension": { 12 | "category": "theme" 13 | } 14 | } 15 | // other fields 16 | } 17 | ``` 18 | 19 | All this will do is show your extension in the "theme" section in the admin dashboard extension list. 20 | 21 | ## Less Variable Customization 22 | 23 | You can define new Less variables in your extension's Less files. There currently isn't an extender to modify Less variable values in the PHP layer, but this is planned for future releases. 24 | 25 | ## Switching Between Themes 26 | 27 | Flarum doesn't currently have a comprehensive system that would support switching between themes. This is planned for future releases. 28 | -------------------------------------------------------------------------------- /i18n/it/docusaurus-plugin-content-docs/current/extend/theme.md: -------------------------------------------------------------------------------- 1 | # Guida rapida 2 | 3 | Flarum "themes" are just extensions. Typically, you'll want to use the `Frontend` extender to register custom [Less](https://lesscss.org/#overview) and JS. Of course, you can use other extenders too: for example, you might want to support settings to allow configuring your theme. 4 | 5 | You can indicate that your extension is a theme by setting the "extra.flarum-extension.category" key to "theme". Per esempio: 6 | 7 | ```json 8 | { 9 | // other fields 10 | "extra": { 11 | "flarum-extension": { 12 | "category": "theme" 13 | } 14 | } 15 | // other fields 16 | } 17 | ``` 18 | 19 | All this will do is show your extension in the "theme" section in the admin dashboard extension list. 20 | 21 | ## Less Variable Customization 22 | 23 | You can define new Less variables in your extension's Less files. There currently isn't an extender to modify Less variable values in the PHP layer, but this is planned for future releases. 24 | 25 | ## Switching Between Themes 26 | 27 | Flarum doesn't currently have a comprehensive system that would support switching between themes. This is planned for future releases. 28 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/current/bugs.md: -------------------------------------------------------------------------------- 1 | # 反馈 Bug 2 | 3 | :::danger 安全漏洞 4 | 5 | 如果您发现 Flarum 存在安全漏洞，请遵循我们的[安全政策](https://github.com/flarum/core/security/policy)，我们会及时处理 6 | 7 | ::: 8 | 9 | 感谢您帮助我们测试 Flarum！ 我们很高兴让您加入这个队伍！ 我们需要可以*排除问题*和*清晰地沟通*的人。 您可能知道，优秀的错误报告需要花费一些时间和精力。 如果您可以做到这些，那让我们开始吧！ 10 | 11 | ## 重复项 12 | 13 | 已经发现了 Bug？ 太棒了！ 我们很乐意听到关于它的消息— 但首先您应该检查一下相关情况，以确保您不会在一个已知问题上浪费时间： 14 | 15 | - 搜索我们的 [支持论坛](https://discuss.flarum.org/t/support) 来查看它是否已经报告。 16 | - 我们也可能正在进行修复，所以也请搜索我们的 [问题跟踪器](https://github.com/flarum/core/issues)。 17 | 18 | 在 *彻底地*搜索一番后，如果无人报告该问题，欢迎您提交报告。 如果只是一个简单的小问题（例如单词拼写问题或图像问题），请直接跳到下一节。 但如果您看到错误，或者它已经明显损坏，我们需要您先收集一些信息。 请跳转到我们的 [故障排除](troubleshoot.md) 指南并遵循那里的指引。 请收集尽可能多的信息！ 19 | 20 | ## 报告 21 | 22 | 我们在GitHub上跟踪问题。 请您确保在 [正确的仓库](https://github.com/flarum) 创建问题（Issue），并填写模版中的所有内容。 23 | 24 | 如果可以，请检查最新版本的 Flarum 是否可以重现该问题。 如果您使用的是预发布版本或开发版本，请指出您正在使用的版本。 25 | 26 | 记住：错误报告的目的是让我们轻松地重现并修复它。 您可能需要阅读 [这篇文章](https://www.chiark.greenend.org.uk/~sgtatham/bugs.html)，了解如何撰写有效的错误报告。 请您 **务必** 清晰描述重现问题的必要步骤。 没有明确重现步骤的问题将不会被标记/分类。 如果一个标记为「需要验证（needs verification）」的问题从被标记开始 5 天内创建者没有进一步反馈信息，该问题将被关闭。 27 | 28 | 一旦您提交了报告，请您 *持续关注* 并耐心等待。 我们可能需要要求进一步的细节或说明。 但我们总是有很多事情要做，所以我们可能需要一段时间才会处理您的报告。 29 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/version-1.x/extend/theme.md: -------------------------------------------------------------------------------- 1 | # Themes 2 | 3 | Flarum "themes" are just extensions. Typically, you'll want to use the `Frontend` extender to register custom [Less](https://lesscss.org/#overview) and JS. Of course, you can use other extenders too: for example, you might want to support settings to allow configuring your theme. 4 | 5 | You can indicate that your extension is a theme by setting the "extra.flarum-extension.category" key to "theme". For example: 6 | 7 | ```json 8 | { 9 | // other fields 10 | "extra": { 11 | "flarum-extension": { 12 | "category": "theme" 13 | } 14 | } 15 | // other fields 16 | } 17 | ``` 18 | 19 | All this will do is show your extension in the "theme" section in the admin dashboard extension list. 20 | 21 | ## Less Variable Customization 22 | 23 | You can define new Less variables in your extension's Less files. There currently isn't an extender to modify Less variable values in the PHP layer, but this is planned for future releases. 24 | 25 | ## Switching Between Themes 26 | 27 | Flarum doesn't currently have a comprehensive system that would support switching between themes. This is planned for future releases. 28 | -------------------------------------------------------------------------------- /i18n/es/docusaurus-plugin-content-docs/current/extend/theme.md: -------------------------------------------------------------------------------- 1 | # Inicio rápido 2 | 3 | Flarum "themes" are just extensions. Typically, you'll want to use the `Frontend` extender to register custom [Less](https://lesscss.org/#overview) and JS. Of course, you can use other extenders too: for example, you might want to support settings to allow configuring your theme. 4 | 5 | You can indicate that your extension is a theme by setting the "extra.flarum-extension.category" key to "theme". Por ejemplo: 6 | 7 | ```json 8 | { 9 | // other fields 10 | "extra": { 11 | "flarum-extension": { 12 | "category": "theme" 13 | } 14 | } 15 | // other fields 16 | } 17 | ``` 18 | 19 | All this will do is show your extension in the "theme" section in the admin dashboard extension list. 20 | 21 | ## Less Variable Customization 22 | 23 | You can define new Less variables in your extension's Less files. There currently isn't an extender to modify Less variable values in the PHP layer, but this is planned for future releases. 24 | 25 | ## Switching Between Themes 26 | 27 | Flarum doesn't currently have a comprehensive system that would support switching between themes. This is planned for future releases. 28 | -------------------------------------------------------------------------------- /i18n/es/docusaurus-plugin-content-docs/version-1.x/extend/theme.md: -------------------------------------------------------------------------------- 1 | # Inicio rápido 2 | 3 | Flarum "themes" are just extensions. Typically, you'll want to use the `Frontend` extender to register custom [Less](https://lesscss.org/#overview) and JS. Of course, you can use other extenders too: for example, you might want to support settings to allow configuring your theme. 4 | 5 | You can indicate that your extension is a theme by setting the "extra.flarum-extension.category" key to "theme". Por ejemplo: 6 | 7 | ```json 8 | { 9 | // other fields 10 | "extra": { 11 | "flarum-extension": { 12 | "category": "theme" 13 | } 14 | } 15 | // other fields 16 | } 17 | ``` 18 | 19 | All this will do is show your extension in the "theme" section in the admin dashboard extension list. 20 | 21 | ## Less Variable Customization 22 | 23 | You can define new Less variables in your extension's Less files. There currently isn't an extender to modify Less variable values in the PHP layer, but this is planned for future releases. 24 | 25 | ## Switching Between Themes 26 | 27 | Flarum doesn't currently have a comprehensive system that would support switching between themes. This is planned for future releases. 28 | -------------------------------------------------------------------------------- /i18n/it/docusaurus-plugin-content-docs/version-1.x/extend/theme.md: -------------------------------------------------------------------------------- 1 | # Guida rapida 2 | 3 | Flarum "themes" are just extensions. Typically, you'll want to use the `Frontend` extender to register custom [Less](https://lesscss.org/#overview) and JS. Of course, you can use other extenders too: for example, you might want to support settings to allow configuring your theme. 4 | 5 | You can indicate that your extension is a theme by setting the "extra.flarum-extension.category" key to "theme". Per esempio: 6 | 7 | ```json 8 | { 9 | // other fields 10 | "extra": { 11 | "flarum-extension": { 12 | "category": "theme" 13 | } 14 | } 15 | // other fields 16 | } 17 | ``` 18 | 19 | All this will do is show your extension in the "theme" section in the admin dashboard extension list. 20 | 21 | ## Less Variable Customization 22 | 23 | You can define new Less variables in your extension's Less files. There currently isn't an extender to modify Less variable values in the PHP layer, but this is planned for future releases. 24 | 25 | ## Switching Between Themes 26 | 27 | Flarum doesn't currently have a comprehensive system that would support switching between themes. This is planned for future releases. 28 | -------------------------------------------------------------------------------- /i18n/tr/docusaurus-plugin-content-docs/current/extend/theme.md: -------------------------------------------------------------------------------- 1 | # Hızlı Başlangıç 2 | 3 | Flarum "themes" are just extensions. Typically, you'll want to use the `Frontend` extender to register custom [Less](https://lesscss.org/#overview) and JS. Of course, you can use other extenders too: for example, you might want to support settings to allow configuring your theme. 4 | 5 | You can indicate that your extension is a theme by setting the "extra.flarum-extension.category" key to "theme". For example: 6 | 7 | ```json 8 | { 9 | // other fields 10 | "extra": { 11 | "flarum-extension": { 12 | "category": "theme" 13 | } 14 | } 15 | // other fields 16 | } 17 | ``` 18 | 19 | All this will do is show your extension in the "theme" section in the admin dashboard extension list. 20 | 21 | ## Less Variable Customization 22 | 23 | You can define new Less variables in your extension's Less files. There currently isn't an extender to modify Less variable values in the PHP layer, but this is planned for future releases. 24 | 25 | ## Switching Between Themes 26 | 27 | Flarum doesn't currently have a comprehensive system that would support switching between themes. This is planned for future releases. 28 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/version-1.x/bugs.md: -------------------------------------------------------------------------------- 1 | # 反馈 Bug 2 | 3 | :::danger 安全漏洞 4 | 5 | 如果您发现 Flarum 存在安全漏洞，请遵循我们的[安全政策](https://github.com/flarum/core/security/policy)，我们会及时处理 6 | 7 | ::: 8 | 9 | 感谢您帮助我们测试 Flarum！ 我们很高兴让您加入这个队伍！ 我们需要可以*排除问题*和*清晰地沟通*的人。 您可能知道，优秀的错误报告需要花费一些时间和精力。 如果您可以做到这些，那让我们开始吧！ 10 | 11 | ## 重复项 12 | 13 | 已经发现了 Bug？ 太棒了！ 我们很乐意听到关于它的消息— 但首先您应该检查一下相关情况，以确保您不会在一个已知问题上浪费时间： 14 | 15 | - 搜索我们的 [支持论坛](https://discuss.flarum.org/t/support) 来查看它是否已经报告。 16 | - 我们也可能正在进行修复，所以也请搜索我们的 [问题跟踪器](https://github.com/flarum/core/issues)。 17 | 18 | 在 *彻底地*搜索一番后，如果无人报告该问题，欢迎您提交报告。 如果只是一个简单的小问题（例如单词拼写问题或图像问题），请直接跳到下一节。 但如果您看到错误，或者它已经明显损坏，我们需要您先收集一些信息。 请跳转到我们的 [故障排除](troubleshoot.md) 指南并遵循那里的指引。 请收集尽可能多的信息！ 19 | 20 | ## 报告 21 | 22 | 我们在GitHub上跟踪问题。 请您确保在 [正确的仓库](https://github.com/flarum) 创建问题（Issue），并填写模版中的所有内容。 23 | 24 | 如果可以，请检查最新版本的 Flarum 是否可以重现该问题。 如果您使用的是预发布版本或开发版本，请指出您正在使用的版本。 25 | 26 | 记住：错误报告的目的是让我们轻松地重现并修复它。 您可能需要阅读 [这篇文章](https://www.chiark.greenend.org.uk/~sgtatham/bugs.html)，了解如何撰写有效的错误报告。 请您 **务必** 清晰描述重现问题的必要步骤。 没有明确重现步骤的问题将不会被标记/分类。 如果一个标记为「需要验证（needs verification）」的问题从被标记开始 5 天内创建者没有进一步反馈信息，该问题将被关闭。 27 | 28 | 一旦您提交了报告，请您 *持续关注* 并耐心等待。 我们可能需要要求进一步的细节或说明。 但我们总是有很多事情要做，所以我们可能需要一段时间才会处理您的报告。 29 | -------------------------------------------------------------------------------- /i18n/tr/docusaurus-plugin-content-docs/version-1.x/extend/theme.md: -------------------------------------------------------------------------------- 1 | # Hızlı Başlangıç 2 | 3 | Flarum "themes" are just extensions. Typically, you'll want to use the `Frontend` extender to register custom [Less](https://lesscss.org/#overview) and JS. Of course, you can use other extenders too: for example, you might want to support settings to allow configuring your theme. 4 | 5 | You can indicate that your extension is a theme by setting the "extra.flarum-extension.category" key to "theme". For example: 6 | 7 | ```json 8 | { 9 | // other fields 10 | "extra": { 11 | "flarum-extension": { 12 | "category": "theme" 13 | } 14 | } 15 | // other fields 16 | } 17 | ``` 18 | 19 | All this will do is show your extension in the "theme" section in the admin dashboard extension list. 20 | 21 | ## Less Variable Customization 22 | 23 | You can define new Less variables in your extension's Less files. There currently isn't an extender to modify Less variable values in the PHP layer, but this is planned for future releases. 24 | 25 | ## Switching Between Themes 26 | 27 | Flarum doesn't currently have a comprehensive system that would support switching between themes. This is planned for future releases. 28 | -------------------------------------------------------------------------------- /package.json: -------------------------------------------------------------------------------- 1 | { 2 | "name": "flarum-docs", 3 | "version": "0.0.0", 4 | "private": true, 5 | "scripts": { 6 | "docusaurus": "docusaurus", 7 | "start": "docusaurus start", 8 | "build": "docusaurus build", 9 | "swizzle": "docusaurus swizzle", 10 | "deploy": "docusaurus deploy", 11 | "clear": "docusaurus clear", 12 | "serve": "docusaurus serve", 13 | "write-translations": "docusaurus write-translations", 14 | "write-heading-ids": "docusaurus write-heading-ids" 15 | }, 16 | "dependencies": { 17 | "@docusaurus/core": "^2.3.1", 18 | "@docusaurus/preset-classic": "^2.3.1", 19 | "@docusaurus/theme-search-algolia": "^2.3.1", 20 | "@mdx-js/react": "^1.6.21", 21 | "@svgr/webpack": "^5.5.0", 22 | "clsx": "^1.1.1", 23 | "file-loader": "^6.2.0", 24 | "prism-react-renderer": "^1.2.1", 25 | "react": "^17.0.1", 26 | "react-dom": "^17.0.1", 27 | "url-loader": "^4.1.1" 28 | }, 29 | "browserslist": { 30 | "production": [ 31 | ">0.5%", 32 | "not dead", 33 | "not op_mini all" 34 | ], 35 | "development": [ 36 | "last 1 chrome version", 37 | "last 1 firefox version", 38 | "last 1 safari version" 39 | ] 40 | } 41 | } 42 | -------------------------------------------------------------------------------- /i18n/it/docusaurus-plugin-content-docs/current/extend/assets.md: -------------------------------------------------------------------------------- 1 | # Risorse Estensione 2 | 3 | Alcune estensioni potrebbero voler includere asset come immagini o file JSON nel loro codice sorgente (non si tratta di upload, che richiederebbe probabilmente un apposito [filesystem](filesystem.md)). 4 | 5 | Lavorare con gli asset è in realtà molto semplice. Basta creare una cartella `assets` nella radice principale della tua estensione, e posizionare tutti i file al suo interno. Flarum copierà automaticamente tali file nella propria directory `assets` (o altra posizione di archiviazione se [impostata da un estensione](filesystem.md)) ogni volta che l'estensione è abilitata o [`php flarum assets:publish`](../console.md) viene eseguito. 6 | 7 | Se si utilizza il driver di archiviazione predefinito, le risorse saranno disponibili all'url `https://FORUM_URL/assets/extensions/EXTENSION_ID/file.path`. Tuttavia, poiché altre estensioni potrebbero usare filesystem remoti, si consiglia di serializzare l'url alle risorse di cui hai bisogno nel backend. See [Flarum's serialization of the logo and favicon URLs](https://github.com/flarum/framework/blob/4ecd9a9b2ff0e9ba42bb158f3f83bb3ddfc10853/framework/core/src/Api/Serializer/ForumSerializer.php#L85-L86) for an example. 8 | -------------------------------------------------------------------------------- /i18n/it/docusaurus-plugin-content-docs/version-1.x/extend/assets.md: -------------------------------------------------------------------------------- 1 | # Risorse Estensione 2 | 3 | Alcune estensioni potrebbero voler includere asset come immagini o file JSON nel loro codice sorgente (non si tratta di upload, che richiederebbe probabilmente un apposito [filesystem](filesystem.md)). 4 | 5 | Lavorare con gli asset è in realtà molto semplice. Basta creare una cartella `assets` nella radice principale della tua estensione, e posizionare tutti i file al suo interno. Flarum copierà automaticamente tali file nella propria directory `assets` (o altra posizione di archiviazione se [impostata da un estensione](filesystem.md)) ogni volta che l'estensione è abilitata o [`php flarum assets:publish`](../console.md) viene eseguito. 6 | 7 | Se si utilizza il driver di archiviazione predefinito, le risorse saranno disponibili all'url `https://FORUM_URL/assets/extensions/EXTENSION_ID/file.path`. Tuttavia, poiché altre estensioni potrebbero usare filesystem remoti, si consiglia di serializzare l'url alle risorse di cui hai bisogno nel backend. See [Flarum's serialization of the logo and favicon URLs](https://github.com/flarum/framework/blob/4ecd9a9b2ff0e9ba42bb158f3f83bb3ddfc10853/framework/core/src/Api/Serializer/ForumSerializer.php#L85-L86) for an example. 8 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | The MIT License (MIT) 2 | 3 | Copyright (c) 2019-2022 Stichting Flarum (Flarum Foundation) 4 | Copyright (c) 2014-2019 Toby Zerner (toby.zerner@gmail.com) 5 | 6 | Permission is hereby granted, free of charge, to any person obtaining a copy 7 | of this software and associated documentation files (the "Software"), to deal 8 | in the Software without restriction, including without limitation the rights 9 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 10 | copies of the Software, and to permit persons to whom the Software is 11 | furnished to do so, subject to the following conditions: 12 | 13 | The above copyright notice and this permission notice shall be included in all 14 | copies or substantial portions of the Software. 15 | 16 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 17 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 18 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 19 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 20 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 21 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 22 | SOFTWARE. 23 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/current/faq.md: -------------------------------------------------------------------------------- 1 | # 常见问题 2 | 3 | ### Flarum 现在是正式版吗？ 4 | 5 | 是的！ 经过 6 年的开发之后，Flarum 1.0.0 最终来了。 6 | 7 | ### 展望未来，下一阶段 Flarum 会做些什么？ 8 | 9 | 相应的计划还在制定中。 不过我们已经有了很多很多想法，期待届时在社区中分享给大家。 10 | 11 | ### 我可以捐款以加快开发进展吗？ 12 | 13 | 衷心感谢所有的捐款。 您可以在 [Github Sponsors](https://github.com/sponsors/flarum) 或 [OpenCollective](https://opencollective.com/flarum) 上捐款。 14 | 15 | 但是，捐款并不会直接影响 Flarum 的开发速度。 我们也鼓励用户在其他方面做出贡献，比如 [贡献代码](contributing.md)、[开发扩展](/extend/)、编写文档、将 Flarum 翻译成其他语言，或在 [社区论坛](https://discuss.flarum.org/) 上提供帮助和支持，成为社区里的中坚力量！ 16 | 17 | ### Flarum 会有****的功能吗？ 什么时候有？ 为什么还没做呢？ 18 | 19 | 我们很想让 Flarum 的功能和插件应有尽有、一应俱全，但现阶段，基本功能和稳定性才是重点。 20 | 21 | ### 我可以将 Flarum 与 WordPress/Laravel/等等集成吗？ 22 | 23 | 同样，答案是「要事先为」。 如果我们还没有解决一个 Issue（或给它分配了一个里程碑），那是因为我们正在处理其他同样重要的事情，所以请耐心等待。 我们会尽量在新版本发布前搞定它。 如果您很着急，可以自行修复它 [并为项目做出贡献](contributing.md)！ 24 | 25 | ### 我可以将我的论坛迁移到 Flarum 上吗？ 26 | 27 | 我们目前没有提供官方的迁移工具，但是现在已有很多由社区提供的解决办法。 一旦我们有信心 Flarum 可以用于生产环境，我们将打造从其他论坛软件（例如 esoTalk、FluxBB、phpBB、Discourse等）导入数据的工具。 28 | 29 | ### 我如何加入 Flarum 团队？ 30 | 31 | > “通过一个神秘而艰苦的考验，这涉及了神秘的仪式，危机生命的冒险，以及对有去无回的远方世界的探索。” ~ jordanjay29 32 | 33 | 好了，认真地说，我们一般都会留意社区里出类拔萃的成员，他们或许能够成为优秀的员工。 就拿我们目前的多数员工来说，他们现在做的事情与成为正式员工前没有什么两样。 34 | 35 | 因此，找到属于您的激情，并以您觉得最好的方式做出贡献。 然后顺其自然。 在这，没有勋章也能让您受到尊重。 -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/version-1.x/faq.md: -------------------------------------------------------------------------------- 1 | # 常见问题 2 | 3 | ### Flarum 现在是正式版吗？ 4 | 5 | 是的！ 经过 6 年的开发之后，Flarum 1.0.0 最终来了。 6 | 7 | ### 展望未来，下一阶段 Flarum 会做些什么？ 8 | 9 | 相应的计划还在制定中。 不过我们已经有了很多很多想法，期待届时在社区中分享给大家。 10 | 11 | ### 我可以捐款以加快开发进展吗？ 12 | 13 | 衷心感谢所有的捐款。 您可以在 [Github Sponsors](https://github.com/sponsors/flarum) 或 [OpenCollective](https://opencollective.com/flarum) 上捐款。 14 | 15 | 但是，捐款并不会直接影响 Flarum 的开发速度。 我们也鼓励用户在其他方面做出贡献，比如 [贡献代码](contributing.md)、[开发扩展](/extend/)、编写文档、将 Flarum 翻译成其他语言，或在 [社区论坛](https://discuss.flarum.org/) 上提供帮助和支持，成为社区里的中坚力量！ 16 | 17 | ### Flarum 会有****的功能吗？ 什么时候有？ 为什么还没做呢？ 18 | 19 | 我们很想让 Flarum 的功能和插件应有尽有、一应俱全，但现阶段，基本功能和稳定性才是重点。 20 | 21 | ### 我可以将 Flarum 与 WordPress/Laravel/等等集成吗？ 22 | 23 | 同样，答案是「要事先为」。 如果我们还没有解决一个 Issue（或给它分配了一个里程碑），那是因为我们正在处理其他同样重要的事情，所以请耐心等待。 我们会尽量在新版本发布前搞定它。 如果您很着急，可以自行修复它 [并为项目做出贡献](contributing.md)！ 24 | 25 | ### 我可以将我的论坛迁移到 Flarum 上吗？ 26 | 27 | 我们目前没有提供官方的迁移工具，但是现在已有很多由社区提供的解决办法。 一旦我们有信心 Flarum 可以用于生产环境，我们将打造从其他论坛软件（例如 esoTalk、FluxBB、phpBB、Discourse等）导入数据的工具。 28 | 29 | ### 我如何加入 Flarum 团队？ 30 | 31 | > “通过一个神秘而艰苦的考验，这涉及了神秘的仪式，危机生命的冒险，以及对有去无回的远方世界的探索。” ~ jordanjay29 32 | 33 | 好了，认真地说，我们一般都会留意社区里出类拔萃的成员，他们或许能够成为优秀的员工。 就拿我们目前的多数员工来说，他们现在做的事情与成为正式员工前没有什么两样。 34 | 35 | 因此，找到属于您的激情，并以您觉得最好的方式做出贡献。 然后顺其自然。 在这，没有勋章也能让您受到尊重。 -------------------------------------------------------------------------------- /src/assets/cog-6-tooth.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | -------------------------------------------------------------------------------- /i18n/vi/docusaurus-plugin-content-docs/current/extenders.md: -------------------------------------------------------------------------------- 1 | # Bộ mở rộng cục bộ 2 | 3 | Nếu có các tùy chỉnh bạn muốn thực hiện cho trang web của mình mà không phân phối toàn bộ tiện ích mở rộng, bạn có thể làm như vậy bằng cách sử dụng **bộ mở rộng cục bộ**. Mỗi bản cài đặt Flarum đều đi kèm với một tệp `extend.php` nơi bạn có thể thêm các đối tượng bộ mở rộng, giống như trong một phần mở rộng đầy đủ. 4 | 5 | Xem [tài liệu mở rộng của chúng tôi](extend/start.md) để biết thêm thông tin về bộ mở rộng (và cả [ví dụ về bộ mở rộng cục bộ](extend/start.md#hello-world)). 6 | 7 | Nếu bạn cần tạo tệp mới (khi thêm class tùy chỉnh được nhập cho bộ mở rộng), bạn sẽ cần điều chỉnh composer.json của mình một chút. Thêm những dòng sau: 8 | 9 | ```json 10 | "autoload": { 11 | "psr-4": { 12 | "App\\": "app/" 13 | } 14 | }, 15 | ``` 16 | 17 | Giờ đây, bạn có thể tạo các tệp PHP mới trong thư mục con `ứng dụng` bằng cách sử dụng namespace `App\...`. 18 | 19 | :::tip Bộ mở rộng cục bộ với Tiện ích mở rộng 20 | 21 | Các bộ mở rộng cục bộ có thể tốt cho các chỉnh sửa nhỏ, nhưng nếu bạn cần các tùy chỉnh lớn, một tiện ích mở rộng có thể là lựa chọn tốt hơn: một cơ sở mã riêng biệt, xử lý tốt hơn nhiều tệp, công cụ dành cho nhà phát triển và khả năng dễ dàng mã nguồn mở là những lợi ích lớn. 22 | 23 | ::: 24 | -------------------------------------------------------------------------------- /i18n/vi/docusaurus-plugin-content-docs/version-1.x/extenders.md: -------------------------------------------------------------------------------- 1 | # Bộ mở rộng cục bộ 2 | 3 | Nếu có các tùy chỉnh bạn muốn thực hiện cho trang web của mình mà không phân phối toàn bộ tiện ích mở rộng, bạn có thể làm như vậy bằng cách sử dụng **bộ mở rộng cục bộ**. Mỗi bản cài đặt Flarum đều đi kèm với một tệp `extend.php` nơi bạn có thể thêm các đối tượng bộ mở rộng, giống như trong một phần mở rộng đầy đủ. 4 | 5 | Xem [tài liệu mở rộng của chúng tôi](extend/start.md) để biết thêm thông tin về bộ mở rộng (và cả [ví dụ về bộ mở rộng cục bộ](extend/start.md#hello-world)). 6 | 7 | Nếu bạn cần tạo tệp mới (khi thêm class tùy chỉnh được nhập cho bộ mở rộng), bạn sẽ cần điều chỉnh composer.json của mình một chút. Thêm những dòng sau: 8 | 9 | ```json 10 | "autoload": { 11 | "psr-4": { 12 | "App\\": "app/" 13 | } 14 | }, 15 | ``` 16 | 17 | Giờ đây, bạn có thể tạo các tệp PHP mới trong thư mục con `ứng dụng` bằng cách sử dụng namespace `App\...`. 18 | 19 | :::tip Bộ mở rộng cục bộ với Tiện ích mở rộng 20 | 21 | Các bộ mở rộng cục bộ có thể tốt cho các chỉnh sửa nhỏ, nhưng nếu bạn cần các tùy chỉnh lớn, một tiện ích mở rộng có thể là lựa chọn tốt hơn: một cơ sở mã riêng biệt, xử lý tốt hơn nhiều tệp, công cụ dành cho nhà phát triển và khả năng dễ dàng mã nguồn mở là những lợi ích lớn. 22 | 23 | ::: 24 | -------------------------------------------------------------------------------- /i18n/it/docusaurus-plugin-content-docs/current/extend/translate.md: -------------------------------------------------------------------------------- 1 | # Tradurre Flarum 2 | 3 | ### LanguagePack 4 | 5 | Come extender, [`LanguagePack`](https://github.com/flarum/core/blob/master/src/Extend/LanguagePack.php) ti consente di definire che la tua estensione è appunto un language pack. 6 | 7 | Tutto quello che devi fare è istanziarlo, e assicurarti che il tuo language pack sia nella cartella `locale`, e sei a posto! 8 | 9 | Ecco un esempio veloce dal pacchetto [Flarum English](https://github.com/flarum/lang-english/blob/master/extend.php): 10 | 11 | ```php 12 | > /dev/null 2>&1 45 | ``` 46 | 47 | `* * * * *` 会告诉 cron 每分钟都来运行你的命令。 48 | 49 | 如果你想修改触发时间，但不确切知道 cron 表达式是如何工作的，你可以使用[cron表达式生成器](https://crontab.guru)来轻松获取所需的命令。 50 | 51 | `cd /path-to-your-project && php flarum schedule:run` 这行代码将执行Flarum的调度器以触发当前所有等待运行的任务。 如果PHP不在你的系统路径中，你可能需要尝试设置PHP的完整路径。 52 | 53 | 最后，`>> /dev/null 2>&1` 抑制了命令的所有输出。 54 | 55 | 瞧！ 现在任何注册了定时任务的扩展程序，从每分钟到每天、每月、每年，都将自动在你的服务器上运行。 56 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/version-1.x/scheduler.md: -------------------------------------------------------------------------------- 1 | # 调度器 2 | 3 | Flarum的调度器让扩展程序能够轻松地自动化某些任务。 在本指南中，我们将介绍如何设置它。 我们不会深入讨论cron本身的细节，但如果你想进一步了解它，我建议你查看[Wikipedia上关于cron的文章](https://en.wikipedia.org/wiki/Cron)。 4 | 5 | ## 为什么我要关心？ 6 | 7 | 很简单，现在有越来越多的扩展程序支持在后台自动为你处理某些功能。 想知道为什么`fof/drafts`的“定时发布”没有发布，抑或是`fof/best-answer`的“在X天后提醒用户设置最佳答案”功能没有被触发吗？ 那是因为它们会自动用调度器服务来配置自己，但这一切配置的前提是一行简短的cron任务。 8 | 9 | ## 有什么扩展程序现在在使用调度器？ 10 | 11 | 最火的一些例子如下： 12 | 13 | - [FoF Best Answer](https://github.com/FriendsOfFlarum/best-answer) 14 | - [FoF Drafts](https://github.com/FriendsOfFlarum/drafts) 15 | - [FoF Sitemap](https://github.com/FriendsOfFlarum/sitemap) 16 | - [FoF Open Collective](https://github.com/FriendsOfFlarum/open-collective) 17 | - [FoF Github Sponsors](https://github.com/FriendsOfFlarum/github-sponsors) 18 | 19 | ## 让我们配置起来！ 20 | 21 | 几乎所有（全部）Linux发行版本都自带或可以安装cron。 例如，在基于Debian和Ubuntu的系统上，你可以这样安装`cron`： 22 | 23 | ``` 24 | sudo apt-get update 25 | sudo apt-get install cron 26 | ``` 27 | 28 | 如果你使用的是基于RHEL的Linux发行版（如CentOS、AlmaLinux、Rocky Linux等），可以这样安装cron： 29 | 30 | ``` 31 | sudo dnf update 32 | sudo dnf install crontabs 33 | ``` 34 | 35 | 安装好了cron，让我们创建Flarum所需的唯一定时条目： 36 | 37 | ``` 38 | crontab -e 39 | ``` 40 | 41 | 这将打开 cron 编辑器。 你或许会有其他 cron 条目，但没关系。 添加以下这行，并记住在底部留一个空行。 42 | 43 | ``` 44 | * * * * * cd /path-to-your-project && php flarum schedule:run >> /dev/null 2>&1 45 | ``` 46 | 47 | `* * * * *` 会告诉 cron 每分钟都来运行你的命令。 48 | 49 | 如果你想修改触发时间，但不确切知道 cron 表达式是如何工作的，你可以使用[cron表达式生成器](https://crontab.guru)来轻松获取所需的命令。 50 | 51 | `cd /path-to-your-project && php flarum schedule:run` 这行代码将执行Flarum的调度器以触发当前所有等待运行的任务。 如果PHP不在你的系统路径中，你可能需要尝试设置PHP的完整路径。 52 | 53 | 最后，`>> /dev/null 2>&1` 抑制了命令的所有输出。 54 | 55 | 瞧！ 现在任何注册了定时任务的扩展程序，从每分钟到每天、每月、每年，都将自动在你的服务器上运行。 56 | -------------------------------------------------------------------------------- /i18n/es/docusaurus-plugin-content-docs/current/themes.md: -------------------------------------------------------------------------------- 1 | # Theming 2 | 3 | While we've worked hard to make Flarum as beautiful as we can, each community will probably want to make some tweaks/modifications to fit their desired style. 4 | 5 | ## Panel de Administración 6 | 7 | The [admin dashboard](admin.md)'s Appearance page is a great first place to start customizing your forum. Here, you can: 8 | 9 | - Select theme colors 10 | - Toggle dark mode and a colored header 11 | - Upload a logo and favicon (icon shown in browser tabs) 12 | - Add HTML for custom headers and footers 13 | - Add [custom LESS/CSS](#css-theming) to change how elements are displayed 14 | 15 | ## CSS Theming 16 | 17 | El CSS es un lenguaje de hojas de estilo que indica a los navegadores cómo mostrar los elementos de una página web. Nos permite modificar todo, desde los colores hasta las fuentes, el tamaño de los elementos y su posicionamiento, y las animaciones. Añadir CSS personalizado puede ser una gran manera de modificar su instalación de Flarum para que coincida con un tema. 18 | 19 | Un tutorial de CSS está más allá del alcance de esta documentación, pero hay muchos recursos en línea para aprender los fundamentos de CSS. 20 | 21 | :::tip 22 | 23 | Flarum utiliza LESS, que facilita la escritura de CSS al permitir variables, condicionales y funciones. 24 | 25 | ::: 26 | 27 | ## Extensiones 28 | 29 | El flexible [sistema de extensiones](extensions.md) de Flarum te permite añadir, eliminar o modificar prácticamente cualquier parte de Flarum. Si quieres hacer modificaciones temáticas sustanciales más allá de cambiar colores/tamaños/estilos, una extensión personalizada es definitivamente el camino a seguir. Para aprender cómo hacer una extensión, ¡consulta nuestra [documentación de extensiones](extend/README.md)! 30 | -------------------------------------------------------------------------------- /i18n/es/docusaurus-plugin-content-docs/version-1.x/themes.md: -------------------------------------------------------------------------------- 1 | # Theming 2 | 3 | While we've worked hard to make Flarum as beautiful as we can, each community will probably want to make some tweaks/modifications to fit their desired style. 4 | 5 | ## Panel de Administración 6 | 7 | The [admin dashboard](admin.md)'s Appearance page is a great first place to start customizing your forum. Here, you can: 8 | 9 | - Select theme colors 10 | - Toggle dark mode and a colored header 11 | - Upload a logo and favicon (icon shown in browser tabs) 12 | - Add HTML for custom headers and footers 13 | - Add [custom LESS/CSS](#css-theming) to change how elements are displayed 14 | 15 | ## CSS Theming 16 | 17 | El CSS es un lenguaje de hojas de estilo que indica a los navegadores cómo mostrar los elementos de una página web. Nos permite modificar todo, desde los colores hasta las fuentes, el tamaño de los elementos y su posicionamiento, y las animaciones. Añadir CSS personalizado puede ser una gran manera de modificar su instalación de Flarum para que coincida con un tema. 18 | 19 | Un tutorial de CSS está más allá del alcance de esta documentación, pero hay muchos recursos en línea para aprender los fundamentos de CSS. 20 | 21 | :::tip 22 | 23 | Flarum utiliza LESS, que facilita la escritura de CSS al permitir variables, condicionales y funciones. 24 | 25 | ::: 26 | 27 | ## Extensiones 28 | 29 | El flexible [sistema de extensiones](extensions.md) de Flarum te permite añadir, eliminar o modificar prácticamente cualquier parte de Flarum. Si quieres hacer modificaciones temáticas sustanciales más allá de cambiar colores/tamaños/estilos, una extensión personalizada es definitivamente el camino a seguir. Para aprender cómo hacer una extensión, ¡consulta nuestra [documentación de extensiones](extend/README.md)! 30 | -------------------------------------------------------------------------------- /i18n/vi/docusaurus-plugin-content-docs/current/config.md: -------------------------------------------------------------------------------- 1 | # Tệp cấu hình 2 | 3 | Chỉ có một số nơi không thể cấu hình thông qua bảng điều khiển quản trị Flarum (không bao gồm database), đó chính là tệp `config.php` nằm trong thư mục càid dặt Flarum của bạn. 4 | 5 | Tệp này mặc dù rất nhẹ, nhưng nó chứa các thông tin quan trọng để Flarum của bạn hoạt động. 6 | 7 | Nếu tệp tồn tại, điều đó cho biết rằng Flarum đã được cài đặt. Nó cũng cung cấp cho Flarum với thông tin database và nhiều hơn nữa. 8 | 9 | Dưới đây là tổng quan nhanh về những thứ có trong tệp cấu hình: 10 | 11 | ```php 12 | false, // bật tắt chế độ gỡ lỗi, sử dụng để khắc phục sự cố 14 | 'offline' => false, // bật tắt chế độ bảo trì. Quản trị viên và người dùng sẽ không thể truy cập vào trang web. 15 | 'database' => 16 | array ( 17 | 'driver' => 'mysql', // trình điều khiển cơ sở dữ liệu. Vd: MySQL, MariaDB... 18 | 'host' => 'localhost', // máy chủ kết nối, localhost trong hầu hết các trường hợp trừ khi sử dụng dịch vụ bên ngoài 19 | 'database' => 'flarum', // tên cơ sở dữ liệu 20 | 'username' => 'root', // tên người dùng cơ sở dữ liệu 21 | 'password' => '', // mật khẩu cơ sở dữ liệu 22 | 'charset' => 'utf8mb4', 23 | 'collation' => 'utf8mb4_unicode_ci', 24 | 'prefix' => '', // tiền tố cho các bảng, hữu ích nếu bạn đang chia sẻ cùng một cơ sở dữ liệu với một dịch vụ khác 25 | 'port' => '3306', // cổng kết nối, mặc định là 3306 với MySQL 26 | 'strict' => false, 27 | ), 28 | 'url' => 'https://flarum.localhost', // URL trang web, bạn sẽ muốn thay đổi điều này nếu bạn thay đổi tên miền 29 | 'paths' => 30 | array ( 31 | 'api' => 'api', // /api chuyển đến API 32 | 'admin' => 'admin', // /admin chuyển tới quản trị viên 33 | ), 34 | ); 35 | ``` 36 | -------------------------------------------------------------------------------- /i18n/vi/docusaurus-plugin-content-docs/version-1.x/config.md: -------------------------------------------------------------------------------- 1 | # Tệp cấu hình 2 | 3 | Chỉ có một số nơi không thể cấu hình thông qua bảng điều khiển quản trị Flarum (không bao gồm database), đó chính là tệp `config.php` nằm trong thư mục càid dặt Flarum của bạn. 4 | 5 | Tệp này mặc dù rất nhẹ, nhưng nó chứa các thông tin quan trọng để Flarum của bạn hoạt động. 6 | 7 | Nếu tệp tồn tại, điều đó cho biết rằng Flarum đã được cài đặt. Nó cũng cung cấp cho Flarum với thông tin database và nhiều hơn nữa. 8 | 9 | Dưới đây là tổng quan nhanh về những thứ có trong tệp cấu hình: 10 | 11 | ```php 12 | false, // bật tắt chế độ gỡ lỗi, sử dụng để khắc phục sự cố 14 | 'offline' => false, // bật tắt chế độ bảo trì. Quản trị viên và người dùng sẽ không thể truy cập vào trang web. 15 | 'database' => 16 | array ( 17 | 'driver' => 'mysql', // trình điều khiển cơ sở dữ liệu. Vd: MySQL, MariaDB... 18 | 'host' => 'localhost', // máy chủ kết nối, localhost trong hầu hết các trường hợp trừ khi sử dụng dịch vụ bên ngoài 19 | 'database' => 'flarum', // tên cơ sở dữ liệu 20 | 'username' => 'root', // tên người dùng cơ sở dữ liệu 21 | 'password' => '', // mật khẩu cơ sở dữ liệu 22 | 'charset' => 'utf8mb4', 23 | 'collation' => 'utf8mb4_unicode_ci', 24 | 'prefix' => '', // tiền tố cho các bảng, hữu ích nếu bạn đang chia sẻ cùng một cơ sở dữ liệu với một dịch vụ khác 25 | 'port' => '3306', // cổng kết nối, mặc định là 3306 với MySQL 26 | 'strict' => false, 27 | ), 28 | 'url' => 'https://flarum.localhost', // URL trang web, bạn sẽ muốn thay đổi điều này nếu bạn thay đổi tên miền 29 | 'paths' => 30 | array ( 31 | 'api' => 'api', // /api chuyển đến API 32 | 'admin' => 'admin', // /admin chuyển tới quản trị viên 33 | ), 34 | ); 35 | ``` 36 | -------------------------------------------------------------------------------- /i18n/vi/docusaurus-plugin-content-docs/current/themes.md: -------------------------------------------------------------------------------- 1 | # Chủ đề 2 | 3 | Mặc dù chúng tôi đã làm việc chăm chỉ để làm cho Flarum đẹp nhất có thể, nhưng mỗi cộng đồng có thể sẽ muốn thực hiện một số chỉnh sửa/sửa đổi để phù hợp với phong cách mong muốn của họ. 4 | 5 | ## Bảng điều khiển Quản trị 6 | 7 | The [admin dashboard](admin.md)'s Appearance page is a great first place to start customizing your forum. Tại đây, bạn có thể: 8 | 9 | - Chọn màu chủ đề 10 | - Chuyển đổi chế độ tối và màu đầu trang 11 | - Tải lên icon và favicon (icon hiển thị trong các tab của trình duyệt) 12 | - Thêm HTML cho đầu trang và chân trang tùy chỉnh 13 | - Thên [mã LESS/CSS](#css-theming) để thay đổi cách các phần tử được hiển thị 14 | 15 | ## Chủ đề CSS 16 | 17 | CSS là một ngôn ngữ biểu định kiểu cho các trình duyệt biết cách hiển thị các phần tử của một trang web. Nó cho phép chúng tôi sửa đổi mọi thứ từ màu sắc, phông chữ đến kích thước phần tử và vị trí cho đến hình ảnh động. Thêm CSS tùy chỉnh có thể là một cách tuyệt vời để sửa đổi cài đặt Flarum của bạn cho phù hợp với chủ đề. 18 | 19 | Hướng dẫn CSS nằm ngoài phạm vi của tài liệu này, nhưng có rất nhiều tài nguyên trực tuyến tuyệt vời để tìm hiểu kiến ​​thức cơ bản về CSS. 20 | 21 | :::tip 22 | 23 | Flarum thực sự sử dụng LESS, giúp viết CSS dễ dàng hơn bằng cách cho phép các biến, điều kiện và hàm. 24 | 25 | ::: 26 | 27 | ## Tiện ích mở rộng 28 | 29 | [Hệ thống tiện ích mở rộng](extensions.md) linh hoạt của Flarum cho phép bạn thêm, xóa hoặc sửa đổi trên thực tế bất kỳ phần nào của Flarum. Nếu bạn muốn thực hiện các sửa đổi đáng kể về chủ đề ngoài việc thay đổi màu sắc/kích thước/kiểu dáng, thì một tiện ích mở rộng tùy chỉnh chắc chắn là cách tốt nhất. Để tìm hiểu cách tạo tiện ích mở rộng, hãy xem [tài liệu về tiện ích mở rộng](extend/README.md) của chúng tôi! 30 | -------------------------------------------------------------------------------- /i18n/vi/docusaurus-plugin-content-docs/version-1.x/themes.md: -------------------------------------------------------------------------------- 1 | # Chủ đề 2 | 3 | Mặc dù chúng tôi đã làm việc chăm chỉ để làm cho Flarum đẹp nhất có thể, nhưng mỗi cộng đồng có thể sẽ muốn thực hiện một số chỉnh sửa/sửa đổi để phù hợp với phong cách mong muốn của họ. 4 | 5 | ## Bảng điều khiển Quản trị 6 | 7 | The [admin dashboard](admin.md)'s Appearance page is a great first place to start customizing your forum. Tại đây, bạn có thể: 8 | 9 | - Chọn màu chủ đề 10 | - Chuyển đổi chế độ tối và màu đầu trang 11 | - Tải lên icon và favicon (icon hiển thị trong các tab của trình duyệt) 12 | - Thêm HTML cho đầu trang và chân trang tùy chỉnh 13 | - Thên [mã LESS/CSS](#css-theming) để thay đổi cách các phần tử được hiển thị 14 | 15 | ## Chủ đề CSS 16 | 17 | CSS là một ngôn ngữ biểu định kiểu cho các trình duyệt biết cách hiển thị các phần tử của một trang web. Nó cho phép chúng tôi sửa đổi mọi thứ từ màu sắc, phông chữ đến kích thước phần tử và vị trí cho đến hình ảnh động. Thêm CSS tùy chỉnh có thể là một cách tuyệt vời để sửa đổi cài đặt Flarum của bạn cho phù hợp với chủ đề. 18 | 19 | Hướng dẫn CSS nằm ngoài phạm vi của tài liệu này, nhưng có rất nhiều tài nguyên trực tuyến tuyệt vời để tìm hiểu kiến ​​thức cơ bản về CSS. 20 | 21 | :::tip 22 | 23 | Flarum thực sự sử dụng LESS, giúp viết CSS dễ dàng hơn bằng cách cho phép các biến, điều kiện và hàm. 24 | 25 | ::: 26 | 27 | ## Tiện ích mở rộng 28 | 29 | [Hệ thống tiện ích mở rộng](extensions.md) linh hoạt của Flarum cho phép bạn thêm, xóa hoặc sửa đổi trên thực tế bất kỳ phần nào của Flarum. Nếu bạn muốn thực hiện các sửa đổi đáng kể về chủ đề ngoài việc thay đổi màu sắc/kích thước/kiểu dáng, thì một tiện ích mở rộng tùy chỉnh chắc chắn là cách tốt nhất. Để tìm hiểu cách tạo tiện ích mở rộng, hãy xem [tài liệu về tiện ích mở rộng](extend/README.md) của chúng tôi! 30 | -------------------------------------------------------------------------------- /i18n/tr/docusaurus-plugin-content-docs/current/themes.md: -------------------------------------------------------------------------------- 1 | # Tema 2 | 3 | Flarum'u olabildiğince güzel hale getirmek için çok çalışmış olsak da, her topluluk muhtemelen arzu ettikleri stile uyacak bazı ince ayarlar/değişiklikler yapmak isteyecektir. 4 | 5 | ## Yönetici Gösterge Paneli 6 | 7 | [Yönetici gösterge tablosu](admin.md)'nun Görünüm sayfası, forumunuzu özelleştirmeye başlamak için harika bir ilk yerdir. Burada yapabilirsin: 8 | 9 | - Tema renklerini seçin 10 | - Karanlık modu ve renkli üstbilgi değiştir 11 | - Bir logo ve favicon yükleyin (tarayıcı sekmelerinde gösterilen simge) 12 | - Özel üstbilgiler ve altbilgiler için HTML ekleyin 13 | - Öğelerin görüntülenme şeklini değiştirmek için [özel LESS/CSS](#css-theming) ekleyin 14 | 15 | ## CSS Tema Oluşturma 16 | 17 | CSS, tarayıcılara bir web sayfasının öğelerinin nasıl görüntüleneceğini söyleyen bir stil sayfası dilidir. Renklerden yazı tiplerine, eleman boyutuna ve konumlandırmadan animasyonlara kadar her şeyi değiştirmemizi sağlar. Özel CSS eklemek, Flarum kurulumunuzu bir temayla eşleşecek şekilde değiştirmenin harika bir yolu olabilir. 18 | 19 | Bir CSS eğitimi bu belgesinin kapsamı dışındadır, ancak CSS'nin temellerini öğrenmek için birçok harika çevrimiçi kaynak vardır. 20 | 21 | :::tip 22 | 23 | Flarum aslında LESS kullanır, bu da değişkenlere, koşullara ve işlevlere izin vererek CSS yazmayı kolaylaştırır. 24 | 25 | ::: 26 | 27 | ## Uzantılar 28 | 29 | Flarum'un esnek [uzantı sistemi](extensions.md), Flarum'un herhangi bir parçasını pratik olarak eklemenize, çıkarmanıza veya değiştirmenize olanak tanır. Renkleri/boyutları/stilleri değiştirmenin ötesinde önemli tema değişiklikleri yapmak istiyorsanız, kesinlikle gitmenin yolu özel bir uzantıdır. Bir uzantının nasıl oluşturulacağını öğrenmek için [uzantı belgelerimize](extend/README.md) göz atın! 30 | -------------------------------------------------------------------------------- /i18n/tr/docusaurus-plugin-content-docs/version-1.x/themes.md: -------------------------------------------------------------------------------- 1 | # Tema 2 | 3 | Flarum'u olabildiğince güzel hale getirmek için çok çalışmış olsak da, her topluluk muhtemelen arzu ettikleri stile uyacak bazı ince ayarlar/değişiklikler yapmak isteyecektir. 4 | 5 | ## Yönetici Gösterge Paneli 6 | 7 | [Yönetici gösterge tablosu](admin.md)'nun Görünüm sayfası, forumunuzu özelleştirmeye başlamak için harika bir ilk yerdir. Burada yapabilirsin: 8 | 9 | - Tema renklerini seçin 10 | - Karanlık modu ve renkli üstbilgi değiştir 11 | - Bir logo ve favicon yükleyin (tarayıcı sekmelerinde gösterilen simge) 12 | - Özel üstbilgiler ve altbilgiler için HTML ekleyin 13 | - Öğelerin görüntülenme şeklini değiştirmek için [özel LESS/CSS](#css-theming) ekleyin 14 | 15 | ## CSS Tema Oluşturma 16 | 17 | CSS, tarayıcılara bir web sayfasının öğelerinin nasıl görüntüleneceğini söyleyen bir stil sayfası dilidir. Renklerden yazı tiplerine, eleman boyutuna ve konumlandırmadan animasyonlara kadar her şeyi değiştirmemizi sağlar. Özel CSS eklemek, Flarum kurulumunuzu bir temayla eşleşecek şekilde değiştirmenin harika bir yolu olabilir. 18 | 19 | Bir CSS eğitimi bu belgesinin kapsamı dışındadır, ancak CSS'nin temellerini öğrenmek için birçok harika çevrimiçi kaynak vardır. 20 | 21 | :::tip 22 | 23 | Flarum aslında LESS kullanır, bu da değişkenlere, koşullara ve işlevlere izin vererek CSS yazmayı kolaylaştırır. 24 | 25 | ::: 26 | 27 | ## Uzantılar 28 | 29 | Flarum'un esnek [uzantı sistemi](extensions.md), Flarum'un herhangi bir parçasını pratik olarak eklemenize, çıkarmanıza veya değiştirmenize olanak tanır. Renkleri/boyutları/stilleri değiştirmenin ötesinde önemli tema değişiklikleri yapmak istiyorsanız, kesinlikle gitmenin yolu özel bir uzantıdır. Bir uzantının nasıl oluşturulacağını öğrenmek için [uzantı belgelerimize](extend/README.md) göz atın! 30 | -------------------------------------------------------------------------------- /i18n/tr/docusaurus-plugin-content-docs/current.json: -------------------------------------------------------------------------------- 1 | { 2 | "version.label": { 3 | "message": "2.x", 4 | "description": "The label for version current" 5 | }, 6 | "sidebar.guideSidebar.category.Introduction": { 7 | "message": "Giriş", 8 | "description": "The label for category Introduction in sidebar guideSidebar" 9 | }, 10 | "sidebar.guideSidebar.category.Setting Up": { 11 | "message": "Kurulum", 12 | "description": "The label for category Setting Up in sidebar guideSidebar" 13 | }, 14 | "sidebar.guideSidebar.category.Management": { 15 | "message": "Yönetim", 16 | "description": "The label for category Management in sidebar guideSidebar" 17 | }, 18 | "sidebar.guideSidebar.category.Advanced": { 19 | "message": "Gelişmiş", 20 | "description": "The label for category Advanced in sidebar guideSidebar" 21 | }, 22 | "sidebar.extendSidebar.category.Main Concepts": { 23 | "message": "Ana konseptler", 24 | "description": "The label for category Main Concepts in sidebar extendSidebar" 25 | }, 26 | "sidebar.extendSidebar.category.Reference Guides": { 27 | "message": "Reference Guides", 28 | "description": "The label for category Reference Guides in sidebar extendSidebar" 29 | }, 30 | "sidebar.extendSidebar.category.Advanced Guides": { 31 | "message": "Advanced Guides", 32 | "description": "The label for category Advanced Guides in sidebar extendSidebar" 33 | }, 34 | "sidebar.extendSidebar.category.Update Guides": { 35 | "message": "Update Guides", 36 | "description": "The label for category Update Guides in sidebar extendSidebar" 37 | }, 38 | "sidebar.internalSidebar.category.Internal Docs": { 39 | "message": "Internal Docs", 40 | "description": "The label for category Internal Docs in sidebar internalSidebar" 41 | } 42 | } 43 | -------------------------------------------------------------------------------- /i18n/en/docusaurus-plugin-content-docs/current.json: -------------------------------------------------------------------------------- 1 | { 2 | "version.label": { 3 | "message": "2.x", 4 | "description": "The label for version current" 5 | }, 6 | "sidebar.guideSidebar.category.Introduction": { 7 | "message": "Introduction", 8 | "description": "The label for category Introduction in sidebar guideSidebar" 9 | }, 10 | "sidebar.guideSidebar.category.Setting Up": { 11 | "message": "Setting Up", 12 | "description": "The label for category Setting Up in sidebar guideSidebar" 13 | }, 14 | "sidebar.guideSidebar.category.Management": { 15 | "message": "Management", 16 | "description": "The label for category Management in sidebar guideSidebar" 17 | }, 18 | "sidebar.guideSidebar.category.Advanced": { 19 | "message": "Advanced", 20 | "description": "The label for category Advanced in sidebar guideSidebar" 21 | }, 22 | "sidebar.extendSidebar.category.Main Concepts": { 23 | "message": "Main Concepts", 24 | "description": "The label for category Main Concepts in sidebar extendSidebar" 25 | }, 26 | "sidebar.extendSidebar.category.Reference Guides": { 27 | "message": "Reference Guides", 28 | "description": "The label for category Reference Guides in sidebar extendSidebar" 29 | }, 30 | "sidebar.extendSidebar.category.Advanced Guides": { 31 | "message": "Advanced Guides", 32 | "description": "The label for category Advanced Guides in sidebar extendSidebar" 33 | }, 34 | "sidebar.extendSidebar.category.Update Guides": { 35 | "message": "Update Guides", 36 | "description": "The label for category Update Guides in sidebar extendSidebar" 37 | }, 38 | "sidebar.internalSidebar.category.Internal Docs": { 39 | "message": "Internal Docs", 40 | "description": "The label for category Internal Docs in sidebar internalSidebar" 41 | } 42 | } 43 | -------------------------------------------------------------------------------- /i18n/es/docusaurus-plugin-content-docs/current.json: -------------------------------------------------------------------------------- 1 | { 2 | "version.label": { 3 | "message": "2.x", 4 | "description": "The label for version current" 5 | }, 6 | "sidebar.guideSidebar.category.Introduction": { 7 | "message": "Introduction", 8 | "description": "The label for category Introduction in sidebar guideSidebar" 9 | }, 10 | "sidebar.guideSidebar.category.Setting Up": { 11 | "message": "Setting Up", 12 | "description": "The label for category Setting Up in sidebar guideSidebar" 13 | }, 14 | "sidebar.guideSidebar.category.Management": { 15 | "message": "Management", 16 | "description": "The label for category Management in sidebar guideSidebar" 17 | }, 18 | "sidebar.guideSidebar.category.Advanced": { 19 | "message": "Advanced", 20 | "description": "The label for category Advanced in sidebar guideSidebar" 21 | }, 22 | "sidebar.extendSidebar.category.Main Concepts": { 23 | "message": "Main Concepts", 24 | "description": "The label for category Main Concepts in sidebar extendSidebar" 25 | }, 26 | "sidebar.extendSidebar.category.Reference Guides": { 27 | "message": "Reference Guides", 28 | "description": "The label for category Reference Guides in sidebar extendSidebar" 29 | }, 30 | "sidebar.extendSidebar.category.Advanced Guides": { 31 | "message": "Advanced Guides", 32 | "description": "The label for category Advanced Guides in sidebar extendSidebar" 33 | }, 34 | "sidebar.extendSidebar.category.Update Guides": { 35 | "message": "Update Guides", 36 | "description": "The label for category Update Guides in sidebar extendSidebar" 37 | }, 38 | "sidebar.internalSidebar.category.Internal Docs": { 39 | "message": "Internal Docs", 40 | "description": "The label for category Internal Docs in sidebar internalSidebar" 41 | } 42 | } 43 | -------------------------------------------------------------------------------- /i18n/it/docusaurus-plugin-content-docs/current.json: -------------------------------------------------------------------------------- 1 | { 2 | "version.label": { 3 | "message": "2.x", 4 | "description": "The label for version current" 5 | }, 6 | "sidebar.guideSidebar.category.Introduction": { 7 | "message": "Introduction", 8 | "description": "The label for category Introduction in sidebar guideSidebar" 9 | }, 10 | "sidebar.guideSidebar.category.Setting Up": { 11 | "message": "Setting Up", 12 | "description": "The label for category Setting Up in sidebar guideSidebar" 13 | }, 14 | "sidebar.guideSidebar.category.Management": { 15 | "message": "Management", 16 | "description": "The label for category Management in sidebar guideSidebar" 17 | }, 18 | "sidebar.guideSidebar.category.Advanced": { 19 | "message": "Advanced", 20 | "description": "The label for category Advanced in sidebar guideSidebar" 21 | }, 22 | "sidebar.extendSidebar.category.Main Concepts": { 23 | "message": "Main Concepts", 24 | "description": "The label for category Main Concepts in sidebar extendSidebar" 25 | }, 26 | "sidebar.extendSidebar.category.Reference Guides": { 27 | "message": "Reference Guides", 28 | "description": "The label for category Reference Guides in sidebar extendSidebar" 29 | }, 30 | "sidebar.extendSidebar.category.Advanced Guides": { 31 | "message": "Advanced Guides", 32 | "description": "The label for category Advanced Guides in sidebar extendSidebar" 33 | }, 34 | "sidebar.extendSidebar.category.Update Guides": { 35 | "message": "Update Guides", 36 | "description": "The label for category Update Guides in sidebar extendSidebar" 37 | }, 38 | "sidebar.internalSidebar.category.Internal Docs": { 39 | "message": "Internal Docs", 40 | "description": "The label for category Internal Docs in sidebar internalSidebar" 41 | } 42 | } 43 | -------------------------------------------------------------------------------- /i18n/tr/docusaurus-plugin-content-docs/current/current.json: -------------------------------------------------------------------------------- 1 | { 2 | "version.label": { 3 | "message": "Next", 4 | "description": "The label for version current" 5 | }, 6 | "sidebar.guideSidebar.category.Introduction": { 7 | "message": "Giriş", 8 | "description": "The label for category Introduction in sidebar guideSidebar" 9 | }, 10 | "sidebar.guideSidebar.category.Setting Up": { 11 | "message": "Ayarlama", 12 | "description": "The label for category Setting Up in sidebar guideSidebar" 13 | }, 14 | "sidebar.guideSidebar.category.Management": { 15 | "message": "Yönetim", 16 | "description": "The label for category Management in sidebar guideSidebar" 17 | }, 18 | "sidebar.guideSidebar.category.Advanced": { 19 | "message": "Advanced", 20 | "description": "The label for category Advanced in sidebar guideSidebar" 21 | }, 22 | "sidebar.extendSidebar.category.Main Concepts": { 23 | "message": "Ana Kavramlar", 24 | "description": "The label for category Main Concepts in sidebar extendSidebar" 25 | }, 26 | "sidebar.extendSidebar.category.Reference Guides": { 27 | "message": "Referans Kılavuzları", 28 | "description": "The label for category Reference Guides in sidebar extendSidebar" 29 | }, 30 | "sidebar.extendSidebar.category.Advanced Guides": { 31 | "message": "Gelişmiş Kılavuzlar", 32 | "description": "The label for category Advanced Guides in sidebar extendSidebar" 33 | }, 34 | "sidebar.extendSidebar.category.Update Guides": { 35 | "message": "Update Guides", 36 | "description": "The label for category Update Guides in sidebar extendSidebar" 37 | }, 38 | "sidebar.internalSidebar.category.Internal Docs": { 39 | "message": "Internal Docs", 40 | "description": "The label for category Internal Docs in sidebar internalSidebar" 41 | } 42 | } -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/current/internal/merging.md: -------------------------------------------------------------------------------- 1 | # PR 合并工作流程 2 | 3 | 4 | ## 执行审查标准 5 | 6 | - Adheres to our conventions or can be patched up easily after merging, follows proper code style. 7 | - Are there any implementation details that could be done better through alternate technologies/technical approaches? 8 | - Does not touch any lines outside of the intended changes, eg through formatting or compilation. 9 | - If the changes are to code intended as a public API, has a proper doc block been included? 10 | 11 | ## Merge Time! 12 | 13 | If all of the checks in the template are met, **any** core developer may merge this PR. If the PR is authored by a core developer, they should probably be the ones to merge it. 14 | 15 | - 合并： 16 | - GitHub offers several ways to merge a PR. Choose between the following strategies: 17 | - **Merge** when the PR branch consists of atomic, well-described commits that are nice to have in the version history. 18 | - **Squash** when lots of cleanup commits have accumulated. Please make sure to follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/#summary) spec for the squash commit. 19 | 20 | - 合并后： 21 | - Make sure the *issue* (if none exists, the PR - but not both) belongs to the appropriate milestone and project board. 22 | - PRs in extensions cannot be assigned to core milestones, so create a core issue that references it and add it to the milestone. 23 | - Close all relevant issues (*if* they are closed completely). 24 | - Regressions should be labeled as such and removed from the project board and milestone after merging. 25 | - Check for follow-up tasks: 26 | - Merge related PRs (language files, extensions, documentations). 27 | - Documentation updates. 28 | - Create issues for further follow-up tasks, if necessary. 29 | 30 | -------------------------------------------------------------------------------- /i18n/zh/docusaurus-plugin-content-docs/version-1.x/internal/merging.md: -------------------------------------------------------------------------------- 1 | # PR 合并工作流程 2 | 3 | 4 | ## 执行审查标准 5 | 6 | - Adheres to our conventions or can be patched up easily after merging, follows proper code style. 7 | - Are there any implementation details that could be done better through alternate technologies/technical approaches? 8 | - Does not touch any lines outside of the intended changes, eg through formatting or compilation. 9 | - If the changes are to code intended as a public API, has a proper doc block been included? 10 | 11 | ## Merge Time! 12 | 13 | If all of the checks in the template are met, **any** core developer may merge this PR. If the PR is authored by a core developer, they should probably be the ones to merge it. 14 | 15 | - 合并： 16 | - GitHub offers several ways to merge a PR. Choose between the following strategies: 17 | - **Merge** when the PR branch consists of atomic, well-described commits that are nice to have in the version history. 18 | - **Squash** when lots of cleanup commits have accumulated. Please make sure to follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/#summary) spec for the squash commit. 19 | 20 | - 合并后： 21 | - Make sure the *issue* (if none exists, the PR - but not both) belongs to the appropriate milestone and project board. 22 | - PRs in extensions cannot be assigned to core milestones, so create a core issue that references it and add it to the milestone. 23 | - Close all relevant issues (*if* they are closed completely). 24 | - Regressions should be labeled as such and removed from the project board and milestone after merging. 25 | - Check for follow-up tasks: 26 | - Merge related PRs (language files, extensions, documentations). 27 | - Documentation updates. 28 | - Create issues for further follow-up tasks, if necessary. 29 | 30 | -------------------------------------------------------------------------------- /i18n/tr/docusaurus-plugin-content-docs/version-1.x/current.json: -------------------------------------------------------------------------------- 1 | { 2 | "version.label": { 3 | "message": "Next", 4 | "description": "The label for version current" 5 | }, 6 | "sidebar.guideSidebar.category.Introduction": { 7 | "message": "Giriş", 8 | "description": "The label for category Introduction in sidebar guideSidebar" 9 | }, 10 | "sidebar.guideSidebar.category.Setting Up": { 11 | "message": "Ayarlama", 12 | "description": "The label for category Setting Up in sidebar guideSidebar" 13 | }, 14 | "sidebar.guideSidebar.category.Management": { 15 | "message": "Yönetim", 16 | "description": "The label for category Management in sidebar guideSidebar" 17 | }, 18 | "sidebar.guideSidebar.category.Advanced": { 19 | "message": "Advanced", 20 | "description": "The label for category Advanced in sidebar guideSidebar" 21 | }, 22 | "sidebar.extendSidebar.category.Main Concepts": { 23 | "message": "Ana Kavramlar", 24 | "description": "The label for category Main Concepts in sidebar extendSidebar" 25 | }, 26 | "sidebar.extendSidebar.category.Reference Guides": { 27 | "message": "Referans Kılavuzları", 28 | "description": "The label for category Reference Guides in sidebar extendSidebar" 29 | }, 30 | "sidebar.extendSidebar.category.Advanced Guides": { 31 | "message": "Gelişmiş Kılavuzlar", 32 | "description": "The label for category Advanced Guides in sidebar extendSidebar" 33 | }, 34 | "sidebar.extendSidebar.category.Update Guides": { 35 | "message": "Update Guides", 36 | "description": "The label for category Update Guides in sidebar extendSidebar" 37 | }, 38 | "sidebar.internalSidebar.category.Internal Docs": { 39 | "message": "Internal Docs", 40 | "description": "The label for category Internal Docs in sidebar internalSidebar" 41 | } 42 | } -------------------------------------------------------------------------------- /i18n/vi/docusaurus-plugin-content-docs/current.json: -------------------------------------------------------------------------------- 1 | { 2 | "version.label": { 3 | "message": "2.x", 4 | "description": "The label for version current" 5 | }, 6 | "sidebar.guideSidebar.category.Introduction": { 7 | "message": "Giới thiệu", 8 | "description": "The label for category Introduction in sidebar guideSidebar" 9 | }, 10 | "sidebar.guideSidebar.category.Setting Up": { 11 | "message": "Cài đặt", 12 | "description": "The label for category Setting Up in sidebar guideSidebar" 13 | }, 14 | "sidebar.guideSidebar.category.Management": { 15 | "message": "Quản lý", 16 | "description": "The label for category Management in sidebar guideSidebar" 17 | }, 18 | "sidebar.guideSidebar.category.Advanced": { 19 | "message": "Nâng cao", 20 | "description": "The label for category Advanced in sidebar guideSidebar" 21 | }, 22 | "sidebar.extendSidebar.category.Main Concepts": { 23 | "message": "Khái niệm chính", 24 | "description": "The label for category Main Concepts in sidebar extendSidebar" 25 | }, 26 | "sidebar.extendSidebar.category.Reference Guides": { 27 | "message": "Hướng dẫn Tham khảo", 28 | "description": "The label for category Reference Guides in sidebar extendSidebar" 29 | }, 30 | "sidebar.extendSidebar.category.Advanced Guides": { 31 | "message": "Hướng dẫn nâng cao", 32 | "description": "The label for category Advanced Guides in sidebar extendSidebar" 33 | }, 34 | "sidebar.extendSidebar.category.Update Guides": { 35 | "message": "Hướng dẫn nâng cấp", 36 | "description": "The label for category Update Guides in sidebar extendSidebar" 37 | }, 38 | "sidebar.internalSidebar.category.Internal Docs": { 39 | "message": "Tài liệu nội bộ", 40 | "description": "The label for category Internal Docs in sidebar internalSidebar" 41 | } 42 | } 43 | -------------------------------------------------------------------------------- /docs/contributing-docs-translations.md: -------------------------------------------------------------------------------- 1 | # Docs and Translation 2 | 3 | ## Add Documentation 4 | 5 | Adding documentation can help countless future Flarum users. A few ideas of what to work on: 6 | 7 | - User guides to help Flarum end users with some advanced Flarum features. 8 | - More [frequently asked questions](faq.md). 9 | - Expanded [troubleshooting](troubleshoot.md) steps. 10 | - Step-by-step tutorials for Flarum development or installation. 11 | - [Technical reference guides](extend/README.md) for extension developers. 12 | - Improving literally anything else you think we should elaborate on or explain better. 13 | 14 | A good way to find topics to write about is to look for common questions in the [support tag](https://discuss.flarum.org/t/support) of our community. 15 | 16 | ## Translate Flarum 17 | 18 | We want Flarum to be accessible to everyone, regardless of language! By contributing translations, you make it possible for many more people to enjoy Flarum. Best of all, we use user-friendly GUIs for translations, so no technical skills are necessary to help! 19 | 20 | Translations for Flarum core, bundled extensions, and community extensions are managed through [Weblate](https://weblate.rob006.net/projects/flarum/). 21 | 22 | Translations for this documentation are managed through [Crowdin](https://crowdin.com/project/flarum-docs). 23 | 24 | The Flarum Foundation has created the "flarum-lang" organization to support translators and ensure continuous availability of language packs. You can learn more about this by [visiting the GitHub repository](https://github.com/flarum-lang/about). 25 | 26 | If you want to support an existing language pack, start a new translation, or you run into issues using weblate or crowdin, it's best to [get in touch with the `flarum-lang` team](https://discuss.flarum.org/d/27519-the-flarum-language-project). 27 | -------------------------------------------------------------------------------- /i18n/es/docusaurus-plugin-content-docs/current/current.json: -------------------------------------------------------------------------------- 1 | { 2 | "version.label": { 3 | "message": "Next", 4 | "description": "The label for version current" 5 | }, 6 | "sidebar.guideSidebar.category.Introduction": { 7 | "message": "Introducción", 8 | "description": "The label for category Introduction in sidebar guideSidebar" 9 | }, 10 | "sidebar.guideSidebar.category.Setting Up": { 11 | "message": "Configuración", 12 | "description": "The label for category Setting Up in sidebar guideSidebar" 13 | }, 14 | "sidebar.guideSidebar.category.Management": { 15 | "message": "Gestión", 16 | "description": "The label for category Management in sidebar guideSidebar" 17 | }, 18 | "sidebar.guideSidebar.category.Advanced": { 19 | "message": "Advanced", 20 | "description": "The label for category Advanced in sidebar guideSidebar" 21 | }, 22 | "sidebar.extendSidebar.category.Main Concepts": { 23 | "message": "Conceptos Principales", 24 | "description": "The label for category Main Concepts in sidebar extendSidebar" 25 | }, 26 | "sidebar.extendSidebar.category.Reference Guides": { 27 | "message": "Guías de Referencia", 28 | "description": "The label for category Reference Guides in sidebar extendSidebar" 29 | }, 30 | "sidebar.extendSidebar.category.Advanced Guides": { 31 | "message": "Guías Avanzadas", 32 | "description": "The label for category Advanced Guides in sidebar extendSidebar" 33 | }, 34 | "sidebar.extendSidebar.category.Update Guides": { 35 | "message": "Update Guides", 36 | "description": "The label for category Update Guides in sidebar extendSidebar" 37 | }, 38 | "sidebar.internalSidebar.category.Internal Docs": { 39 | "message": "Internal Docs", 40 | "description": "The label for category Internal Docs in sidebar internalSidebar" 41 | } 42 | } -------------------------------------------------------------------------------- /i18n/it/docusaurus-plugin-content-docs/current/current.json: -------------------------------------------------------------------------------- 1 | { 2 | "version.label": { 3 | "message": "Next", 4 | "description": "The label for version current" 5 | }, 6 | "sidebar.guideSidebar.category.Introduction": { 7 | "message": "Introduzione", 8 | "description": "The label for category Introduction in sidebar guideSidebar" 9 | }, 10 | "sidebar.guideSidebar.category.Setting Up": { 11 | "message": "Impostazioni", 12 | "description": "The label for category Setting Up in sidebar guideSidebar" 13 | }, 14 | "sidebar.guideSidebar.category.Management": { 15 | "message": "Gestione", 16 | "description": "The label for category Management in sidebar guideSidebar" 17 | }, 18 | "sidebar.guideSidebar.category.Advanced": { 19 | "message": "Advanced", 20 | "description": "The label for category Advanced in sidebar guideSidebar" 21 | }, 22 | "sidebar.extendSidebar.category.Main Concepts": { 23 | "message": "Concetti principali", 24 | "description": "The label for category Main Concepts in sidebar extendSidebar" 25 | }, 26 | "sidebar.extendSidebar.category.Reference Guides": { 27 | "message": "Guide di riferimento", 28 | "description": "The label for category Reference Guides in sidebar extendSidebar" 29 | }, 30 | "sidebar.extendSidebar.category.Advanced Guides": { 31 | "message": "Guide Avanzate", 32 | "description": "The label for category Advanced Guides in sidebar extendSidebar" 33 | }, 34 | "sidebar.extendSidebar.category.Update Guides": { 35 | "message": "Update Guides", 36 | "description": "The label for category Update Guides in sidebar extendSidebar" 37 | }, 38 | "sidebar.internalSidebar.category.Internal Docs": { 39 | "message": "Internal Docs", 40 | "description": "The label for category Internal Docs in sidebar internalSidebar" 41 | } 42 | } -------------------------------------------------------------------------------- /i18n/it/docusaurus-plugin-content-docs/version-1.x/current.json: -------------------------------------------------------------------------------- 1 | { 2 | "version.label": { 3 | "message": "Next", 4 | "description": "The label for version current" 5 | }, 6 | "sidebar.guideSidebar.category.Introduction": { 7 | "message": "Introduzione", 8 | "description": "The label for category Introduction in sidebar guideSidebar" 9 | }, 10 | "sidebar.guideSidebar.category.Setting Up": { 11 | "message": "Impostazioni", 12 | "description": "The label for category Setting Up in sidebar guideSidebar" 13 | }, 14 | "sidebar.guideSidebar.category.Management": { 15 | "message": "Gestione", 16 | "description": "The label for category Management in sidebar guideSidebar" 17 | }, 18 | "sidebar.guideSidebar.category.Advanced": { 19 | "message": "Advanced", 20 | "description": "The label for category Advanced in sidebar guideSidebar" 21 | }, 22 | "sidebar.extendSidebar.category.Main Concepts": { 23 | "message": "Concetti principali", 24 | "description": "The label for category Main Concepts in sidebar extendSidebar" 25 | }, 26 | "sidebar.extendSidebar.category.Reference Guides": { 27 | "message": "Guide di riferimento", 28 | "description": "The label for category Reference Guides in sidebar extendSidebar" 29 | }, 30 | "sidebar.extendSidebar.category.Advanced Guides": { 31 | "message": "Guide Avanzate", 32 | "description": "The label for category Advanced Guides in sidebar extendSidebar" 33 | }, 34 | "sidebar.extendSidebar.category.Update Guides": { 35 | "message": "Update Guides", 36 | "description": "The label for category Update Guides in sidebar extendSidebar" 37 | }, 38 | "sidebar.internalSidebar.category.Internal Docs": { 39 | "message": "Internal Docs", 40 | "description": "The label for category Internal Docs in sidebar internalSidebar" 41 | } 42 | } -------------------------------------------------------------------------------- /i18n/es/docusaurus-plugin-content-docs/version-1.x/current.json: -------------------------------------------------------------------------------- 1 | { 2 | "version.label": { 3 | "message": "Next", 4 | "description": "The label for version current" 5 | }, 6 | "sidebar.guideSidebar.category.Introduction": { 7 | "message": "Introducción", 8 | "description": "The label for category Introduction in sidebar guideSidebar" 9 | }, 10 | "sidebar.guideSidebar.category.Setting Up": { 11 | "message": "Configuración", 12 | "description": "The label for category Setting Up in sidebar guideSidebar" 13 | }, 14 | "sidebar.guideSidebar.category.Management": { 15 | "message": "Gestión", 16 | "description": "The label for category Management in sidebar guideSidebar" 17 | }, 18 | "sidebar.guideSidebar.category.Advanced": { 19 | "message": "Advanced", 20 | "description": "The label for category Advanced in sidebar guideSidebar" 21 | }, 22 | "sidebar.extendSidebar.category.Main Concepts": { 23 | "message": "Conceptos Principales", 24 | "description": "The label for category Main Concepts in sidebar extendSidebar" 25 | }, 26 | "sidebar.extendSidebar.category.Reference Guides": { 27 | "message": "Guías de Referencia", 28 | "description": "The label for category Reference Guides in sidebar extendSidebar" 29 | }, 30 | "sidebar.extendSidebar.category.Advanced Guides": { 31 | "message": "Guías Avanzadas", 32 | "description": "The label for category Advanced Guides in sidebar extendSidebar" 33 | }, 34 | "sidebar.extendSidebar.category.Update Guides": { 35 | "message": "Update Guides", 36 | "description": "The label for category Update Guides in sidebar extendSidebar" 37 | }, 38 | "sidebar.internalSidebar.category.Internal Docs": { 39 | "message": "Internal Docs", 40 | "description": "The label for category Internal Docs in sidebar internalSidebar" 41 | } 42 | } --------------------------------------------------------------------------------