Skip to content
Grav 2.0 is officially stable. Read the announcement →

Muut Archive Legend

@Muut · Joined 9 years ago · 18337 posts · 3878 topics · 137 reputation

Badges

✏️ First Post 💬 Conversation Starter ❤️ Well Liked

Recent posts

  • How to add an extra content field · 11 years ago

    That's the default location where to "lookup" the default file, so you can omit it.

  • How to add an extra content field · 11 years ago

    Thanks. Unlike the other blueprint files, this one does not seem to have the context: element. Does that matter?

  • How to add an extra content field · 11 years ago

    You need to add a new page template file and define new fields for the content tab, for example: default2.yaml title: Default2 '@extends': default form: fields: tabs: fields: con

  • How to add an extra content field · 11 years ago

    I would like some of my posts to contain an extra field, called subhead. Ideally, this would be presented through Admin in Add Page. I can see where the field ought to go in /system/blueprints/pages/d

  • Site + RTFM documentation in one? · 10 years ago

    Good :D, waiting.

  • Site + RTFM documentation in one? · 10 years ago

    I'm attempting to figure this out as well. Will post if I can manage anything.

  • Site + RTFM documentation in one? · 11 years ago

    Tried to introduce another for loop, which will let me get rid of the top level menu, but completely messes up the menu items, showing only the top level elements for every chapter and navigation is b

  • Site + RTFM documentation in one? · 11 years ago

    Still didn't got it, but got closer to it: in sidebar.html.twig I added a [2:]: {% for p in page.children[2:] %} This makes only the documentation folder's children listed on the sidebar as wanted but

  • Site + RTFM documentation in one? · 11 years ago

    tried to solve it by collections: title: Getting started taxonomy: category: docs theme: learn2 content: items: '@taxonomy.category': docs Still shows all the pages in sidebar navigation.

  • Site + RTFM documentation in one? · 11 years ago

    This worked out pretty well, only that it ends up also with the default theme's pages in the documentation's navigation sidebar as chapters of the documentation. Do you know of a way to use the docume