Most of them are a chain. I try to indicate a link/order by putting "part ####" in the title.
Oh I see.. I'd interpreted it as an explicit previous/next link.
I've written part 1/2/3 etc posts too, and (like you) try to have an introduction or short explanation so that some of it may make sense if someone has not read an earlier part, or not read it in sequence.
That's a good solution : ) Your example is a variation of the third option I think.. I couldn't see links in a chain,
For step-by-step guides and tutotials too, the combined system is popular, i.e. having a complete list somewhere (to the left side, or in a table as you do) and also have the suggested next and previous, such as buttons.. with some attempt to make each page standalone or readable for those who may have skipped some of the posts.. I notice you always have an intro-type section and photo or diagram.
For blogs the 'next' and 'previous' becomes harder since it's not a feature of the platform, so it has to be done manually.. so personally I feel it sometimes may not be worthwhile.. it's an accoutrement perhaps and not essential mostly. Others may feel differently. For some very complex tutorials where people may get lost it becomes more essential I feel.
I'd say the second option, the chain, can almost never work.. after having trained engineers on topics at work (although I appreciate training is a different thing), it soon becomes very clear engineers don't like such a method.. they like to go off and explore their own things, and will not stick to the training/tutorial step-by-step because at some point they want to skip and try their own things or explore elsewhere. Basically they don't like that rigid format! : )
I try to solve that by putting the table with links at the end of each post in a series (example).
When I add a post, I update all posts to have the new one in the table.
I update one post, then switch to HTML mode and copy that table. Then update the other posts with that copy.
I've just completed my first road test write-up and used the single blog format. From a writing standpoint... I struggled. Maybe it will get better, but I found it tough to stay focused. I also realized that I need to add the pictures as I go. I need them to keep the thought process flowing.
Also don't like blogs or reviews that are 5000+ words, get to the point and say what you need to say. If you need to elaborate extensively on a point, make a side blog.
I have tried publishing using each of these methods and they all have their own merits, but when reading a blog I far prefer reading completely self contained blogs (all in one).
If there is a section of no interest, like an unboxing, it is trivial to scroll down to the meat, rather than clicking on a linked page only to find out it is of little interest. The bottom line is it is quicker to scroll back and forth in a single blog than to click back and forth through multiple pages. If a blog is going to be gigantic, authors should take into consideration that most viewers may not have the attention span to read the whole thing and keep blogs to a readable size.
When a blog is so big or spread out in time that it is not published all at the same time I think it is still preferable to add on to the original blog rather than create new disjointed blogs. I hate online articles that have a paragraph on a page surrounded with endless advertising and you have to click to another page to see another small paragraph, especially when there are other click buttons that look like a continuation button, but go somewhere else entirely. The best solution, of course, is to hold off on publishing until the blog is complete, but sometimes a deadline for publishing is involved.
Inbox for a-reason is good, inbox blog to cover the space is what u dislike.
Some well designed inbox demo can fully reveal the capability of product over one glance. New stm32mp1-disc comes with one neat opnStLinux demo and short video. That worth a brief intro.
I like single page content. Most content that I read is in that format: books, papers, references, etc. It supports "find" and makes searching easier.
Now on content that I dont like, Im not a big fan of unpacking, and zillions of unnecesary images, such as screen captures of every minor detail during software installation.
Top Comments