Checking file tree integrity YET AGAIN with Universal

Using Themes
1

I’m made a file tree in content to match the menu in config.yml of my
site using Universal. Here is the tree:


content
│   albums.md
│   contact.md
│   demos.md
│   gallery.md
│   home.md
│   map.md
│
├───about
│       faqs.md
│       links.md
│       our-history.md
│       our-purpose.md
│       toc.md
│
├───blog
└───shop

Now, here’s the menu:

menu:
  main:
    - name: Home
      identifier: menu.home
      url: /
      weight: 1
    - name: 'Gallery'
      url: /
      weight: 1
      parent: menu.home
    - name: 'Theater'
      url: /
      weight: 2
      parent: menu.home
    - name: 'Albums'
      url: /
      weight: 3
      parent: menu.home
    - name: 'Demos'
      url: /
      weight: 4
      parent: menu.home
    - name: Blog
      identifier: menu.blog
      url: /blog/
      weight: 2
    - name: Shop
      identifier: menu.shop
      url: /shop/
      weight: 3
    - name: About
      identifier: menu.about
      url: /about/
      weight: 4
    - name: Our History
      identifier: section.a-history
      url: ''
      weight: 1
      parent: menu.about
    - name: Our Purpose
      identifier: section.a-purpose
      url: ''
      weight: 2
      parent: menu.about
    - name: ToC
      identifier: section.a-toc
      url: ''
      weight: 3
      parent: menu.about
    - name: FAQs
      identifier: section.a-faqs
      url: ''
      weight: 4
      parent: menu.about
    - name: Links
      identifier: section.a-links
      url: ''
      weight: 5
      parent: menu.about
    - name: Map
      identifier: menu.map
      url: /map/
      weight: 5
    - name: Home
      identifier: section.ap-home
      url: ''
      weight: 1
      parent: menu.map
    - name: Gallery
      identifier: section.ap-gallery
      url: ''
      weight: 2
      parent: menu.map
    - name: Theater
      identifier: section.ap-theater
      url: ''
      weight: 3
      parent: menu.map
    - name: Albums
      identifier: section.ap-albums
      url: ''
      weight: 4
      parent: menu.map
    - name: Demos
      identifier: section.ap-demos
      url: ''
      weight: 5
      parent: menu.map
    - name: Blog
      identifier: section.ap-blog
      url: ''
      weight: 1
      parent: menu.map
    - name: Shop
      identifier: section.ap-shop
      url: ''
      weight: 1
      parent: menu.map
    - name: About
      identifier: section.ap-about
      url: ''
      weight: 1
      parent: menu.map
    - name: Our History
      identifier: section.ap-history
      url: ''
      weight: 2
      parent: menu.map
    - name: Our Purpose
      identifier: section.ap-purpose
      url: ''
      weight: 3
      parent: menu.map
    - name: ToC
      identifier: section.ap-toc
      url: ''
      weight: 4
      parent: menu.map
    - name: FAQs
      identifier: section.ap-faqs
      url: ''
      weight: 5
      parent: menu.map
    - name: Links
      identifier: section.ap-links
      url: ''
      weight: 6
      parent: menu.map
    - name: Contact
      identifier: contact
      url: /contact/
      weight: 6

Am I doing it right?

2

Some help, here, this is crucial to knowing the theme!

3

We have a file tree and a menu definition without pointing to nowhere, same locations… and a question if this is right…

It looks like this is a very special thing to the Universal theme (which has multiple variants of pages. So whatever happens there, if your setup is right is some magic hidden in layouts and more config…

There’s a menu section in their documentation and they have an issue tracker on their github. So for the general “is this correct” you might get a more accurate and faster answer there.

1 Like
4

Thanks, I will try to get an answer there.

5

Hear me out…

I’ve been doing a lot of thinking, and it has possibly came to my
attention, that the entries in the example site in Universal with
the ‘/’ and/or ‘’ as the URL tend to be empty.

Further proof should be the example site itself, as the creator
probably had no time fleshing out that menu, and was only
just showing an example, as many of the links were
unclickable but the blog, contact and FAQ pages.

Judging by this, I can assume that my config YAML needs
more editing, as I probably need to confirm this…

Please respond, if you think this was interesting.

6

Okay, now this is the tree for the content:

\CONTENT
│   contact.md
│   map.md
│
├───about
│       faqs.md
│       links.md
│       our-history.md
│       our-purpose.md
│       toc.md
│
├───albums
├───blog
│   └───2025
├───demos
├───gallery
└───shop

I hit server -w and found my config file to be right on the money, only that this came up before the compile:

WARN  calling IsSet with unsupported type "invalid" (<nil>) will always return false.

and the about and map dropdowns wouldn’t show right nor the home page’s when on other pages, except the contact page!!!

What went wrong?

7

I temporarily fixed it for now, and that warning still comes up. The map page became a link hub page, the about folder became a page full of about pages and both lost their dropdown features, as the home dropdown only works around working pages.

Now, to work on that warning!

8

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.