That seems to fix it.
On a separate issue, it would be good I think to have an indication of some sort when a heading has been collapsed. Also a config setting to disable collapsing, if that isn't there already.
Super. The fix is already in the dev build.
Ah, interesting. I actually got rid of them because I don't like them when looking at long prose. Should be an easy fix though. I will probably put in a CSS variable to allow turning on and off very easily via the page template.
OK, sensible option. Let me think about the best way. I'm trying to avoid adding options to the node so as to keep it as simple as possible. But that would be an option. I'll see if I can do it through CSS though.
Thanks for the testing and the suggestions.
New version live.
Sorry, should have said. Your request for the collapse markers is in but not yet the option for turning off the collapsible sections, that one has to wait for the next release I'm afraid as it needs more work.
No rush, I am still just experimenting with it. Great work though, I will certainly be moving some stuff over to it.
Thanks.
I've now set up my first Internet accessible route via Cloudflare. Giving me access to my new Info content site. Site generated from Markdown using Markweb, Node-RED host, cloudflare secure routes with login and other security applied.
I have noticed that initial load can be a bit slow. I also have a large page (has code examples and an example flow) which was a little slow to initially load. I'll keep an eye on that but would also welcome any feedback on things that may seem a little slow.
Noticed a couple of other small improvements. For example around having a visible site name and icon and allowing a bit more flexibility around the browser tab name.
I expect a lot more usability things will crop up in real-world use so please don't be shy about letting me know. 
Is this the Much Ado about IT site?
Ah, no. That is my old blog that hasn't been updated in a long while. It is running on Netlify and uses Hugo. I have a newer blog at www.totallyinformation.net which is hosted on a Cloudflare public site using Astro. They are both fully public web sites with the markdown source hosted on GitLab and GitHub respectively.
This is a simple information site that I'm considering using to replace my current use of Obsidian. It might contain information that I would prefer not to be public such as internal configuration information. Nothing super-secret you understand but even so.
I am also considering whether to replace my public site with a Markweb site. But that would be set up on a separate Node-RED instance I think. But before going down that route, I need to be sure that the performance and reliability of Markweb is good enough. Reliability should be good as it is relatively simple code. But I suspect that performance will need tweaking somewhat as people get towards larger sites - more caching of things also likely needed in the longer term.
This is why I'm keen to get feedback from people regarding performance in the real world. My local tests seem reasonable enough and good enough to match something like Obsidian anyway.
Right now, I'm only seeing a couple of people using Markweb (via the telemetry so it make take a month to catch up with real usage) vs nearly a 1,300 users of uibuilder - that, of course, is only from people who have upgraded to v7.7.x
That is what I thought. You must be referring to the Markweb site for the Manuals? Or have I lost the plot??
You've lost the plot!
I have used OneNote since its early days for recording information and research I want to retain for myself. In the last few years I started to switch to Obsidian for more technical notes such as these:
Since retirement, I've been keeping a mini journal in there as well.
One of the inspirations for Markweb was Obsidian and similar Markdown-based apps. So it makes sense to see whether I can use Markweb to replace Obsidian. These are mostly private research notes but it is nice to be able to access them over the internet occasionally. Of course, I don't have a Markdown editing feature - yet. But it is on my radar.
There are a number of websites that I might transfer to Markweb sites. You mention manuals - I assume you mean both Markweb and the wider UIBUILDER documentation? Those are certainly possibilities, a public-facing version of the Demo site would be a first step I think.
Moving the general UIBUILDER docs site is a little trickier since the public-facing aspect of that uses GitHub pages and Docksify (another inspiration for Markweb). Docksify does the Markdown conversion in the browser instead of the server and that's how the docs work both on the Internet and locally in your Node-RED instance.
I will be looking to see if I can reproduce some of these features in the future for Markweb. For example, I think that a markweb-save node might be interesting. It would take a Markweb site and dynamically convert it to pure HTML. That way, you could use any free static site service (GitHub pages, Netlify, Cloudflare pages, etc) to publish it.
So many possibilities!
It's been a hard few weeks, but I get it and as a Joplin user, I might have all my preferred Recipes (Meals) in .md format.
Once @Colin has debugged this for me... (Just joking Colin! I might have time to have a go this afternoon!!) So many Projects, so little time!!
My growing collection still in OneNote rather than Obsidian as that is easier to access on mobile and tablet devices. But Markweb may change that dynamic too.
I did try that, hoping for a better sync experience. But I didn't really get on with it.
Indeed! Speaking of which, time to cut the grass so I can fill the green bin before it gets collected today.
I am syncing across Linux, iPad, Android and Lenovo Tablet with no problems. I do have a Nextcloud instance though, which also serves Calendar and Contacts using DavX5 on Android devices, Thunderbird on Linux. Also I use the Nextcloud server for sharing Files, Documents etc. to others.
I will see how Markweb goes and decide what to do with that when I have it working.
I use Obsidian on PC and Android, using syncthing to sync them. It works very well.
Back on what the markweb pages look like, level 1 headings still don't look good in browser light mode. They show as very dark blue, virtually unreadable on the dark background. I think you haven't used level 1 headings in the demo which is probably why you have not seen it.
I have just updated my ubuntu to 26.04 and the screenshot app is crashing for some reason, so I can't show an example.
No, the styling only works in dark at present, I think I did say that. More work would be needed to get a light-mode style that is comfortable to use.
I think (maybe?) I do say somewhere that you should not use <h1> in your Markdown. This is because every page already has one of those and WCAG accessibility standards say that you should only ever have 1 level 1 heading and it should be the title of the page and near the top.
In fact, you are supposed to get a visible warning if you try to put another h1 on the page, that is baked into the core uibuilder brand styling. But I think it may have somehow been undone in the Markweb styling.
Anyway, bottom line is that the default page template already provides an h1 as the page title and you should avoid adding any more.
By the way, if you have suggestions for a light mode set of styles, I'd be glad to incorporate them. The main uibuilder brand styles have both light and dark modes defined, it is just the Markweb ones that need some work.
I thought that was what you did to get the demo site working in light mode. I misunderstood.
Now you mention it I think I did see that somewhere.
I had not twigged that you were mapping markdown H1 to <h1>. That is obviously the sensible way to do it. I won't use H1 in the markdown.
I don't know about styling, I don't know much about CSS at all really.
Oh well. If you can live with a dark approach for now, it should be good. To be honest, I've been on dark mode for a few years now. So unless people pressure me to do something, a light mode is some way off I'm afraid. But, I am easily persuaded.
I run the system in light mode, but I run some apps in dark (Obsidian for example). Don't exactly know why, it has just evolved like that.
For Markweb, for me, all that matters is that it is easily readable with the browser in either mode.
Looking at the demo again, with the browser in light mode, html links are too dark blue, so very difficult to read.
On a separate issue, I am creating and editing my pages with Obsidian, which is working well. Have you considered supporting the obsidian link format for inter-page links using [[page]]?
Adding class="dark" to the html` tag in the page template should force the page into dark mode. I did add that as the default but if you had already used a config folder for your Markweb instance, you may need to either delete the config html file if you've not made any changes (it is re-created from the updated template after restarting Node-RED). Or, if you have made other customisations, just add it manually.
The Demo site should appear in dark mode regardless. If not, we need to have a look at what is wrong.
This browser profile is set to light mode and the demo site is showing as dark style. What is different for you?
I absolutely have thought about it. Personally I don't use them because I use a number of different Markdown tools and not all of them support that style of link, I always use [My Link](...).
I will add this back in as a request though to the the backlog, thanks for raising.
BTW, I will extend Markweb to support more than just the current index.md files for similar reasons. There are other tools that use variations on that naming such as Hugo and Astro and I'd like to be able to enable easier migrations.
Unfortunately, Obsidian doesn't support native folder pages, you can create pages titled index but it doesn't use them as folder pages like static site generators do. Something to bear in mind since any folder without an index file won't show up in your Markweb site. That is to allow for asset folders & to prevent 404 errors when clicking on a folder name in the navigation.
I have deleted the node_modules folder and the uibuilder folder and run npm install. The flow has only the markweb node showing the demo (and a second one that is disabled). Then restarted node-red. The start of the demo looks just as you have shown it, it is just links that are too dark.
When I inspect the html I do see class="dark" at the top. The link itself shows
a: -webkit-any-link {
color: -webkit-link;
cursor: pointer;
text-decoration: underline;
}
This is in Edge and Brave. Does that mean that this is the default colour that the browser is using for links for the dark class?
