@ramez, Although I'm not a fan of one-page website, I did some playing...
Note: The quote you mention is from the overview of page types. That's only part of the story. There is more information to be found at Modular Pages.
Also of interest is the documentation on Page Collections.
I played with a combination of both above technologies.
The following is based on the One-Page Site skeleton. That skeleton comes with the following pages:
01.home/
01._hero/
hero.md
02._highlights/
features.md
03._callout/
text.md
04._features/
features.md
modular.md
A modular page is made up by a collection of other pages. In this case the page 01.home/modular.md uses a collection based on its child modular pages.
content:
items: @self.modular
However, a collection can also be based on taxonomies. E.g.:
content:
items:
'@taxonomy.tag': features
Reusing the 'features' child modular from 'home' can be achieved as follows:
- Add a taxonomy tag to the modular page
/01.home/04._features/features.md:
- Create a new modular page below
/pages/:
- Add the following content to
02.features/modular.md:
content:
items:
'@taxonomy.tag': features
- Point your browser to localhost/my-site/features...
You have now created a new modular page, that uses a collection of pages with taxonomy tag 'features`.
Note: Although this gives you an idea to solve your question about reusing content, I'm not sure if this is the way to go...
Here is some more info on SEO and one-pages websites: Optimizing a single page: One page website SEO
Hope this helps...