@intlayer/docs 5.5.11 → 5.6.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/blog/ar/intlayer_with_next-intl.md +0 -1
- package/blog/ar/list_i18n_technologies/CMS/wordpress.md +1 -1
- package/blog/ar/list_i18n_technologies/frameworks/angular.md +1 -1
- package/blog/ar/list_i18n_technologies/frameworks/flutter.md +1 -1
- package/blog/ar/list_i18n_technologies/frameworks/react-native.md +1 -1
- package/blog/ar/list_i18n_technologies/frameworks/react.md +1 -1
- package/blog/ar/list_i18n_technologies/frameworks/svelte.md +1 -1
- package/blog/ar/list_i18n_technologies/frameworks/vue.md +1 -1
- package/blog/ar/what_is_internationalization.md +2 -2
- package/blog/de/intlayer_with_next-intl.md +0 -1
- package/blog/de/list_i18n_technologies/CMS/wordpress.md +1 -1
- package/blog/de/list_i18n_technologies/frameworks/angular.md +1 -1
- package/blog/de/list_i18n_technologies/frameworks/flutter.md +1 -1
- package/blog/de/list_i18n_technologies/frameworks/react-native.md +1 -1
- package/blog/de/list_i18n_technologies/frameworks/react.md +1 -1
- package/blog/de/list_i18n_technologies/frameworks/svelte.md +1 -1
- package/blog/de/list_i18n_technologies/frameworks/vue.md +1 -1
- package/blog/de/what_is_internationalization.md +2 -2
- package/blog/en/intlayer_with_next-intl.md +0 -1
- package/blog/en/list_i18n_technologies/CMS/wordpress.md +1 -1
- package/blog/en/list_i18n_technologies/frameworks/angular.md +1 -1
- package/blog/en/list_i18n_technologies/frameworks/flutter.md +1 -1
- package/blog/en/list_i18n_technologies/frameworks/react-native.md +1 -1
- package/blog/en/list_i18n_technologies/frameworks/react.md +1 -1
- package/blog/en/list_i18n_technologies/frameworks/svelte.md +1 -1
- package/blog/en/list_i18n_technologies/frameworks/vue.md +1 -1
- package/blog/en/what_is_internationalization.md +2 -2
- package/blog/en-GB/intlayer_with_next-intl.md +0 -1
- package/blog/en-GB/list_i18n_technologies/CMS/wordpress.md +1 -1
- package/blog/en-GB/list_i18n_technologies/frameworks/angular.md +1 -1
- package/blog/en-GB/list_i18n_technologies/frameworks/flutter.md +1 -1
- package/blog/en-GB/list_i18n_technologies/frameworks/react-native.md +1 -1
- package/blog/en-GB/list_i18n_technologies/frameworks/svelte.md +1 -1
- package/blog/en-GB/list_i18n_technologies/frameworks/vue.md +1 -1
- package/blog/en-GB/what_is_internationalization.md +2 -2
- package/blog/es/intlayer_with_next-intl.md +0 -1
- package/blog/es/list_i18n_technologies/CMS/wordpress.md +1 -1
- package/blog/es/list_i18n_technologies/frameworks/angular.md +1 -1
- package/blog/es/list_i18n_technologies/frameworks/flutter.md +1 -1
- package/blog/es/list_i18n_technologies/frameworks/react-native.md +1 -1
- package/blog/es/list_i18n_technologies/frameworks/react.md +1 -1
- package/blog/es/list_i18n_technologies/frameworks/svelte.md +1 -1
- package/blog/es/list_i18n_technologies/frameworks/vue.md +1 -1
- package/blog/es/what_is_internationalization.md +2 -2
- package/blog/fr/intlayer_with_next-intl.md +0 -1
- package/blog/fr/list_i18n_technologies/CMS/wordpress.md +1 -1
- package/blog/fr/list_i18n_technologies/frameworks/angular.md +1 -1
- package/blog/fr/list_i18n_technologies/frameworks/flutter.md +1 -1
- package/blog/fr/list_i18n_technologies/frameworks/react-native.md +1 -1
- package/blog/fr/list_i18n_technologies/frameworks/react.md +1 -1
- package/blog/fr/list_i18n_technologies/frameworks/svelte.md +1 -1
- package/blog/fr/list_i18n_technologies/frameworks/vue.md +1 -1
- package/blog/fr/what_is_internationalization.md +2 -2
- package/blog/hi/list_i18n_technologies/CMS/wordpress.md +1 -1
- package/blog/hi/list_i18n_technologies/frameworks/angular.md +1 -1
- package/blog/hi/list_i18n_technologies/frameworks/flutter.md +1 -1
- package/blog/hi/list_i18n_technologies/frameworks/react-native.md +1 -1
- package/blog/hi/list_i18n_technologies/frameworks/react.md +1 -1
- package/blog/hi/list_i18n_technologies/frameworks/svelte.md +1 -1
- package/blog/hi/list_i18n_technologies/frameworks/vue.md +1 -1
- package/blog/hi/what_is_internationalization.md +2 -2
- package/blog/it/intlayer_with_next-intl.md +0 -1
- package/blog/it/list_i18n_technologies/CMS/wordpress.md +1 -1
- package/blog/it/list_i18n_technologies/frameworks/angular.md +1 -1
- package/blog/it/list_i18n_technologies/frameworks/react-native.md +1 -1
- package/blog/it/list_i18n_technologies/frameworks/react.md +1 -1
- package/blog/it/list_i18n_technologies/frameworks/svelte.md +1 -1
- package/blog/it/list_i18n_technologies/frameworks/vue.md +1 -1
- package/blog/it/what_is_internationalization.md +2 -2
- package/blog/ja/intlayer_with_next-intl.md +0 -1
- package/blog/ja/list_i18n_technologies/CMS/wordpress.md +1 -1
- package/blog/ja/list_i18n_technologies/frameworks/angular.md +1 -1
- package/blog/ja/list_i18n_technologies/frameworks/flutter.md +1 -1
- package/blog/ja/list_i18n_technologies/frameworks/react-native.md +1 -1
- package/blog/ja/list_i18n_technologies/frameworks/react.md +1 -1
- package/blog/ja/list_i18n_technologies/frameworks/svelte.md +1 -1
- package/blog/ja/list_i18n_technologies/frameworks/vue.md +1 -1
- package/blog/ja/what_is_internationalization.md +2 -2
- package/blog/ko/intlayer_with_next-intl.md +0 -1
- package/blog/ko/list_i18n_technologies/CMS/wordpress.md +1 -1
- package/blog/ko/list_i18n_technologies/frameworks/angular.md +1 -1
- package/blog/ko/list_i18n_technologies/frameworks/react-native.md +1 -1
- package/blog/ko/list_i18n_technologies/frameworks/react.md +1 -1
- package/blog/ko/list_i18n_technologies/frameworks/vue.md +1 -1
- package/blog/pt/intlayer_with_next-intl.md +0 -1
- package/blog/pt/list_i18n_technologies/CMS/wordpress.md +1 -1
- package/blog/pt/list_i18n_technologies/frameworks/angular.md +1 -1
- package/blog/pt/list_i18n_technologies/frameworks/flutter.md +1 -1
- package/blog/pt/list_i18n_technologies/frameworks/react-native.md +1 -1
- package/blog/pt/list_i18n_technologies/frameworks/react.md +1 -1
- package/blog/pt/list_i18n_technologies/frameworks/svelte.md +1 -1
- package/blog/pt/list_i18n_technologies/frameworks/vue.md +1 -1
- package/blog/pt/what_is_internationalization.md +2 -2
- package/blog/ru/intlayer_with_next-intl.md +0 -1
- package/blog/ru/list_i18n_technologies/CMS/wordpress.md +1 -1
- package/blog/ru/list_i18n_technologies/frameworks/angular.md +1 -1
- package/blog/ru/list_i18n_technologies/frameworks/flutter.md +1 -1
- package/blog/ru/list_i18n_technologies/frameworks/react-native.md +1 -1
- package/blog/ru/list_i18n_technologies/frameworks/react.md +1 -1
- package/blog/ru/list_i18n_technologies/frameworks/svelte.md +1 -1
- package/blog/ru/list_i18n_technologies/frameworks/vue.md +1 -1
- package/blog/ru/what_is_internationalization.md +2 -2
- package/blog/zh/intlayer_with_next-intl.md +0 -1
- package/blog/zh/list_i18n_technologies/CMS/wordpress.md +1 -1
- package/blog/zh/list_i18n_technologies/frameworks/angular.md +1 -1
- package/blog/zh/list_i18n_technologies/frameworks/flutter.md +1 -1
- package/blog/zh/list_i18n_technologies/frameworks/react-native.md +1 -1
- package/blog/zh/list_i18n_technologies/frameworks/react.md +1 -1
- package/blog/zh/list_i18n_technologies/frameworks/svelte.md +1 -1
- package/blog/zh/list_i18n_technologies/frameworks/vue.md +1 -1
- package/blog/zh/what_is_internationalization.md +2 -2
- package/dist/cjs/blog.cjs +2 -2
- package/dist/cjs/blog.cjs.map +1 -1
- package/dist/cjs/common.cjs +17 -6
- package/dist/cjs/common.cjs.map +1 -1
- package/dist/cjs/doc.cjs +2 -2
- package/dist/cjs/doc.cjs.map +1 -1
- package/dist/cjs/frequentQuestions.cjs +2 -2
- package/dist/cjs/frequentQuestions.cjs.map +1 -1
- package/dist/cjs/generated/blog.entry.cjs +1152 -252
- package/dist/cjs/generated/blog.entry.cjs.map +1 -1
- package/dist/cjs/generated/docs.entry.cjs +3778 -1124
- package/dist/cjs/generated/docs.entry.cjs.map +1 -1
- package/dist/cjs/generated/frequentQuestions.entry.cjs +794 -161
- package/dist/cjs/generated/frequentQuestions.entry.cjs.map +1 -1
- package/dist/cjs/generated/legal.entry.cjs +32 -31
- package/dist/cjs/generated/legal.entry.cjs.map +1 -1
- package/dist/cjs/legal.cjs +2 -2
- package/dist/cjs/legal.cjs.map +1 -1
- package/dist/esm/blog.mjs +2 -2
- package/dist/esm/blog.mjs.map +1 -1
- package/dist/esm/common.mjs +17 -6
- package/dist/esm/common.mjs.map +1 -1
- package/dist/esm/doc.mjs +2 -2
- package/dist/esm/doc.mjs.map +1 -1
- package/dist/esm/frequentQuestions.mjs +2 -2
- package/dist/esm/frequentQuestions.mjs.map +1 -1
- package/dist/esm/generated/blog.entry.mjs +1151 -252
- package/dist/esm/generated/blog.entry.mjs.map +1 -1
- package/dist/esm/generated/docs.entry.mjs +3777 -1124
- package/dist/esm/generated/docs.entry.mjs.map +1 -1
- package/dist/esm/generated/frequentQuestions.entry.mjs +793 -161
- package/dist/esm/generated/frequentQuestions.entry.mjs.map +1 -1
- package/dist/esm/generated/legal.entry.mjs +31 -31
- package/dist/esm/generated/legal.entry.mjs.map +1 -1
- package/dist/esm/legal.mjs +2 -2
- package/dist/esm/legal.mjs.map +1 -1
- package/dist/types/blog.d.ts +2 -2
- package/dist/types/blog.d.ts.map +1 -1
- package/dist/types/common.d.ts +5 -2
- package/dist/types/common.d.ts.map +1 -1
- package/dist/types/doc.d.ts +2 -2
- package/dist/types/doc.d.ts.map +1 -1
- package/dist/types/frequentQuestions.d.ts +2 -2
- package/dist/types/frequentQuestions.d.ts.map +1 -1
- package/dist/types/generated/blog.entry.d.ts.map +1 -1
- package/dist/types/generated/docs.entry.d.ts.map +1 -1
- package/dist/types/generated/frequentQuestions.entry.d.ts +1 -0
- package/dist/types/generated/frequentQuestions.entry.d.ts.map +1 -1
- package/dist/types/generated/legal.entry.d.ts.map +1 -1
- package/dist/types/legal.d.ts +2 -2
- package/dist/types/legal.d.ts.map +1 -1
- package/docs/ar/intlayer_CMS.md +1 -0
- package/docs/ar/intlayer_cli.md +292 -177
- package/docs/ar/intlayer_visual_editor.md +1 -0
- package/docs/ar/intlayer_with_angular.md +1 -0
- package/docs/ar/intlayer_with_create_react_app.md +1 -0
- package/docs/ar/intlayer_with_lynx+react.md +1 -0
- package/docs/ar/intlayer_with_nextjs_14.md +1 -0
- package/docs/ar/intlayer_with_nextjs_15.md +3 -1
- package/docs/ar/intlayer_with_nuxt.md +1 -0
- package/docs/ar/intlayer_with_react_native+expo.md +1 -0
- package/docs/ar/intlayer_with_vite+preact.md +4 -3
- package/docs/ar/intlayer_with_vite+react.md +108 -112
- package/docs/ar/intlayer_with_vite+solid.md +4 -3
- package/docs/ar/intlayer_with_vite+svelte.md +4 -3
- package/docs/ar/intlayer_with_vite+vue.md +5 -4
- package/docs/ar/mcp_server.md +126 -92
- package/docs/de/intlayer_CMS.md +1 -0
- package/docs/de/intlayer_cli.md +291 -171
- package/docs/de/intlayer_visual_editor.md +1 -0
- package/docs/de/intlayer_with_angular.md +1 -0
- package/docs/de/intlayer_with_create_react_app.md +1 -0
- package/docs/de/intlayer_with_lynx+react.md +1 -0
- package/docs/de/intlayer_with_nextjs_14.md +1 -0
- package/docs/de/intlayer_with_nextjs_15.md +3 -1
- package/docs/de/intlayer_with_nuxt.md +1 -0
- package/docs/de/intlayer_with_react_native+expo.md +1 -0
- package/docs/de/intlayer_with_vite+preact.md +4 -3
- package/docs/de/intlayer_with_vite+react.md +128 -146
- package/docs/de/intlayer_with_vite+solid.md +4 -3
- package/docs/de/intlayer_with_vite+svelte.md +4 -3
- package/docs/de/intlayer_with_vite+vue.md +5 -4
- package/docs/de/mcp_server.md +116 -112
- package/docs/en/CI_CD.md +3 -1
- package/docs/en/autoFill.md +3 -1
- package/docs/en/configuration.md +7 -3
- package/docs/en/dictionary/condition.md +3 -1
- package/docs/en/dictionary/content_extention_customization.md +3 -1
- package/docs/en/dictionary/enumeration.md +3 -1
- package/docs/en/dictionary/file.md +3 -1
- package/docs/en/dictionary/function_fetching.md +3 -1
- package/docs/en/dictionary/get_started.md +3 -1
- package/docs/en/dictionary/insertion.md +3 -1
- package/docs/en/dictionary/markdown.md +3 -1
- package/docs/en/dictionary/nesting.md +3 -1
- package/docs/en/dictionary/translation.md +3 -1
- package/docs/en/how_works_intlayer.md +3 -1
- package/docs/en/index.md +3 -1
- package/docs/en/interest_of_intlayer.md +3 -1
- package/docs/en/intlayer_CMS.md +4 -1
- package/docs/en/intlayer_cli.md +246 -136
- package/docs/en/intlayer_visual_editor.md +4 -1
- package/docs/en/intlayer_with_angular.md +4 -1
- package/docs/en/intlayer_with_create_react_app.md +4 -1
- package/docs/en/intlayer_with_express.md +3 -1
- package/docs/en/intlayer_with_lynx+react.md +4 -1
- package/docs/en/intlayer_with_nextjs_14.md +7 -1
- package/docs/en/intlayer_with_nextjs_15.md +8 -2
- package/docs/en/intlayer_with_nextjs_page_router.md +5 -1
- package/docs/en/intlayer_with_nuxt.md +4 -1
- package/docs/en/intlayer_with_react_native+expo.md +4 -1
- package/docs/en/intlayer_with_vite+preact.md +9 -4
- package/docs/en/intlayer_with_vite+react.md +18 -10
- package/docs/en/intlayer_with_vite+solid.md +7 -4
- package/docs/en/intlayer_with_vite+svelte.md +7 -4
- package/docs/en/intlayer_with_vite+vue.md +10 -5
- package/docs/en/introduction.md +3 -1
- package/docs/en/mcp_server.md +114 -80
- package/docs/en/packages/@intlayer/api/index.md +3 -1
- package/docs/en/packages/@intlayer/chokidar/index.md +3 -1
- package/docs/en/packages/@intlayer/cli/index.md +3 -1
- package/docs/en/packages/@intlayer/config/index.md +3 -1
- package/docs/en/packages/@intlayer/core/index.md +3 -1
- package/docs/en/packages/@intlayer/design-system/index.md +3 -1
- package/docs/en/packages/@intlayer/dictionary-entry/index.md +3 -1
- package/docs/en/packages/@intlayer/editor/index.md +3 -1
- package/docs/en/packages/@intlayer/editor-react/index.md +3 -1
- package/docs/en/packages/@intlayer/webpack/index.md +3 -1
- package/docs/en/packages/angular-intlayer/index.md +3 -1
- package/docs/en/packages/express-intlayer/index.md +3 -1
- package/docs/en/packages/express-intlayer/t.md +3 -1
- package/docs/en/packages/intlayer/getConfiguration.md +3 -1
- package/docs/en/packages/intlayer/getEnumeration.md +3 -1
- package/docs/en/packages/intlayer/getHTMLTextDir.md +3 -1
- package/docs/en/packages/intlayer/getLocaleLang.md +3 -1
- package/docs/en/packages/intlayer/getLocaleName.md +3 -1
- package/docs/en/packages/intlayer/getLocalizedUrl.md +3 -1
- package/docs/en/packages/intlayer/getMultilingualUrls.md +3 -1
- package/docs/en/packages/intlayer/getPathWithoutLocale.md +3 -1
- package/docs/en/packages/intlayer/getTranslation.md +3 -1
- package/docs/en/packages/intlayer/getTranslationContent.md +3 -1
- package/docs/en/packages/intlayer/index.md +3 -1
- package/docs/en/packages/intlayer-cli/index.md +3 -1
- package/docs/en/packages/intlayer-editor/index.md +3 -1
- package/docs/en/packages/lynx-intlayer/index.md +3 -1
- package/docs/en/packages/next-intlayer/index.md +3 -1
- package/docs/en/packages/next-intlayer/t.md +3 -1
- package/docs/en/packages/next-intlayer/useDictionary.md +3 -1
- package/docs/en/packages/next-intlayer/useIntlayer.md +3 -1
- package/docs/en/packages/next-intlayer/useIntlayerAsync.md +3 -1
- package/docs/en/packages/next-intlayer/useLocale.md +3 -1
- package/docs/en/packages/nuxt-intlayer/index.md +3 -1
- package/docs/en/packages/preact-intlayer/index.md +3 -1
- package/docs/en/packages/react-intlayer/index.md +3 -1
- package/docs/en/packages/react-intlayer/t.md +3 -1
- package/docs/en/packages/react-intlayer/useDictionary.md +3 -1
- package/docs/en/packages/react-intlayer/useIntlayer.md +3 -1
- package/docs/en/packages/react-intlayer/useIntlayerAsync.md +3 -1
- package/docs/en/packages/react-intlayer/useLocale.md +3 -1
- package/docs/en/packages/react-native-intlayer/index.md +3 -1
- package/docs/en/packages/react-scripts-intlayer/index.md +3 -1
- package/docs/en/packages/solid-intlayer/index.md +3 -1
- package/docs/en/packages/svelte-intlayer/index.md +3 -1
- package/docs/en/packages/vite-intlayer/index.md +3 -1
- package/docs/en/packages/vue-intlayer/index.md +3 -1
- package/docs/en/per_locale_file.md +3 -1
- package/docs/en/roadmap.md +5 -2
- package/docs/en/vs_code_extension.md +3 -1
- package/docs/en-GB/intlayer_CMS.md +1 -0
- package/docs/en-GB/intlayer_cli.md +257 -138
- package/docs/en-GB/intlayer_visual_editor.md +1 -0
- package/docs/en-GB/intlayer_with_angular.md +1 -0
- package/docs/en-GB/intlayer_with_create_react_app.md +1 -0
- package/docs/en-GB/intlayer_with_lynx+react.md +1 -0
- package/docs/en-GB/intlayer_with_nextjs_14.md +1 -0
- package/docs/en-GB/intlayer_with_nextjs_15.md +3 -1
- package/docs/en-GB/intlayer_with_nuxt.md +1 -0
- package/docs/en-GB/intlayer_with_react_native+expo.md +1 -0
- package/docs/en-GB/intlayer_with_vite+preact.md +4 -3
- package/docs/en-GB/intlayer_with_vite+react.md +71 -87
- package/docs/en-GB/intlayer_with_vite+solid.md +4 -3
- package/docs/en-GB/intlayer_with_vite+svelte.md +4 -3
- package/docs/en-GB/intlayer_with_vite+vue.md +5 -4
- package/docs/en-GB/mcp_server.md +116 -82
- package/docs/es/intlayer_CMS.md +1 -0
- package/docs/es/intlayer_cli.md +283 -164
- package/docs/es/intlayer_visual_editor.md +1 -0
- package/docs/es/intlayer_with_angular.md +1 -0
- package/docs/es/intlayer_with_create_react_app.md +1 -0
- package/docs/es/intlayer_with_lynx+react.md +1 -0
- package/docs/es/intlayer_with_nextjs_14.md +1 -0
- package/docs/es/intlayer_with_nextjs_15.md +3 -1
- package/docs/es/intlayer_with_nuxt.md +1 -0
- package/docs/es/intlayer_with_react_native+expo.md +1 -0
- package/docs/es/intlayer_with_vite+preact.md +4 -3
- package/docs/es/intlayer_with_vite+react.md +98 -98
- package/docs/es/intlayer_with_vite+solid.md +4 -3
- package/docs/es/intlayer_with_vite+svelte.md +4 -3
- package/docs/es/intlayer_with_vite+vue.md +5 -4
- package/docs/es/mcp_server.md +120 -86
- package/docs/es/vs_code_extension.md +1 -0
- package/docs/fr/intlayer_CMS.md +1 -0
- package/docs/fr/intlayer_cli.md +280 -184
- package/docs/fr/intlayer_visual_editor.md +1 -0
- package/docs/fr/intlayer_with_angular.md +1 -0
- package/docs/fr/intlayer_with_create_react_app.md +1 -0
- package/docs/fr/intlayer_with_lynx+react.md +1 -0
- package/docs/fr/intlayer_with_nextjs_14.md +1 -0
- package/docs/fr/intlayer_with_nextjs_15.md +3 -1
- package/docs/fr/intlayer_with_nuxt.md +1 -0
- package/docs/fr/intlayer_with_react_native+expo.md +1 -0
- package/docs/fr/intlayer_with_vite+preact.md +5 -4
- package/docs/fr/intlayer_with_vite+react.md +80 -69
- package/docs/fr/intlayer_with_vite+solid.md +4 -3
- package/docs/fr/intlayer_with_vite+svelte.md +4 -3
- package/docs/fr/intlayer_with_vite+vue.md +5 -4
- package/docs/fr/mcp_server.md +121 -87
- package/docs/hi/intlayer_CMS.md +1 -0
- package/docs/hi/intlayer_cli.md +295 -174
- package/docs/hi/intlayer_visual_editor.md +1 -0
- package/docs/hi/intlayer_with_angular.md +1 -0
- package/docs/hi/intlayer_with_create_react_app.md +1 -0
- package/docs/hi/intlayer_with_lynx+react.md +1 -0
- package/docs/hi/intlayer_with_nextjs_14.md +1 -0
- package/docs/hi/intlayer_with_nextjs_15.md +3 -1
- package/docs/hi/intlayer_with_nuxt.md +1 -0
- package/docs/hi/intlayer_with_react_native+expo.md +1 -0
- package/docs/hi/intlayer_with_vite+preact.md +4 -3
- package/docs/hi/intlayer_with_vite+react.md +114 -111
- package/docs/hi/intlayer_with_vite+solid.md +4 -3
- package/docs/hi/intlayer_with_vite+svelte.md +4 -3
- package/docs/hi/intlayer_with_vite+vue.md +5 -4
- package/docs/hi/mcp_server.md +118 -84
- package/docs/it/intlayer_CMS.md +1 -0
- package/docs/it/intlayer_cli.md +282 -167
- package/docs/it/intlayer_visual_editor.md +1 -0
- package/docs/it/intlayer_with_angular.md +1 -0
- package/docs/it/intlayer_with_create_react_app.md +1 -0
- package/docs/it/intlayer_with_lynx+react.md +1 -0
- package/docs/it/intlayer_with_nextjs_14.md +1 -0
- package/docs/it/intlayer_with_nextjs_15.md +3 -1
- package/docs/it/intlayer_with_nuxt.md +1 -0
- package/docs/it/intlayer_with_react_native+expo.md +1 -0
- package/docs/it/intlayer_with_vite+preact.md +4 -3
- package/docs/it/intlayer_with_vite+react.md +163 -116
- package/docs/it/intlayer_with_vite+solid.md +4 -3
- package/docs/it/intlayer_with_vite+svelte.md +4 -3
- package/docs/it/intlayer_with_vite+vue.md +4 -4
- package/docs/it/mcp_server.md +120 -86
- package/docs/ja/intlayer_CMS.md +1 -0
- package/docs/ja/intlayer_cli.md +285 -168
- package/docs/ja/intlayer_visual_editor.md +1 -0
- package/docs/ja/intlayer_with_angular.md +1 -0
- package/docs/ja/intlayer_with_create_react_app.md +1 -0
- package/docs/ja/intlayer_with_lynx+react.md +1 -0
- package/docs/ja/intlayer_with_nextjs_14.md +1 -0
- package/docs/ja/intlayer_with_nextjs_15.md +3 -1
- package/docs/ja/intlayer_with_nuxt.md +1 -0
- package/docs/ja/intlayer_with_react_native+expo.md +1 -0
- package/docs/ja/intlayer_with_vite+preact.md +4 -3
- package/docs/ja/intlayer_with_vite+react.md +160 -222
- package/docs/ja/intlayer_with_vite+solid.md +4 -3
- package/docs/ja/intlayer_with_vite+svelte.md +4 -3
- package/docs/ja/intlayer_with_vite+vue.md +5 -4
- package/docs/ja/mcp_server.md +121 -85
- package/docs/ko/intlayer_CMS.md +1 -0
- package/docs/ko/intlayer_cli.md +291 -175
- package/docs/ko/intlayer_visual_editor.md +1 -0
- package/docs/ko/intlayer_with_angular.md +1 -0
- package/docs/ko/intlayer_with_create_react_app.md +1 -0
- package/docs/ko/intlayer_with_lynx+react.md +1 -0
- package/docs/ko/intlayer_with_nextjs_14.md +1 -0
- package/docs/ko/intlayer_with_nextjs_15.md +3 -1
- package/docs/ko/intlayer_with_nuxt.md +1 -0
- package/docs/ko/intlayer_with_react_native+expo.md +1 -0
- package/docs/ko/intlayer_with_vite+preact.md +4 -3
- package/docs/ko/intlayer_with_vite+react.md +123 -152
- package/docs/ko/intlayer_with_vite+solid.md +4 -3
- package/docs/ko/intlayer_with_vite+svelte.md +4 -3
- package/docs/ko/intlayer_with_vite+vue.md +5 -4
- package/docs/ko/mcp_server.md +117 -83
- package/docs/ko/packages/intlayer/getLocalizedUrl.md +1 -23
- package/docs/pt/intlayer_CMS.md +1 -0
- package/docs/pt/intlayer_cli.md +274 -154
- package/docs/pt/intlayer_visual_editor.md +1 -0
- package/docs/pt/intlayer_with_angular.md +1 -0
- package/docs/pt/intlayer_with_create_react_app.md +1 -0
- package/docs/pt/intlayer_with_lynx+react.md +1 -0
- package/docs/pt/intlayer_with_nextjs_14.md +1 -0
- package/docs/pt/intlayer_with_nextjs_15.md +3 -1
- package/docs/pt/intlayer_with_nuxt.md +1 -0
- package/docs/pt/intlayer_with_react_native+expo.md +1 -0
- package/docs/pt/intlayer_with_vite+preact.md +4 -3
- package/docs/pt/intlayer_with_vite+react.md +117 -136
- package/docs/pt/intlayer_with_vite+solid.md +4 -3
- package/docs/pt/intlayer_with_vite+svelte.md +4 -3
- package/docs/pt/intlayer_with_vite+vue.md +4 -4
- package/docs/pt/mcp_server.md +121 -87
- package/docs/ru/intlayer_CMS.md +1 -0
- package/docs/ru/intlayer_cli.md +287 -170
- package/docs/ru/intlayer_visual_editor.md +1 -0
- package/docs/ru/intlayer_with_angular.md +1 -0
- package/docs/ru/intlayer_with_create_react_app.md +1 -0
- package/docs/ru/intlayer_with_lynx+react.md +1 -0
- package/docs/ru/intlayer_with_nextjs_14.md +1 -0
- package/docs/ru/intlayer_with_nextjs_15.md +3 -1
- package/docs/ru/intlayer_with_nuxt.md +1 -0
- package/docs/ru/intlayer_with_react_native+expo.md +1 -0
- package/docs/ru/intlayer_with_vite+preact.md +4 -3
- package/docs/ru/intlayer_with_vite+react.md +105 -87
- package/docs/ru/intlayer_with_vite+solid.md +4 -3
- package/docs/ru/intlayer_with_vite+svelte.md +4 -3
- package/docs/ru/intlayer_with_vite+vue.md +5 -4
- package/docs/ru/mcp_server.md +119 -85
- package/docs/zh/intlayer_CMS.md +1 -0
- package/docs/zh/intlayer_cli.md +275 -155
- package/docs/zh/intlayer_visual_editor.md +1 -0
- package/docs/zh/intlayer_with_angular.md +1 -0
- package/docs/zh/intlayer_with_create_react_app.md +1 -0
- package/docs/zh/intlayer_with_lynx+react.md +1 -0
- package/docs/zh/intlayer_with_nextjs_14.md +1 -0
- package/docs/zh/intlayer_with_nextjs_15.md +3 -1
- package/docs/zh/intlayer_with_nuxt.md +1 -0
- package/docs/zh/intlayer_with_react_native+expo.md +1 -0
- package/docs/zh/intlayer_with_vite+preact.md +4 -3
- package/docs/zh/intlayer_with_vite+react.md +154 -188
- package/docs/zh/intlayer_with_vite+solid.md +4 -3
- package/docs/zh/intlayer_with_vite+svelte.md +4 -3
- package/docs/zh/intlayer_with_vite+vue.md +5 -4
- package/docs/zh/mcp_server.md +119 -86
- package/docs/zh/packages/intlayer/getLocalizedUrl.md +1 -23
- package/frequent_questions/ar/build_error_CI_CD.md +75 -0
- package/frequent_questions/de/build_error_CI_CD.md +75 -0
- package/frequent_questions/en/build_error_CI_CD.md +75 -0
- package/frequent_questions/en-GB/build_error_CI_CD.md +75 -0
- package/frequent_questions/es/build_error_CI_CD.md +75 -0
- package/frequent_questions/fr/build_error_CI_CD.md +75 -0
- package/frequent_questions/hi/build_error_CI_CD.md +75 -0
- package/frequent_questions/it/build_error_CI_CD.md +75 -0
- package/frequent_questions/ja/build_error_CI_CD.md +75 -0
- package/frequent_questions/ja/intlayer_command_undefined.md +3 -3
- package/frequent_questions/ko/build_error_CI_CD.md +75 -0
- package/frequent_questions/ko/intlayer_command_undefined.md +3 -3
- package/frequent_questions/pt/build_error_CI_CD.md +75 -0
- package/frequent_questions/ru/build_error_CI_CD.md +75 -0
- package/frequent_questions/zh/build_error_CI_CD.md +75 -0
- package/frequent_questions/zh/intlayer_command_undefined.md +3 -3
- package/legal/ar/privacy_notice.md +83 -0
- package/legal/ar/terms_of_service.md +55 -0
- package/legal/de/privacy_notice.md +83 -0
- package/legal/de/terms_of_service.md +55 -0
- package/legal/en/privacy_notice.md +83 -0
- package/legal/en/terms_of_service.md +55 -0
- package/legal/en-GB/privacy_notice.md +83 -0
- package/legal/en-GB/terms_of_service.md +55 -0
- package/legal/es/privacy_notice.md +83 -0
- package/legal/es/terms_of_service.md +55 -0
- package/legal/fr/privacy_notice.md +83 -0
- package/legal/fr/terms_of_service.md +55 -0
- package/legal/hi/privacy_notice.md +83 -0
- package/legal/hi/terms_of_service.md +55 -0
- package/legal/it/privacy_notice.md +83 -0
- package/legal/it/terms_of_service.md +55 -0
- package/legal/ja/privacy_notice.md +83 -0
- package/legal/ja/terms_of_service.md +55 -0
- package/legal/ko/privacy_notice.md +83 -0
- package/legal/ko/terms_of_service.md +55 -0
- package/legal/pt/privacy_notice.md +83 -0
- package/legal/pt/terms_of_service.md +55 -0
- package/legal/ru/privacy_notice.md +83 -0
- package/legal/ru/terms_of_service.md +55 -0
- package/legal/zh/privacy_notice.md +83 -0
- package/legal/zh/terms_of_service.md +55 -0
- package/package.json +12 -11
- package/src/blog.ts +6 -4
- package/src/common.ts +25 -7
- package/src/doc.ts +6 -4
- package/src/frequentQuestions.ts +6 -4
- package/src/generated/blog.entry.ts +1177 -280
- package/src/generated/docs.entry.ts +3868 -1217
- package/src/generated/frequentQuestions.entry.ts +808 -178
- package/src/generated/legal.entry.ts +34 -36
- package/src/legal.ts +6 -4
|
@@ -0,0 +1,75 @@
|
|
|
1
|
+
---
|
|
2
|
+
createdAt: 2025-05-20
|
|
3
|
+
updatedAt: 2025-06-29
|
|
4
|
+
title: Ошибка сборки в CI/CD
|
|
5
|
+
description: Узнайте, как исправить ошибки сборки, возникающие в средах CI/CD.
|
|
6
|
+
keywords:
|
|
7
|
+
- сборка
|
|
8
|
+
- ошибка
|
|
9
|
+
- ci
|
|
10
|
+
- cd
|
|
11
|
+
- конвейер
|
|
12
|
+
- intlayer
|
|
13
|
+
- словари
|
|
14
|
+
- next.js
|
|
15
|
+
- предварительная сборка
|
|
16
|
+
- автоматизация
|
|
17
|
+
slugs:
|
|
18
|
+
- doc
|
|
19
|
+
- faq
|
|
20
|
+
- build-error-ci-cd
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
# Ошибка при сборке в CI/CD
|
|
24
|
+
|
|
25
|
+
Если вы получаете ошибку такого вида в Next.js:
|
|
26
|
+
|
|
27
|
+
```text
|
|
28
|
+
Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error
|
|
29
|
+
```
|
|
30
|
+
|
|
31
|
+
Вот несколько решений:
|
|
32
|
+
|
|
33
|
+
## 1. Отсутствуют словари
|
|
34
|
+
|
|
35
|
+
Убедитесь, что словари собираются на этапе сборки.
|
|
36
|
+
|
|
37
|
+
Часто сборка работает локально, но не на CI/CD. Причина в том, что локально каталог `.intlayer` присутствует, а на CI/CD его нет, так как он исключён из сборки.
|
|
38
|
+
|
|
39
|
+
Вы можете исправить это, добавив скрипт предварительной сборки (prebuild) в `package.json` вашего проекта.
|
|
40
|
+
|
|
41
|
+
```json5 fileName=package.json
|
|
42
|
+
{
|
|
43
|
+
// ...
|
|
44
|
+
"scripts": {
|
|
45
|
+
"prebuild": "npx intlayer dictionaries build", // Будет выполнен перед сборкой
|
|
46
|
+
"build": "next build",
|
|
47
|
+
},
|
|
48
|
+
}
|
|
49
|
+
```
|
|
50
|
+
|
|
51
|
+
> Обратите внимание, что если вы используете функцию `withIntlayer` или эквивалентный плагин для сборщика вашего фреймворка, скрипт предварительной сборки будет выполнен перед сборкой.
|
|
52
|
+
|
|
53
|
+
## 2. Отсутствие переменных окружения во время сборки или выполнения
|
|
54
|
+
|
|
55
|
+
В контейнере или на платформе с автоматическим деплоем рекомендуется исключать файл `.env` из сборки.
|
|
56
|
+
|
|
57
|
+
```text fileName=".gitignore or .dockerignore"
|
|
58
|
+
# Переменные окружения
|
|
59
|
+
.env
|
|
60
|
+
**/.env
|
|
61
|
+
.env.*
|
|
62
|
+
**/.env.*
|
|
63
|
+
```
|
|
64
|
+
|
|
65
|
+
Если ваши переменные окружения недоступны во время сборки, будет выброшена ошибка.
|
|
66
|
+
|
|
67
|
+
```ts
|
|
68
|
+
import { Metadata } from "next";
|
|
69
|
+
|
|
70
|
+
export const generateMetadata = async ({ params }): Promise<Metadata> => ({
|
|
71
|
+
metadataBase: new URL(process.env.NEXT_PUBLIC_URL), // Базовый URL из переменной окружения
|
|
72
|
+
});
|
|
73
|
+
```
|
|
74
|
+
|
|
75
|
+
Вероятно, это не связано с Intlayer. Поэтому проверьте ваши переменные окружения во время сборки на вашей CI/CD платформе.
|
|
@@ -0,0 +1,75 @@
|
|
|
1
|
+
---
|
|
2
|
+
createdAt: 2025-05-20
|
|
3
|
+
updatedAt: 2025-06-29
|
|
4
|
+
title: CI/CD 中的构建错误
|
|
5
|
+
description: 了解如何修复在 CI/CD 环境中发生的构建错误。
|
|
6
|
+
keywords:
|
|
7
|
+
- 构建
|
|
8
|
+
- 错误
|
|
9
|
+
- ci
|
|
10
|
+
- cd
|
|
11
|
+
- 流水线
|
|
12
|
+
- intlayer
|
|
13
|
+
- 字典
|
|
14
|
+
- next.js
|
|
15
|
+
- 预构建
|
|
16
|
+
- 自动化
|
|
17
|
+
slugs:
|
|
18
|
+
- doc
|
|
19
|
+
- faq
|
|
20
|
+
- build-error-ci-cd
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
# CI/CD 中的构建错误
|
|
24
|
+
|
|
25
|
+
如果你在 Next.js 中遇到如下错误:
|
|
26
|
+
|
|
27
|
+
```text
|
|
28
|
+
Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error
|
|
29
|
+
```
|
|
30
|
+
|
|
31
|
+
这里有一些解决方案:
|
|
32
|
+
|
|
33
|
+
## 1. 缺少字典文件
|
|
34
|
+
|
|
35
|
+
确保字典文件在构建阶段被生成。
|
|
36
|
+
|
|
37
|
+
本地构建通常可以正常工作,但在 CI/CD 上却不行。原因是本地存在 `.intlayer` 目录,而在 CI/CD 上由于被排除在构建之外,所以不存在该目录。
|
|
38
|
+
|
|
39
|
+
你可以通过在项目的 `package.json` 中添加预构建脚本来解决此问题。
|
|
40
|
+
|
|
41
|
+
```json5 fileName=package.json
|
|
42
|
+
{
|
|
43
|
+
// ...
|
|
44
|
+
"scripts": {
|
|
45
|
+
"prebuild": "npx intlayer dictionaries build", // 构建前运行
|
|
46
|
+
"build": "next build",
|
|
47
|
+
},
|
|
48
|
+
}
|
|
49
|
+
```
|
|
50
|
+
|
|
51
|
+
> 注意,如果你使用 `withIntlayer` 函数,或者你框架的等效打包插件,预构建脚本会在构建之前自动运行。
|
|
52
|
+
|
|
53
|
+
## 2. 构建/运行时缺少环境变量
|
|
54
|
+
|
|
55
|
+
在容器或自动部署平台中,建议将 `.env` 文件排除在构建之外。
|
|
56
|
+
|
|
57
|
+
```text fileName=".gitignore or .dockerignore"
|
|
58
|
+
# 环境变量
|
|
59
|
+
.env
|
|
60
|
+
**/.env
|
|
61
|
+
.env.*
|
|
62
|
+
**/.env.*
|
|
63
|
+
```
|
|
64
|
+
|
|
65
|
+
如果你的环境变量在构建时不可用,将会抛出错误。
|
|
66
|
+
|
|
67
|
+
```ts
|
|
68
|
+
import { Metadata } from "next";
|
|
69
|
+
|
|
70
|
+
export const generateMetadata = async ({ params }): Promise<Metadata> => ({
|
|
71
|
+
metadataBase: new URL(process.env.NEXT_PUBLIC_URL), // 使用环境变量设置元数据基础URL
|
|
72
|
+
});
|
|
73
|
+
```
|
|
74
|
+
|
|
75
|
+
这很可能与 Intlayer 无关。所以请检查你在 CI/CD 平台上构建时的环境变量配置。
|
|
@@ -144,7 +144,7 @@ npm --version
|
|
|
144
144
|
11. **检查权限问题**
|
|
145
145
|
如果遇到权限错误:
|
|
146
146
|
|
|
147
|
-
|
|
147
|
+
```bash
|
|
148
148
|
# 对于基于 Unix 的系统
|
|
149
149
|
sudo npm install -g intlayer
|
|
150
150
|
|
|
@@ -152,5 +152,5 @@ sudo npm install -g intlayer
|
|
|
152
152
|
mkdir ~/.npm-global
|
|
153
153
|
npm config set prefix '~/.npm-global'
|
|
154
154
|
# 添加到你的 ~/.profile 或 ~/.bashrc 文件中:
|
|
155
|
-
export PATH=~/.npm-global/bin:$PATH
|
|
156
|
-
|
|
155
|
+
export PATH=~/.npm-global/bin:$PATH
|
|
156
|
+
```
|
|
@@ -0,0 +1,83 @@
|
|
|
1
|
+
---
|
|
2
|
+
createdAt: 2025-04-18
|
|
3
|
+
updatedAt: 2025-06-29
|
|
4
|
+
title: إشعار الخصوصية في Intlayer
|
|
5
|
+
description: اكتشف كيف تتعامل Intlayer مع المعلومات التي يتم جمعها من خلال موقعنا الإلكتروني ونظام إدارة المحتوى الخاص بنا. اتبع الوثائق لفهم التنسيقات المختلفة وحالات الاستخدام.
|
|
6
|
+
keywords:
|
|
7
|
+
- التدويل
|
|
8
|
+
- التوثيق
|
|
9
|
+
- Intlayer
|
|
10
|
+
- الخصوصية
|
|
11
|
+
- الإشعار
|
|
12
|
+
- الكوكيز
|
|
13
|
+
- التتبع
|
|
14
|
+
- التحليلات
|
|
15
|
+
- تحليلات جوجل
|
|
16
|
+
- بكسل ميتا (فيسبوك)
|
|
17
|
+
- المصادقة
|
|
18
|
+
- بيانات المستخدم
|
|
19
|
+
slugs:
|
|
20
|
+
- privacy-notice
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
# إشعار الخصوصية في Intlayer
|
|
24
|
+
|
|
25
|
+
## المقدمة
|
|
26
|
+
|
|
27
|
+
في Intlayer، نحن نأخذ الخصوصية على محمل الجد. يشرح هذا الإشعار كيف نتعامل مع المعلومات التي يتم جمعها من خلال موقعنا الإلكتروني ونظام إدارة المحتوى الخاص بنا.
|
|
28
|
+
|
|
29
|
+
## الاتصال
|
|
30
|
+
|
|
31
|
+
إذا كان لديك أي أسئلة أو مخاوف بشأن الخصوصية، يرجى الاتصال بنا على العنوان التالي: [contact@intlayer.org](mailto:contact@intlayer.org).
|
|
32
|
+
|
|
33
|
+
## استخدام الكوكيز وتقنيات التتبع
|
|
34
|
+
|
|
35
|
+
نستخدم **تحليلات جوجل** و**بكسل ميتا (فيسبوك)** لتحليل استخدام موقعنا الإلكتروني وتحسين خدماتنا. تولد هذه الأدوات إحصائيات ومعلومات أخرى حول الموقع باستخدام الكوكيز المخزنة على أجهزة المستخدمين.
|
|
36
|
+
|
|
37
|
+
لمزيد من المعلومات:
|
|
38
|
+
|
|
39
|
+
- [سياسة الخصوصية لجوجل](https://policies.google.com/privacy)
|
|
40
|
+
- [سياسة الخصوصية لميتا](https://www.facebook.com/privacy/policy)
|
|
41
|
+
|
|
42
|
+
## المصادقة وبيانات المستخدم
|
|
43
|
+
|
|
44
|
+
يتطلب الوصول إلى نظام إدارة المحتوى Intlayer مصادقة المستخدم. نحن نقدم كل من المصادقة عبر البريد الإلكتروني/كلمة المرور وتسجيل الدخول عبر طرف ثالث باستخدام **جوجل** و**GitHub**.
|
|
45
|
+
|
|
46
|
+
أثناء عملية المصادقة، نقوم بجمع:
|
|
47
|
+
|
|
48
|
+
- عنوان البريد الإلكتروني
|
|
49
|
+
- اسم العرض (أو الاسم المختار)
|
|
50
|
+
|
|
51
|
+
يمكن للمستخدمين أيضًا الوصول إلى نظام إدارة المحتوى عبر رموز وصول مرتبطة بحسابهم. ترتبط هذه الرموز بنفس بيانات المصادقة.
|
|
52
|
+
|
|
53
|
+
## تخزين البيانات والأمان
|
|
54
|
+
|
|
55
|
+
يتم تخزين بيانات مصادقة المستخدم في **قاعدة بيانات MongoDB** مستضافة على **cloud.mongodb.com**:
|
|
56
|
+
|
|
57
|
+
- **المنطقة:** AWS / أوريغون (us-west-2)
|
|
58
|
+
- **النوع:** مجموعة نسخ متماثلة (3 عقد)
|
|
59
|
+
- **أمان كلمة المرور:** جميع كلمات المرور مشفرة باستخدام ممارسات معيارية في الصناعة.
|
|
60
|
+
|
|
61
|
+
نحن لا نخزن أي بيانات شخصية غير ضرورية تتجاوز ما هو مطلوب للمصادقة والوصول الآمن إلى نظام إدارة المحتوى.
|
|
62
|
+
|
|
63
|
+
## مشاركة البيانات مع أطراف ثالثة
|
|
64
|
+
|
|
65
|
+
نحن لا نبيع أو نشارك بياناتك الشخصية مع أطراف ثالثة، إلا إذا كان ذلك مطلوبًا لأغراض التحليلات (Google Analytics، Facebook Pixel) أو كجزء من عملية المصادقة (تسجيل الدخول عبر Google أو GitHub).
|
|
66
|
+
|
|
67
|
+
## حقوق المستخدمين
|
|
68
|
+
|
|
69
|
+
بصفتك مستخدمًا، لديك الحق في:
|
|
70
|
+
|
|
71
|
+
- الوصول إلى البيانات الشخصية التي نحتفظ بها عنك
|
|
72
|
+
- طلب تصحيح أو حذف بياناتك
|
|
73
|
+
- إلغاء الوصول أو حذف حسابك
|
|
74
|
+
|
|
75
|
+
لأي طلب يتعلق ببياناتك، يرجى الاتصال بنا على [contact@intlayer.org](mailto:contact@intlayer.org).
|
|
76
|
+
|
|
77
|
+
## التغييرات على هذا الإشعار
|
|
78
|
+
|
|
79
|
+
قد نقوم بتحديث إشعار الخصوصية هذا من وقت لآخر. يُنصح المستخدمون بالتحقق بانتظام من هذه الصفحة للبقاء على اطلاع بأي تغييرات.
|
|
80
|
+
|
|
81
|
+
---
|
|
82
|
+
|
|
83
|
+
أخبرنا إذا كنت ترغب في نبرة أكثر رسمية، أو إضافة إشارات إلى GDPR/CCPA، أو تكييفها لصفحة قانونية على موقعك.
|
|
@@ -0,0 +1,55 @@
|
|
|
1
|
+
---
|
|
2
|
+
createdAt: 2025-04-18
|
|
3
|
+
updatedAt: 2025-06-29
|
|
4
|
+
title: شروط خدمة Intlayer
|
|
5
|
+
description: اكتشف كيف يتعامل Intlayer مع المعلومات التي يتم جمعها من خلال موقعنا الإلكتروني ونظام إدارة المحتوى الخاص بنا. اتبع الوثائق لفهم التنسيقات المختلفة وحالات الاستخدام.
|
|
6
|
+
keywords:
|
|
7
|
+
- التدويل
|
|
8
|
+
- التوثيق
|
|
9
|
+
- Intlayer
|
|
10
|
+
- شروط الخدمة
|
|
11
|
+
- الخدمة
|
|
12
|
+
- الاستخدام
|
|
13
|
+
- الترخيص
|
|
14
|
+
- المسؤولية
|
|
15
|
+
- الخصوصية
|
|
16
|
+
- المساهمات
|
|
17
|
+
- النسبة
|
|
18
|
+
- تعديل الشروط
|
|
19
|
+
slugs:
|
|
20
|
+
- terms-of-service
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
# شروط استخدام Intlayer
|
|
24
|
+
|
|
25
|
+
## 1. قبول الشروط
|
|
26
|
+
|
|
27
|
+
باستخدامك Intlayer، فإنك توافق على الالتزام بشروط الاستخدام هذه. إذا لم تقبل هذه الشروط، يرجى عدم استخدام الأداة.
|
|
28
|
+
|
|
29
|
+
## 2. الترخيص
|
|
30
|
+
|
|
31
|
+
يتم توزيع Intlayer بموجب **رخصة Apache 2.0** التي تسمح باستخدام وتعديل وتوزيع الكود لكل من المشاريع مفتوحة المصدر والتجارية. يُسمح للمستخدمين بتعديل الشيفرة المصدرية وتقديم المساهمات عبر طلبات السحب وفقًا للإرشادات الموضحة في [دليل المساهمات](https://github.com/aymericzip/intlayer/blob/main/CONTRIBUTING.md). يُحظر بشدة سرقة الشيفرة للاستخدام التجاري.
|
|
32
|
+
|
|
33
|
+
## 3. الاستخدام التجاري
|
|
34
|
+
|
|
35
|
+
يسمح لك باستخدام Intlayer للمشاريع التجارية. ومع ذلك، يُحظر إعادة استخدام الشيفرة لإنشاء أدوات منافسة مباشرة تعتمد على Intlayer دون تحويل كبير أو إضافة قيمة جوهرية.
|
|
36
|
+
|
|
37
|
+
## 4. المسؤولية
|
|
38
|
+
|
|
39
|
+
يسعى القائمون على صيانة Intlayer إلى تصحيح الأخطاء ومشاكل الأمان بمجرد اكتشافها. ومع ذلك، فإنهم ينفون أي مسؤولية عن الأضرار الناتجة عن مثل هذه المشاكل على بنى المستخدمين التحتية. نشجع المستخدمين على الإبلاغ عن المشاكل عبر [نظام تتبع القضايا](https://github.com/aymericzip/intlayer/issues).
|
|
40
|
+
|
|
41
|
+
## 5. الخصوصية
|
|
42
|
+
|
|
43
|
+
لا يقوم Intlayer بجمع أو تخزين أي بيانات شخصية للمستخدمين.
|
|
44
|
+
|
|
45
|
+
## 6. المساهمات
|
|
46
|
+
|
|
47
|
+
يُشجع المستخدمون على المساهمة في Intlayer باتباع الإرشادات المقدمة في دليل المساهمة الخاص بنا. يجب أن يلتزم أي كود مقدم بمعايير الجودة المعتمدة وسيتم مراجعته من قبل القائمين على الصيانة قبل دمجه.
|
|
48
|
+
|
|
49
|
+
## 7. النسبة
|
|
50
|
+
|
|
51
|
+
يجب أن تُعطي أي أداة تم تطويرها لتوسيع أو استخدام كود Intlayer اعترافًا واضحًا لـ Intlayer كأساس للكود. يجب أن يكون هذا الاعتراف مرئيًا في كود المصدر وكذلك في أي وثائق للمستخدم أو ترويجية.
|
|
52
|
+
|
|
53
|
+
## 8. تعديل الشروط
|
|
54
|
+
|
|
55
|
+
يجوز تعديل شروط الاستخدام هذه في أي وقت. سيتم إعلام المستخدمين بأي تغييرات جوهرية في شروط الاستخدام ويجب عليهم قبول التغييرات للاستمرار في استخدام Intlayer.
|
|
@@ -0,0 +1,83 @@
|
|
|
1
|
+
---
|
|
2
|
+
createdAt: 2025-04-18
|
|
3
|
+
updatedAt: 2025-06-29
|
|
4
|
+
title: Intlayer Datenschutzhinweis
|
|
5
|
+
description: Entdecken Sie, wie Intlayer Informationen verarbeitet, die über unsere Website und das CMS gesammelt werden. Folgen Sie der Dokumentation, um die verschiedenen Formate und Anwendungsfälle zu verstehen.
|
|
6
|
+
keywords:
|
|
7
|
+
- Internationalisierung
|
|
8
|
+
- Dokumentation
|
|
9
|
+
- Intlayer
|
|
10
|
+
- Datenschutz
|
|
11
|
+
- Hinweis
|
|
12
|
+
- Cookies
|
|
13
|
+
- Tracking
|
|
14
|
+
- Analyse
|
|
15
|
+
- Google Analytics
|
|
16
|
+
- Meta (Facebook) Pixel
|
|
17
|
+
- Authentifizierung
|
|
18
|
+
- Benutzerdaten
|
|
19
|
+
slugs:
|
|
20
|
+
- privacy-notice
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
# Intlayer Datenschutzhinweis
|
|
24
|
+
|
|
25
|
+
## Einführung
|
|
26
|
+
|
|
27
|
+
Bei Intlayer nehmen wir den Datenschutz ernst. Dieser Hinweis erklärt, wie wir Informationen verarbeiten, die über unsere Website und das CMS gesammelt werden.
|
|
28
|
+
|
|
29
|
+
## Kontakt
|
|
30
|
+
|
|
31
|
+
Wenn Sie Fragen oder Bedenken zum Datenschutz haben, kontaktieren Sie uns bitte unter folgender Adresse: [contact@intlayer.org](mailto:contact@intlayer.org).
|
|
32
|
+
|
|
33
|
+
## Verwendung von Cookies und Tracking-Technologien
|
|
34
|
+
|
|
35
|
+
Wir verwenden **Google Analytics** und das **Meta (Facebook) Pixel**, um die Nutzung unserer Website zu analysieren und unsere Dienste zu verbessern. Diese Tools erzeugen Statistiken und andere Informationen über die Website, indem sie Cookies auf den Geräten der Nutzer speichern.
|
|
36
|
+
|
|
37
|
+
Für weitere Informationen:
|
|
38
|
+
|
|
39
|
+
- [Datenschutzerklärung von Google](https://policies.google.com/privacy)
|
|
40
|
+
- [Datenschutzerklärung von Meta](https://www.facebook.com/privacy/policy)
|
|
41
|
+
|
|
42
|
+
## Authentifizierung und Benutzerdaten
|
|
43
|
+
|
|
44
|
+
Der Zugriff auf das Intlayer CMS erfordert eine Benutzerauthentifizierung. Wir bieten sowohl eine E-Mail/Passwort-Authentifizierung als auch eine Anmeldung über Drittanbieter wie **Google** und **GitHub** an.
|
|
45
|
+
|
|
46
|
+
Während des Authentifizierungsprozesses erfassen wir:
|
|
47
|
+
|
|
48
|
+
- E-Mail-Adresse
|
|
49
|
+
- Anzeigename (oder gewählter Name)
|
|
50
|
+
|
|
51
|
+
Benutzer können auch über Zugriffstoken, die mit ihrem Konto verknüpft sind, auf das CMS zugreifen. Diese Token sind an dieselben Authentifizierungsdaten gebunden.
|
|
52
|
+
|
|
53
|
+
## Datenspeicherung und Sicherheit
|
|
54
|
+
|
|
55
|
+
Die Authentifizierungsdaten der Benutzer werden in einer **MongoDB-Datenbank** gespeichert, die auf **cloud.mongodb.com** gehostet wird:
|
|
56
|
+
|
|
57
|
+
- **Region:** AWS / Oregon (us-west-2)
|
|
58
|
+
- **Typ:** Replica Set (3 Knoten)
|
|
59
|
+
- **Passwortsicherheit:** Alle Passwörter werden nach branchenüblichen Standards gehasht.
|
|
60
|
+
|
|
61
|
+
Wir speichern keine unnötigen personenbezogenen Daten über das hinaus, was für die Authentifizierung und den sicheren Zugriff auf das CMS erforderlich ist.
|
|
62
|
+
|
|
63
|
+
## Datenweitergabe an Dritte
|
|
64
|
+
|
|
65
|
+
Wir verkaufen oder teilen Ihre persönlichen Daten **nicht** mit Dritten, außer wenn dies für Analysezwecke (Google Analytics, Facebook Pixel) oder im Rahmen des Authentifizierungsprozesses (Google- oder GitHub-Anmeldung) erforderlich ist.
|
|
66
|
+
|
|
67
|
+
## Rechte der Nutzer
|
|
68
|
+
|
|
69
|
+
Als Nutzer haben Sie das Recht:
|
|
70
|
+
|
|
71
|
+
- Zugriff auf die persönlichen Daten zu erhalten, die wir über Sie speichern
|
|
72
|
+
- die Korrektur oder Löschung Ihrer Daten zu verlangen
|
|
73
|
+
- den Zugriff zu widerrufen oder Ihr Konto zu löschen
|
|
74
|
+
|
|
75
|
+
Für Anfragen bezüglich Ihrer Daten kontaktieren Sie uns bitte unter [contact@intlayer.org](mailto:contact@intlayer.org).
|
|
76
|
+
|
|
77
|
+
## Änderungen dieser Mitteilung
|
|
78
|
+
|
|
79
|
+
Wir können diese Datenschutzerklärung von Zeit zu Zeit aktualisieren. Nutzer werden empfohlen, diese Seite regelmäßig zu überprüfen, um über Änderungen informiert zu bleiben.
|
|
80
|
+
|
|
81
|
+
---
|
|
82
|
+
|
|
83
|
+
Lassen Sie mich wissen, wenn Sie einen formelleren Ton wünschen, GDPR/CCPA-Erwähnungen hinzufügen möchten oder die Seite für eine rechtliche Seite auf Ihrer Website anpassen wollen.
|
|
@@ -0,0 +1,55 @@
|
|
|
1
|
+
---
|
|
2
|
+
createdAt: 2025-04-18
|
|
3
|
+
updatedAt: 2025-06-29
|
|
4
|
+
title: Intlayer Nutzungsbedingungen
|
|
5
|
+
description: Entdecken Sie, wie Intlayer Informationen verarbeitet, die über unsere Website und das CMS gesammelt werden. Folgen Sie der Dokumentation, um die verschiedenen Formate und Anwendungsfälle zu verstehen.
|
|
6
|
+
keywords:
|
|
7
|
+
- Internationalisierung
|
|
8
|
+
- Dokumentation
|
|
9
|
+
- Intlayer
|
|
10
|
+
- Nutzungsbedingungen
|
|
11
|
+
- Dienstleistung
|
|
12
|
+
- Nutzung
|
|
13
|
+
- Lizenz
|
|
14
|
+
- Haftung
|
|
15
|
+
- Datenschutz
|
|
16
|
+
- Beiträge
|
|
17
|
+
- Urhebernennung
|
|
18
|
+
- Änderung der Bedingungen
|
|
19
|
+
slugs:
|
|
20
|
+
- terms-of-service
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
# Intlayer Nutzungsbedingungen
|
|
24
|
+
|
|
25
|
+
## 1. Annahme der Bedingungen
|
|
26
|
+
|
|
27
|
+
Durch die Nutzung von Intlayer erklären Sie sich mit diesen Nutzungsbedingungen einverstanden. Wenn Sie diesen Bedingungen nicht zustimmen, verwenden Sie das Tool bitte nicht.
|
|
28
|
+
|
|
29
|
+
## 2. Lizenz
|
|
30
|
+
|
|
31
|
+
Intlayer wird unter der **Apache 2.0 Lizenz** vertrieben, die die Nutzung, Modifikation und Verbreitung des Codes sowohl für Open-Source- als auch für kommerzielle Projekte erlaubt. Benutzer dürfen den Quellcode ändern und Beiträge über Pull Requests gemäß den Richtlinien in unserem [Beitragsleitfaden](https://github.com/aymericzip/intlayer/blob/main/CONTRIBUTING.md) einreichen. Code-Diebstahl für kommerzielle Zwecke ist streng verboten.
|
|
32
|
+
|
|
33
|
+
## 3. Kommerzielle Nutzung
|
|
34
|
+
|
|
35
|
+
Sie dürfen Intlayer für kommerzielle Projekte verwenden. Die Wiederverwendung des Codes zur Erstellung direkter Konkurrenztools auf Basis von Intlayer ohne wesentliche Transformation oder erheblichen Mehrwert ist jedoch untersagt.
|
|
36
|
+
|
|
37
|
+
## 4. Haftung
|
|
38
|
+
|
|
39
|
+
Die Verantwortlichen von Intlayer bemühen sich, Fehler und Sicherheitsprobleme so schnell wie möglich zu beheben. Sie übernehmen jedoch keine Haftung für Schäden, die durch solche Probleme an der Infrastruktur der Nutzer entstehen. Wir empfehlen den Nutzern, Probleme über unser [Issue-Tracking-System](https://github.com/aymericzip/intlayer/issues) zu melden.
|
|
40
|
+
|
|
41
|
+
## 5. Datenschutz
|
|
42
|
+
|
|
43
|
+
Intlayer sammelt oder speichert keine personenbezogenen Daten der Nutzer.
|
|
44
|
+
|
|
45
|
+
## 6. Beiträge
|
|
46
|
+
|
|
47
|
+
Nutzer werden ermutigt, zu Intlayer beizutragen, indem sie den Richtlinien in unserem Beitragshandbuch folgen. Jeder eingereichte Code muss den festgelegten Qualitätsstandards entsprechen und wird vor der Integration von den Verantwortlichen überprüft.
|
|
48
|
+
|
|
49
|
+
## 7. Urhebernennung
|
|
50
|
+
|
|
51
|
+
Jedes Tool, das entwickelt wird, um den Intlayer-Code zu erweitern oder zu nutzen, muss Intlayer als Grundlage des Codes klar anerkennen. Diese Urhebernennung muss sowohl im Quellcode als auch in jeglicher Benutzer- oder Werbedokumentation sichtbar sein.
|
|
52
|
+
|
|
53
|
+
## 8. Änderung der Bedingungen
|
|
54
|
+
|
|
55
|
+
Diese Nutzungsbedingungen können jederzeit geändert werden. Die Nutzer werden über wesentliche Änderungen der Nutzungsbedingungen informiert und müssen den Änderungen zustimmen, um Intlayer weiterhin verwenden zu können.
|
|
@@ -0,0 +1,83 @@
|
|
|
1
|
+
---
|
|
2
|
+
createdAt: 2025-04-18
|
|
3
|
+
updatedAt: 2025-06-29
|
|
4
|
+
title: Intlayer Privacy Notice
|
|
5
|
+
description: Discover how Intlayer handles information collected through our website and CMS. Follow the documentation to understand the different formats and use cases.
|
|
6
|
+
keywords:
|
|
7
|
+
- Internationalization
|
|
8
|
+
- Documentation
|
|
9
|
+
- Intlayer
|
|
10
|
+
- Privacy
|
|
11
|
+
- Notice
|
|
12
|
+
- Cookies
|
|
13
|
+
- Tracking
|
|
14
|
+
- Analytics
|
|
15
|
+
- Google Analytics
|
|
16
|
+
- Meta (Facebook) Pixel
|
|
17
|
+
- Authentication
|
|
18
|
+
- User Data
|
|
19
|
+
slugs:
|
|
20
|
+
- privacy-notice
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
# Intlayer Privacy Notice
|
|
24
|
+
|
|
25
|
+
## Introduction
|
|
26
|
+
|
|
27
|
+
At Intlayer, we take privacy seriously. This notice explains how we handle information collected through our website and CMS.
|
|
28
|
+
|
|
29
|
+
## Contact
|
|
30
|
+
|
|
31
|
+
If you have any questions or concerns about privacy, please contact us at the following address: [contact@intlayer.org](mailto:contact@intlayer.org).
|
|
32
|
+
|
|
33
|
+
## Use of Cookies and Tracking Technologies
|
|
34
|
+
|
|
35
|
+
We use **Google Analytics** and the **Meta (Facebook) Pixel** to analyze the use of our website and improve our services. These tools generate statistics and other information about the website using cookies stored on users' devices.
|
|
36
|
+
|
|
37
|
+
For more information:
|
|
38
|
+
|
|
39
|
+
- [Google's privacy policy](https://policies.google.com/privacy)
|
|
40
|
+
- [Meta’s privacy policy](https://www.facebook.com/privacy/policy)
|
|
41
|
+
|
|
42
|
+
## Authentication and User Data
|
|
43
|
+
|
|
44
|
+
Access to the Intlayer CMS requires user authentication. We offer both email/password authentication and third-party sign-in via **Google** and **GitHub**.
|
|
45
|
+
|
|
46
|
+
During the authentication process, we collect:
|
|
47
|
+
|
|
48
|
+
- Email address
|
|
49
|
+
- Display name (or chosen name)
|
|
50
|
+
|
|
51
|
+
Users may also access the CMS via access tokens linked to their account. These tokens are tied to the same authentication data.
|
|
52
|
+
|
|
53
|
+
## Data Storage and Security
|
|
54
|
+
|
|
55
|
+
User authentication data is stored in a **MongoDB database** hosted on **cloud.mongodb.com**:
|
|
56
|
+
|
|
57
|
+
- **Region:** AWS / Oregon (us-west-2)
|
|
58
|
+
- **Type:** Replica Set (3 nodes)
|
|
59
|
+
- **Password Security:** All passwords are hashed using industry-standard practices.
|
|
60
|
+
|
|
61
|
+
We do not store any unnecessary personal data beyond what is required for authentication and secure CMS access.
|
|
62
|
+
|
|
63
|
+
## Data Sharing with Third Parties
|
|
64
|
+
|
|
65
|
+
We do **not** sell or share your personal data with third parties, except as required for analytics (Google Analytics, Facebook Pixel) or as part of the authentication process (Google or GitHub sign-in).
|
|
66
|
+
|
|
67
|
+
## Users' Rights
|
|
68
|
+
|
|
69
|
+
As a user, you have the right to:
|
|
70
|
+
|
|
71
|
+
- Access the personal data we hold about you
|
|
72
|
+
- Request correction or deletion of your data
|
|
73
|
+
- Revoke access or delete your account
|
|
74
|
+
|
|
75
|
+
For any request regarding your data, contact us at [contact@intlayer.org](mailto:contact@intlayer.org).
|
|
76
|
+
|
|
77
|
+
## Changes to This Notice
|
|
78
|
+
|
|
79
|
+
We may update this privacy notice from time to time. Users are advised to regularly check this page to stay informed of any changes.
|
|
80
|
+
|
|
81
|
+
---
|
|
82
|
+
|
|
83
|
+
Let me know if you'd like a more formal tone, add GDPR/CCPA mentions, or adapt it for a legal page on your site.
|
|
@@ -0,0 +1,55 @@
|
|
|
1
|
+
---
|
|
2
|
+
createdAt: 2025-04-18
|
|
3
|
+
updatedAt: 2025-06-29
|
|
4
|
+
title: Intlayer Terms of Service
|
|
5
|
+
description: Discover how Intlayer handles information collected through our website and CMS. Follow the documentation to understand the different formats and use cases.
|
|
6
|
+
keywords:
|
|
7
|
+
- Internationalization
|
|
8
|
+
- Documentation
|
|
9
|
+
- Intlayer
|
|
10
|
+
- Terms of Service
|
|
11
|
+
- Service
|
|
12
|
+
- Use
|
|
13
|
+
- License
|
|
14
|
+
- Liability
|
|
15
|
+
- Privacy
|
|
16
|
+
- Contributions
|
|
17
|
+
- Attribution
|
|
18
|
+
- Modification of Terms
|
|
19
|
+
slugs:
|
|
20
|
+
- terms-of-service
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
# Intlayer Terms of Use
|
|
24
|
+
|
|
25
|
+
## 1. Acceptance of Terms
|
|
26
|
+
|
|
27
|
+
By using Intlayer, you agree to be bound by these terms of use. If you do not accept these terms, please do not use the tool.
|
|
28
|
+
|
|
29
|
+
## 2. License
|
|
30
|
+
|
|
31
|
+
Intlayer is distributed under the **Apache 2.0 license** which allows the use, modification, and distribution of the code for both open-source and commercial projects. Users are allowed to modify the source code and submit contributions via pull requests in accordance with the guidelines established in our [contribution guide](https://github.com/aymericzip/intlayer/blob/main/CONTRIBUTING.md). Code theft for commercial use is strictly prohibited.
|
|
32
|
+
|
|
33
|
+
## 3. Commercial Use
|
|
34
|
+
|
|
35
|
+
You are permitted to use Intlayer for commercial projects. However, reusing the code to create direct competitor tools based on Intlayer without significant transformation or substantial value addition is prohibited.
|
|
36
|
+
|
|
37
|
+
## 4. Liability
|
|
38
|
+
|
|
39
|
+
The maintainers of Intlayer strive to correct bugs and security issues as soon as they are discovered. However, they disclaim any responsibility for damages resulting from such issues on user infrastructures. We encourage users to report issues via our [issue tracking system](https://github.com/aymericzip/intlayer/issues).
|
|
40
|
+
|
|
41
|
+
## 5. Privacy
|
|
42
|
+
|
|
43
|
+
Intlayer does not collect or store any personal data of users.
|
|
44
|
+
|
|
45
|
+
## 6. Contributions
|
|
46
|
+
|
|
47
|
+
Users are encouraged to contribute to Intlayer by following the guidelines provided in our contribution guide. Any submitted code must adhere to the established quality standards and will be reviewed by the maintainers before integration.
|
|
48
|
+
|
|
49
|
+
## 7. Attribution
|
|
50
|
+
|
|
51
|
+
Any tool developed to extend or utilize Intlayer's code must clearly credit Intlayer as the basis of the code. This attribution must be visible in the source code as well as in any user or promotional documentation.
|
|
52
|
+
|
|
53
|
+
## 8. Modification of Terms
|
|
54
|
+
|
|
55
|
+
These terms of use may be modified at any time. Users will be informed of any significant changes in the terms of use and must accept the changes to continue using Intlayer.
|
|
@@ -0,0 +1,83 @@
|
|
|
1
|
+
---
|
|
2
|
+
createdAt: 2025-04-18
|
|
3
|
+
updatedAt: 2025-06-29
|
|
4
|
+
title: Intlayer Privacy Notice
|
|
5
|
+
description: Discover how Intlayer handles information collected through our website and CMS. Follow the documentation to understand the different formats and use cases.
|
|
6
|
+
keywords:
|
|
7
|
+
- Internationalisation
|
|
8
|
+
- Documentation
|
|
9
|
+
- Intlayer
|
|
10
|
+
- Privacy
|
|
11
|
+
- Notice
|
|
12
|
+
- Cookies
|
|
13
|
+
- Tracking
|
|
14
|
+
- Analytics
|
|
15
|
+
- Google Analytics
|
|
16
|
+
- Meta (Facebook) Pixel
|
|
17
|
+
- Authentication
|
|
18
|
+
- User Data
|
|
19
|
+
slugs:
|
|
20
|
+
- privacy-notice
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
# Intlayer Privacy Notice
|
|
24
|
+
|
|
25
|
+
## Introduction
|
|
26
|
+
|
|
27
|
+
At Intlayer, we take privacy seriously. This notice explains how we handle information collected through our website and CMS.
|
|
28
|
+
|
|
29
|
+
## Contact
|
|
30
|
+
|
|
31
|
+
If you have any questions or concerns about privacy, please contact us at the following address: [contact@intlayer.org](mailto:contact@intlayer.org).
|
|
32
|
+
|
|
33
|
+
## Use of Cookies and Tracking Technologies
|
|
34
|
+
|
|
35
|
+
We use **Google Analytics** and the **Meta (Facebook) Pixel** to analyse the use of our website and improve our services. These tools generate statistics and other information about the website using cookies stored on users' devices.
|
|
36
|
+
|
|
37
|
+
For more information:
|
|
38
|
+
|
|
39
|
+
- [Google's privacy policy](https://policies.google.com/privacy)
|
|
40
|
+
- [Meta’s privacy policy](https://www.facebook.com/privacy/policy)
|
|
41
|
+
|
|
42
|
+
## Authentication and User Data
|
|
43
|
+
|
|
44
|
+
Access to the Intlayer CMS requires user authentication. We offer both email/password authentication and third-party sign-in via **Google** and **GitHub**.
|
|
45
|
+
|
|
46
|
+
During the authentication process, we collect:
|
|
47
|
+
|
|
48
|
+
- Email address
|
|
49
|
+
- Display name (or chosen name)
|
|
50
|
+
|
|
51
|
+
Users may also access the CMS via access tokens linked to their account. These tokens are tied to the same authentication data.
|
|
52
|
+
|
|
53
|
+
## Data Storage and Security
|
|
54
|
+
|
|
55
|
+
User authentication data is stored in a **MongoDB database** hosted on **cloud.mongodb.com**:
|
|
56
|
+
|
|
57
|
+
- **Region:** AWS / Oregon (us-west-2)
|
|
58
|
+
- **Type:** Replica Set (3 nodes)
|
|
59
|
+
- **Password Security:** All passwords are hashed using industry-standard practices.
|
|
60
|
+
|
|
61
|
+
We do not store any unnecessary personal data beyond what is required for authentication and secure CMS access.
|
|
62
|
+
|
|
63
|
+
## Data Sharing with Third Parties
|
|
64
|
+
|
|
65
|
+
We do **not** sell or share your personal data with third parties, except as required for analytics (Google Analytics, Facebook Pixel) or as part of the authentication process (Google or GitHub sign-in).
|
|
66
|
+
|
|
67
|
+
## Users' Rights
|
|
68
|
+
|
|
69
|
+
As a user, you have the right to:
|
|
70
|
+
|
|
71
|
+
- Access the personal data we hold about you
|
|
72
|
+
- Request correction or deletion of your data
|
|
73
|
+
- Revoke access or delete your account
|
|
74
|
+
|
|
75
|
+
For any request regarding your data, contact us at [contact@intlayer.org](mailto:contact@intlayer.org).
|
|
76
|
+
|
|
77
|
+
## Changes to This Notice
|
|
78
|
+
|
|
79
|
+
We may update this privacy notice from time to time. Users are advised to regularly check this page to stay informed of any changes.
|
|
80
|
+
|
|
81
|
+
---
|
|
82
|
+
|
|
83
|
+
Let me know if you'd like a more formal tone, add GDPR/CCPA mentions, or adapt it for a legal page on your site.
|