Yahoo Search Búsqueda en la Web

Resultado de búsqueda

  1. gohugo.io › content-management › multilingualMultilingual mode | Hugo

    9 de may. de 2024 · Hugo's multilingual framework supports single-host and multihost configurations. Localize your project for each language and region, including translations, images, dates, currencies, numbers, percentages, and collation sequence.

  2. 16 de mar. de 2024 · hugo.IsMultihost. Reports whether each configured language has a unique base URL. Syntax. hugo.IsMultihost. Returns. bool. New in v0.124.0. Site configuration: hugo.

  3. gohugo.io › about › featuresFeatures | Hugo

    17 de may. de 2024 · Hugo’s multilingual framework supports single-host and multihost configurations. Output formats Render each page of your site to one or more output formats, with granular control by page kind, section, and path.

  4. 23 de mar. de 2020 · Configure Multilingual Multihost. From Hugo 0.31 we support multiple languages in a multihost configuration. See this issue for details. This means that you can now configure a baseURL per language: If a baseURL is set on the language level, then all languages must have one and they must all be different. Example: config.

  5. 28 de may. de 2020 · How to use Hugo Modules. I’m looking to define multiple baseUrl’s (multihost), however I am working within a single language (Mono-Language). Is there a way to generate multihost websites without having to hack the language tags in config.toml? …

  6. 22 de ene. de 2020 · This multihost support is for i18n where multi-lingual versions of a website can be hosted on different domains. Can this be extended or evolved into a proper multisite feature allowing users to creating/managing websites where each website can have multiple products’ documentation (one repository per one product documentation) and ...

  7. 30 de oct. de 2017 · The current multilingual support in Hugo is restricted to 1 baseURL, i.e. the languages are put into subfolders named after the language code (the default language may be kept on the top level), i.e. https://example.com/en etc. This works great and is possibly the most common use case.