READ THIS FIRST?
2026-09-17
Who or What Is PlebWare?
It is time to explain the when, who, where, why, and what behind Plebware and PlebWare.
At first glance, the two spellings may look almost identical.
They are not.
There are two deliberate ways of writing and understanding the name.
Plebware, with a capital P and the word written as one word, represents the human being operating the technology. In conventional technology language, that person would usually be called the user or end user.
PlebWare, with both the P and the W capitalised, represents something much larger.
It represents the philosophy, ecosystem, projects, publications, educational material, software, research, and ideas that have grown around the original concept.
In simple terms:
Plebware is the person. PlebWare is the World we build around that person.
The human being is not an afterthought.
The human being is the reason the technology exists in the first place.
When Did PlebWare Begin?
The easiest answer is 2006.
The complete answer is considerably more complicated.
The roots of PlebWare reach back to 2003, when Otto Wilhelm Friedrich Brinkmeier founded 0tronix Developments.
0tronix was originally created as a media and information technology business. Its work included web design, graphic design, technical documentation, educational material, multimedia development, computer maintenance, invoicing systems, and other practical technology services.
The underlying idea was already there:
Technology should be used to educate, create, solve problems, and make life easier.
In 2006, the concept that would eventually become PlebWare began taking a recognisable form.
Otto Brinkmeier met Jullian Boyd de Villiers, and through that growing collaboration the project gained another important dimension through audio production and creative media.
Martin de Walt also became an early collaborator.
The name PlebWare emerged from those early discussions.
It was intended to describe technology created for ordinary people rather than technology designed exclusively around corporations, specialists, or technical elites.
The project subsequently developed through several stages.
There was the early concept.
There was the PlebWare identity.
There was the plebware.com period.
There was the development of the GitHub presence.
And eventually there was the modern transformation of PlebWare into a publishing, education, technology, and knowledge ecosystem.
The year 2026 represents another major turning point.
What had once been primarily associated with Linux, computing, repair, and technology has expanded into a much broader platform for publishing, education, artificial intelligence, digital creativity, research, practical computing, and software development.
So when someone asks:
“When did PlebWare begin?”
The honest answer is:
The roots began in 2003, the PlebWare identity emerged around 2006, the formal PlebWare era followed in 2010, and the modern ecosystem is the result of everything that came afterwards.
Who Is PlebWare?
This is where the distinction between Plebware and PlebWare becomes important.
Plebware is not a particular age group.
It is not a social class.
It is not a measure of education.
It does not mean somebody is technologically incapable.
Plebware simply means the human operator.
The person sitting behind the keyboard.
The person holding the phone.
The person repairing an old computer.
The person trying to understand Linux.
The person learning how artificial intelligence works.
The person writing a document.
The person creating a graphic.
The person trying to make an old piece of hardware useful again.
The person who wants technology to work with them, rather than constantly forcing them to work around the technology.
In conventional computing terminology, this person is normally called the user.
PlebWare deliberately uses another word because the word user often reduces a human being to a technical role.
PlebWare begins with the opposite idea.
The human is the operator.
The operator has intentions, experience, limitations, creativity, curiosity, preferences, and goals.
Technology is the tool.
The person remains the reason for using the tool.
That is why the human element is not merely another component of PlebWare.
It is the key component.
Where Did PlebWare Come From?
PlebWare was born in Johannesburg, South Africa.
Its earliest roots were connected to practical computing, media production, documentation, education, and small-business technology.
The project later operated through plebware.com, which served as an important part of the PlebWare story between approximately 2010 and 2020.
The GitHub Pages presence followed, providing a foundation for what would eventually become the modern PlebWare publishing platform.
The present home of PlebWare is:
plebware.github.io
This website is more than a collection of articles.
It has become a working laboratory.
It is a publishing platform.
It is a teaching resource.
It is a documentation system.
It is a research library.
It is a place for experimentation.
It is also the public record of a project that continues to evolve through practical experience.
The location may be Johannesburg, but the project itself is no longer geographically limited.
A person anywhere in the world can read a PlebWare article, learn something from it, use one of its tutorials, examine its software, study its documentation, or contribute through the wider ecosystem.
The physical origins are South African.
The knowledge is intended to be accessible to anyone.
Why Does PlebWare Exist?
The short answer is:
For convenience’s sake, and to cater to the needs of the operator.
But convenience does not mean laziness.
It means removing unnecessary obstacles.
Technology can be incredibly powerful while simultaneously being unnecessarily complicated.
People are often expected to change their behaviour simply because a piece of software was designed that way.
PlebWare approaches the problem from another direction.
What does the human being actually need?
How can the system make that task easier?
How can information be explained without unnecessary jargon?
How can an old computer remain useful?
How can software be repaired instead of immediately replaced?
How can knowledge be preserved?
How can technology help somebody learn rather than simply perform a task for them?
These questions are at the heart of the PlebWare philosophy.
The project therefore places considerable importance on:
- Accessibility.
- Understandability.
- Repairability.
- Practical education.
- Digital independence.
- Human creativity.
- Responsible use of technology.
- Preservation of knowledge.
- Respect for the person operating the system.
PlebWare does not exist simply to produce another piece of software.
It exists because technology is most useful when it serves a human purpose.
What Is PlebWare?
PlebWare is an evolving ecosystem built around one central idea:
Technology should remain connected to humanity.
It includes publishing, education, software development, Linux, artificial intelligence, digital creativity, research, documentation, and practical experimentation.
It also contains a growing vocabulary of projects and concepts.
Among these are PlebMachine, PlebTuition, PlebVox, PlebSticks, PlebPacks, PlebSword, PlebChurch, and other PlebWare projects.
These names are not merely branding.
Each represents an idea, a tool, a body of knowledge, or a particular part of the wider ecosystem.
The ecosystem has also changed considerably over time.
Some early PlebTerms have disappeared.
Others have evolved.
Some have become more important as the project developed.
The terminology is therefore a living part of PlebWare rather than a fixed dictionary.
PlebMachine — The Flagship Technology Project.
One of the most visible expressions of the PlebWare philosophy is PlebMachine.
PlebMachine is a state-driven Linux desktop orchestration system designed around the needs of the human operator.
It is not intended simply to install a collection of applications.
It is designed to help organise the computing environment around what the operator is trying to accomplish.
Different activities can require different environments.
Writing is different from research.
Research is different from graphics.
Graphics are different from music.
Development is different from accounting.
PlebMachine therefore explores the concept of Cognitive Modes and state-driven desktop configuration.
The important principle is that Cognitive Mode is not intended to imprison the operator inside a restricted environment.
The keyboard, right-click menu, Start Menu, and normal Linux desktop remain available.
Instead, the system provides a structured environment that can help the operator concentrate on the task at hand.
This reflects a much larger PlebWare principle:
The computer should adapt to the operator, not the operator to the computer.
PlebMachine is therefore not the definition of PlebWare.
It is one of the clearest practical demonstrations of what PlebWare believes.
PlebTuition — Learning Without the Lecture Hall.
PlebTuition began as the name for downloadable educational material.
The idea has grown considerably.
Today, PlebTuition represents the educational side of PlebWare.
That includes tutorials, explanations, lessons, guides, demonstrations, research material, technical documentation, and practical instruction.
The philosophy is straightforward.
Explain something.
Show how it works.
Allow the person to understand it.
Then let that person decide what to do with the knowledge.
PlebTuition therefore fits naturally into the larger PlebWare philosophy.
Knowledge should not be treated as something reserved for specialists.
If something can be explained clearly, it should be explained clearly.
PlebVox — Give the Knowledge a Voice.
PlebVox grew from the idea that written information should also be accessible through speech.
For many people, listening can be easier than reading.
A long article can become a spoken lesson.
A tutorial can become something that can be listened to while working.
A phone can become the communication terminal through which PlebWare speaks to its operator.
This is particularly important for the mobile side of the ecosystem.
PlebVox is therefore not simply a text-to-speech feature.
It represents another principle:
Knowledge should be available in forms that suit the person receiving it.
The written word remains important.
The spoken word adds another doorway into the same knowledge.
The PlebWare Ecosystem.
Over time, PlebWare has grown far beyond its original computing focus.
It now encompasses several interconnected areas.
Publishing.
Articles, journalism, personal writing, technical documentation, research, devotionals, and creative work.
Education.
Tutorials, PlebTuition lessons, technical guides, and practical explanations.
Technology.
Linux, PlebMachine, automation, desktop orchestration, scripting, and software development.
Artificial Intelligence.
Research, experimentation, AI-assisted development, AI reviews, and practical exploration of emerging tools.
Digital Creativity.
Graphics, multimedia, writing, audio, video, and creative experimentation.
Christian Publishing.
Devotional writing, Bible study resources, Christian education, and digital ministry.
Research and Preservation.
Documenting what works, what fails, what has changed, and what has been learned along the way.
These areas may appear different.
They are actually connected by the same principle.
Use technology to help people create, understand, learn, and do.
The PlebWare Philosophy.
The PlebWare philosophy can be expressed in a few simple ideas.
Technology should be:
- Accessible.
- Understandable.
- Repairable.
- Practical.
- Affordable where possible.
- Respectful of the operator.
- Designed to encourage learning.
- Used to preserve and share knowledge.
This philosophy also explains why Linux has remained so important to the project.
Linux provides an environment in which the operator can examine the system, modify it, repair it, automate it, and learn from it.
That does not mean every person must become a Linux expert.
It means the door is open to those who want to understand what is happening behind the interface.
PlebWare values that openness.
From User to Operator.
Perhaps the simplest way to understand PlebWare is to understand the difference between a user and an operator.
A user is often treated as someone who consumes technology.
An operator participates in it.
An operator asks:
Why does this work this way?
Can it be changed?
Can it be repaired?
Can I make it better?
Can I understand it?
Can I teach somebody else?
That change in language represents a change in philosophy.
PlebWare does not want to make people dependent on technology.
It wants people to become more capable through technology.
The goal is not to turn everyone into a programmer.
The goal is to make technology less intimidating and more useful.
The People Behind PlebWare.
PlebWare is a technical project, but it is also a human story.
Its history includes people who contributed ideas, skills, creativity, encouragement, development, audio production, writing, testing, and practical experience.
At the centre of that history is Otto Wilhelm Friedrich Brinkmeier, founder and continuing architect of the project.
Jullian Boyd de Villiers became an important development and creative collaborator during the early formation of the PlebWare identity.
Martin de Walt was an early collaborator who contributed to the development of the original PlebWare concept.
The project has also grown through the contributions of many people, tools, technologies, communities, and collaborators encountered along the way.
That is an important part of the story.
PlebWare was never created in a vacuum.
It developed through experience.
It developed through experimentation.
It developed through things that worked.
It developed through things that failed.
And it continues to develop because the work itself creates new questions.
Where Is PlebWare Going?
There is no final destination.
That is deliberate.
PlebWare is a living project.
The website will continue to grow.
PlebMachine will continue to evolve.
PlebTuition will continue to teach.
PlebVox will continue to explore ways of making information accessible.
New technologies will be examined.
Old technologies will continue to be repaired and reused where practical.
New articles will be written.
Old knowledge will be preserved.
Some ideas will succeed.
Some ideas will fail.
Both outcomes are useful if something is learned from them.
The future of PlebWare is therefore not simply about creating more software.
It is about continuing to build a body of practical knowledge that ordinary people can actually use.
So, Who or What Is PlebWare?
The answer is surprisingly simple.
Plebware is the human.
PlebWare is the World we build around the human.
PlebMachine is one of its major tools.
PlebTuition is its educational voice.
PlebVox helps give that knowledge a spoken voice.
And the website is where much of that knowledge is published, tested, documented, and preserved.
The spelling may seem like a small detail.
It is actually a statement of purpose.
The capital P in Plebware identifies the person.
The capital W in PlebWare identifies the World we build around that person.
The human comes first.
The technology comes second.
That is the idea at the heart of PlebWare.
The PlebWare Declaration.
Technology is a tool.
Knowledge is a resource.
Learning is a process.
Creativity is human.
And the person operating the machine should never be forgotten.
PlebWare exists to keep those things connected.
Learn.
Build.
Repair.
Create.
Share.
Teach.
That is PlebWare.
PlebWare.
Accessible. Repairable. Understandable Technology.
Plebware is the operator.
PlebWare is the World.
PlebMachine is the machine.
The human remains at the centre.
💬 Comments