Markdown file not building?

Ive run into this in a couple of places. lets say I have a file called /capabilities/training-courses/courses/scrumorg-applying-professional-scrum/index.md that’s of type:course. I want to add another markdown file in the same folder called /capabilities/training-courses/courses/scrumorg-applying-professional-scrum/technical-stuff.md that should also be rendered… but its not.

The change in file is detected, but its never rendered!

Source: NKDAgility.com/site/content/capabilities/training-courses/courses/scrumorg-applying-professional-scrum at 54-update-courses-data

Update: Is this a resources vs content issue? This file is being treated as a resource?

Update:OK, I think I answered my own question… changing to _index changes it from a page to a section, but now it no longer rendered with the type:course bits its rendering with layout/_default/list.html


OK, so is the correct answer:

  1. Change index to _index so that it rendered sub-pages
  2. Add kind: page to force page status

Its about Page Bundles which leads to your effect of rendering or not.

Please find another way.

The ability to set the page kind in front matter is intentionally omitted from the documentation.

Find another way

This is not particularly helpful as it offers no direction for “finding another way”.

I have a type that I want to have sub-pages, and be a page!

Yea… I want to use Branch bundles but then have them render as type: course. However, even with type = course, it uses the default rendering.

What is the recommended way to achieve this?

Define a special layout for these.

Template lookup order

1 Like

If you want a Markdown file to have logical descendants it must be named _index.md[1]. A content file named _index.md is of page kind section.

Use the layout field in front matter to specify an alternate template if needed.


  1. Change the extension to match content format. For example, with the AsciiDoc output format name the file _index.adoc. ↩︎

1 Like