Das ist die deutsche Beispielseite.
Hugo-Scroll theme alternates colors of sections that are placed on single page.
The landing screen is meant to be visually striking.
Single-page approach is oriented towards small to medium content length, that won’t overwhelm the user. You can also delegate lengthier, less important or more sizeable content to dedicated pages.
The belly rules the mind. — spanish proverb
By the way this welcome section won’t show in the cover menu.
Feature notice: This section displays options to customize title:
title = “The Services I Offer”),header_menu_title = “Services”),navigation_menu_title = “My Services”).That is the important part, right? You want to know what I can do for you. This is why I put this right up there into the header menu of the website.
This is not an easy task. You will likely have to pay money for this.
I can raise your table culture!
Want to learn more about my services? See dedicated page with more details.
This demonstates localized content placed in dedicated language folder, content/de. This way you won’t have to use localization suffix with the .md file. Both localisation approaches (separate folder, suffixes in the same folder) can be used and even mixed.
See i18n configuration in [languages] section of config.toml.
Localised content can be put in dedicated folder content/de/. Images should be naturally found from there:
Images in assets folder can be localised, conventionally by adding .de suffix. However, assets may be tricky, see next section for details
Note the filename of this section is a bit artificial to avoid conflict with other examples in en folder. If named the same, this one wouldn’t render. However normally you wouldn’t have one page localized two ways.
This demonstates localized variants about-me.de.md placed along the primary language content, such as content/en. Both localisation approaches (separate folder, suffixes in the same folder) can be used and mixed.
When localised page variants are placed along, images of other languages can’t be used directly. You would need to use .de-suffixed copy of the image: 
Consider using assets instead.
Images from local content location can’t be pipeline-processed.
Alternatively, images can be injected from static/images:
Note the leading / is required in this case.
Images from static location can’t be pipeline-processed and are always copied when publishing the site, even if not linked from any page.
Latest Hugo version supports injection from assets via natural Markdown notation, which empowers this approach for injecting images since pipeline processing (resizing etc) can be used. However, It only worked for me with the local test deployment, there were issues while deploying previews Netlify. Possible workaround would be to use custom shortcode to “touch” the image via Resources.GetMatch. I hope this gets fixed someday.
Historically, Linking image from assets folder worked only via Hugo-specific shortcode, there was a discussion with suggestions.
Note that using images form assets folder is the only way to apply pipeline processing, such as resizing, when building the site. Fore more details, read about asset vs static difference
Assets are only published if linked from a content page.
Let us get in touch!
The file legal-brief.md creates an internal link on the cover page without the leading icon.
If the parameter detailed_page_homepage_content is set to false neither this section nor the navigation menu entry will be shown (but the link on the cover page will be).
If detailed_page_homepage_content is set to true or is missing at all, the link, navigation menu and the content will be rendered. In that case this section might contain less or just summarized information compared to the single page referenced by the parameter detailed_page_path.
Want to see more about the details? See dedicated page with more details or hit the button ‘Legal’ on the cover page.