I am now working under a part-time contract with Turing Machines. My two current assignments are: - help support the community here and on the Turing Machines support email alias, ask@turingpi.com. - update and create documentation on the doc.turingpi.com web site. As I get up to speed, I want to gather input from the community on the documentation structure and content. My opinion is we need separate documentation sections for the v2.3/v2.4 and v2.5 boards. There will be some information overlap/redundancy. Having separate documentation sections will provide a single point of information without having to qualify what points relate to each board version. That can be confusing, particularly for non-English speakers. Feel free to comment here. I'll also take input through Turing Machines' support email alias. I will collect input and pin a post containing periodic summaries here.

I think the first port of call should be to review the documentation and identify what is out of date, the documentation is decent enough but some of it is starting to become outdated, this might be caused by differing versions of the board but I think it is also due to the BMC being updated and the documentation being missed. I think it would be good to also have some common diagnostics people can do for example when having difficulty flashing nodes.

Thank you for the input. Maybe single-subject troubleshooting and HOWTOs would be useful. Discord isn't particularly useful at finding things. Maybe if it had an AI agent that used the database of posts for training.

Yes totally agree Discord is good for chat but things can disappear quickly. and of course even harder if you are not quite sure what you are looking for.

If there are really that many differences between v2.2, .3, .4 & .5 boards separate documentation might be the only way to go. The tpi cli would probably be a page that wouldn't have a bunch of different versions. Most folks would probably keep tpi up to date and thus older docs are less useful.