But I will then also have to get raw HTML to render, and for that, I’m using this shortcode prescription:
Using that generates valid and correct HTML with the <ol reversed> tag, but the webpage does not render the list with reversed numbering/ordering.
Does anyone know why that might be? It isn’t an issue with the browser; I check using both Firefox and Chromium, and both of them present the same issue.
But that does not work either. The browser does not seem to respect it. When I check the page using the built-in inspector, the list does begin with <ol reversed="reversed">, but what is rendered presents a list with regular ordering. I also tried <ol reversed="true">; it does the same thing.
Uh, just to make sure we’re on the same page, the reversed attribute does not reverse the order of the items. It reverses the numbering/lettering of the items.
And the HTML file that’s being produced is correct. So it can’t be anything wrong with HUGO (or the markdown or configuration). I’m at a loss as to where the problem lies.
Okay, so when I open the generated html file directly in a browser, it DOES respect reversed ordering. But when I use hugo server -D , and then open the served page, it DOES NOT reverse the ordering.
When I initialise the server, this is what it tells me:
$ hugo server -D
Start building sites …
hugo v0.84.3+extended linux/amd64 BuildDate=unknown
| EN
-------------------+-----
Pages | 10
Paginator pages | 0
Non-page files | 0
Static files | 2
Processed images | 0
Aliases | 0
Sitemaps | 1
Cleaned | 0
Built in 23 ms
Watching for changes in /home/user/Documents/Website/{archetypes,content,data,layouts,static,themes}
Watching for config changes in /home/user/Documents/Website/config.toml
Environment: "development"
Serving pages from memory
Running in Fast Render Mode. For full rebuilds on change: hugo server --disableFastRender
Web Server is available at //localhost:1313/ (bind address 127.0.0.1)
Press Ctrl+C to stop