How to create non-blog style index.html pages

support
1

Hello,

I want to use Hugo to create a non-blog site.
If I understand correctly, by default the index pages generated are list-based, for blog system.
I red some posts and documentations, and I thinked that I could change this behaviour, but it didn’t work.
Here is my site’s hierarchy
content

Introduction

index.md
intro1.md
intro2.md

Section_1

_index.md
page0.md
page2.md

hyde is the theme I used at the base
I then changed drastically the file in themes>hyde>layout>_default>list.html
it is now

{{"<!-- Debut _default/list.html -->" | safeHTML }}
<html>
<body>
    sampletext
{{ .Content }}
</body>
</html>
{{"<!-- Fin _default/list.html -->" | safeHTML }}

but when I publish the site, I see the “sampletext” text, but not the content of either index.md nor _index.md

I certainly have missed something! Do you have an idea?

2

You have to provide a full site. No one is psychic enough to guess what your problems based on those snippets.

3

Thanks.
So, I uploaded the files here

Frederic

4

I think that it is possible to obtain the result I want.
If someone could post a simple working example, it could point me to the right direction.
TIA

5

First, I put this in a temp GitHub repo because it took too long to figure out how to get this from Google Drive:

https://github.com/rdwatters/antilog-testing

@bep Interestingly, when I run this locally, the {{.Content}} in the theme’s _default/list.html doesn’t actually render, although everything else I add to the template does render (e.g., {{range .Data.Pages}}). This is after I’ve changed content/Introduction/index.md to content/Introduction/_index.md

@Frederic has a section called content/Section_1. If I change that section to content/another-section instead, the content at content/another-section/_index.md does render to the page.

I am getting nothing in the console and using dev branch on Mac.

6

That said, @Frederic, I’m not sure about your level of development experience, but one consideration is to not modify theme files directly, since this will keep you from keeping compatibility with future versions of the theme.

For example, instead of adding all these hacks to themes/hyde/layouts/_default/list.html, anything you write to layouts/_default/list.html will end up overriding whatever is being provided by the Hyde theme.

Also, definitely look into learning git and GitHub :smile: Google Drive is going to make this harder on you in the long run.

7

Hi @rdwatters, Thanks for all!

I tried to reproduce your changes to understand the problem, and didn’t succeed until I wrote the folder exactly as you did!
In fact, the capital seems to be the culprit. If I name the folders with a leading capital (Introduction), it doesn’t work. If I write (introduction), it works.

I suppose I’m the only one to have this problem? BTW I’m using a mac too.

8

I just used the hyde theme as a base to implement for my web site. That’s why I make changes directly in the theme files.
I’ll end up with all of the theme’s file modified.

I didn’t know how to provide the site for testing, so I tried with Google Docs.
It does annoy me to use GitHub and Git, because I work with BitBucket and Mercurial ! :disappointed:

Thanks again

9

Ah, I was too specific. I should have just said “please use git and a hosted git solution.” But it sounds like you’re already doing that. It’s usually just easier to share and debug in the forums from the command line. I assumed too much:)