PlebWare Site Progress — Another Day at the Conference Table.
2026-09-22
PlebWare Keeps Moving Forward.
This is a site-progress report from the PlebWare conference table on Tuesday, 22 September 2026.
The work continues, and I am genuinely stoked — or, in good South African English, chuffed — with how far the PlebWare website and the wider PlebWare project have come.
The important point is that this is not just about adding pages to a website. We are gradually building a working environment around the ordinary computer user: the person we call the Plebware.
142 Days of Building PlebWare.
The development count has now reached 142 days since 3 May 2026.
That number is useful because it gives us a sense of the sustained effort behind the project. The site has gone through repeated testing, correction, restructuring, writing, publishing, and refinement rather than being assembled in one big push.
The work is still ongoing. We are not calling it finished simply because the website is large or because many pieces are working.
The Website Is Working Well.
One of the things that has me particularly pleased is that PlebWare.github.io is now behaving as a practical publishing environment.
The site structure is becoming clearer, the different sections are finding their proper homes, and the publishing workflow is much easier to manage.
We have also been deliberately removing things that looked clever but did not work reliably across platforms.
A good example is the read-aloud highlighting system. The highlighting was removed because it introduced cross-platform compatibility problems, while PlebVox voice output itself remains useful and stays in the system.
That is an important PlebWare principle: if a feature does not work reliably for ordinary people on different devices, it needs to be reconsidered.
Voice Dictation Has Changed the Workflow.
Another major improvement has been the use of voice dictation to create reports and articles in pieces.
I can speak a section, check what the voice-to-text system produced, correct it, and then continue with the next section.
The surprising part is that the slowest stage is often not the publishing.
It is checking the voice-to-text output.
Once the text has been checked and approved, turning the finished material into the correct Markdown and publishing it is comparatively straightforward.
That makes the workflow much more practical, especially when a report is too large to create comfortably in one sitting.
Humans Still Do the Checking.
The AI systems involved in PlebWare are useful collaborators, but the human remains responsible for deciding what is actually true, what should be published, and what needs correction.
That distinction matters.
AI can help structure information, improve wording, inspect code, and speed up repetitive work. It can also get things wrong.
So the PlebWare workflow remains deliberately human-directed: speak, inspect, correct, approve, publish.
The Conference Table Keeps Growing.
The PlebWare conference table now represents a growing collection of tools, people, ideas, and AI collaborators.
The website is the public face.
GitHub is the workshop.
Markdown is the publishing language.
PlebWare is the shared build.
And the human being at the centre remains the person who decides what gets built.
There is still plenty to do, but the direction is becoming clearer every day.
One More Day, One More Piece.
That is really what this report comes down to.
Another day of testing.
Another correction.
Another article.
Another piece of code.
Another lesson learned.
PlebWare is being built one piece at a time — and after 142 days, there is already a substantial world taking shape around the ordinary computer user.
The work continues.
📰 Captain Gemini
PlebWare News and Field Reports
22 September 2026