A site used for a series of sites

support
1

Can a site be used as a home page linked to other sites?

I publish a book series and I want to have a website for each book entry while
that happens, since each book is immersive.

If so, where can I begin?

2

just from the top of my mind, I would have a index.html file which iterate through a array from the hugo.toml file which holds all the information like:

  • name
  • author
  • url

…or whatever else you want on the page.

3

Supposing that I already work with .yml, I’m guessing that I have
to edit my config like this:


baseurl: "https://website.here/"
languageCode: en-us
title: My Book Site
theme: MyTheme

menu:
  main:
    - identifier: book1
      name: Book 1
      url: /booksiteurlhere/ #e.g., https://hiddenworldbook.net
      weight: 10

...

and then continue the editing from there. Am I right?

4

i’m not sure how you want the entire site to look but have a look at a example here: glim-midnight/examplesite/hugo.toml at main · mansoorbarri/glim-midnight · GitHub

its just a basic website which lists all the links mentioned in the config.toml

5

It’s doubtful anyone can provide more help without getting into details. It’s less a matter of yaml configuration, and more about how you structure the content to serve the intention.

How would you describe the desired outcome and what exactly does each “site” contain? Are you aiming to use some specific theme you like? Are you developing one or your own? Are they going to be in a single languages, or many? How do you define immersion specifically: is it a matter of embedding multiple media formats; is the graphic design and theme matching the story; is it going to be a hypertext format with cross-annotations and dynamic indexes?

Assuming that a “series of sites” doesn’t mean that each “website” lives on its own domain, then what you’re looking for in its simplest form is a different section (in practical terms folders of files) for each book. Then again assuming each book’s site contains the content instead of marketing material only, you likely want to separate chapters into separate markdown files (“posts” that any theme displays) or as branch bundles (more files that the theme needs to display).

There’s also several Markdown to PDF & website toolchains, such as Getty’s Quire (which at least some years ago did use Hugo in the backend); BookPub; LeanPub; GitBook (pivoted to technical documentation books several years ago) and more. Of course people have been developing bookish and book themes for Hugo, but each theme has its traits and quirks.

Maybe you’d want to get started with the content first, see the previous toolchains for tips on structure and format, then you can transform this content around into a website at a later point. Unless you’re already there.

6

I’m curious. I looked at mansoor barri’s toml, and it seems
convertible. How do I link a Hugo site’s very own page in
Markdown, without ever having to grab it from a server
seen on your browser?

Should the syntax’s target be relative to the local website
or relative to the server?

7

If it’s multiple files, then sharing from a Git repository is easier.
Not sure what you mean by “syntax’s target”.

8

The target url that’s linked.

Update: I need help, here, the links won’t take me to the pages,
though they’re accessible via post!

9

sounds like you managed it close to working.

your last update does not allow to find a reason. guess all we can say is compare your generated links with the accessible ones from posts.

please have a look at Requesting Help and provide neccessary source and layouts. and point out where and what is not working.

as usual sharing a replayable repo will be the fastest way to get a solution

10

All I did was type Example:[link to content](content/guide/content.md) for all of my
guides’ links, and uploaded the changes, and the next thing, it wouldn’t lead
anywhere!

I tried to edit the link by using its link on the deploy server, but it added that link to the
destination path in the browser and took me to an error page.

The tree:

drive:\my site
├───archetypes
├───assets
├───content
│   ├───guide
│   └───posts
│       └───2025
│           └───jan
├───data
├───i18n
├───layouts
├───static
└───themes
    └───PaperMod
        ├───.github
        │   ├───ISSUE_TEMPLATE
        │   └───workflows
        ├───assets
        │   ├───css
        │   │   ├───common
        │   │   ├───core
        │   │   ├───extended
        │   │   └───includes
        │   └───js
        ├───i18n
        ├───images
        └───layouts
            ├───partials
            │   └───templates
            │       └───_funcs
            ├───shortcodes
            └───_default
                └───_markup

The link: GitHub - UrieW/uwsite

What’s affected is the files that have ‘guide’ in it.

11

Assuming no further configuration for urls exists in hugo.yaml then your links ought to be like :[link to content](/guide/) or :[link to content](/posts/2025/jan) and content.md should be renamed to index.md. Again, further help is impossible without access to the exact code and file system. At this point you should study the documentation better to understand how it Hugo works.

1 Like
12

YES, that’s it

absolutely true - adding Markdown, and the Theme docs for PaperMod

after adding the PaperMod theme using git clone the site was generated.

your links in /content/guides won’t work cause they match your windows filesystem from the site root inside content folder. They should match the rendered paths in your public folder

  • path separator is ‘/’
  • no content folder
  • just link to the folder (or index.html inside the folder)

as

# Books  - WRONG

[Book Formatting Guide](content\guide\book-fd.md)

[Book Cover Making Guide](content\guide\bookcover-make.md)

# Books - WORKING

[Book Formatting Guide](/guide/book-fd)

[Book Formatting Guide](/guide/book-fd/index.html)

[Book Cover Making Guide](/guide/bookcover-make)

all said:

You have a markdown page linking to local pages. By the discussion before I would have expected some generated list based on data…