Ajabbi Research Monthly Newsletter

Mike's Notes

Below is an initial mockup of the proposed free monthly email newsletter from Ajabbi Research. The newsletter will focus on a different subject in-depth each month. Examples could include User Interfaces, Ontologies, and API.

Existing content from On a Sandy Beach and Ajabbi.com will be referred to.

This draft mockup is an experiment. A presentation will be given to the Open R&D Group on Sunday. All suggestions are welcome. Please forgive the formatting. It will get better.

Subscriptions

Anyone is welcome to subscribe; it's 100% free, and it can be discussed, shared, and reused.

Schedule

Publishing on SubStack will begin in January 2026 and will be issued on the first Friday of each month. Each issue will also be published on the Ajabbi Research website.

Planned Issues

  • January 2026: Design System
  • February 2026: i18n
  • March 2026: Open Handbook
  • April 2026: Complex Adaptive Systems
  • May 2026: Origins of Pipi
  • June 2026: 

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

06/10/2025

Ajabbi Research Monthly Newsletter

By: Mike Peters
On a Sandy Beach: 22/09/2025

Mike is the inventor and architect of Pipi and the founder of Ajabbi.


Ajabbi Research

January 2026

Design System Issue

"A design system is a set of standards to manage design at scale by reducing redundancy while creating a shared language and visual consistency across different pages and channels." - Therese Fessenden, NNGroup

Summary

One paragraph goes here. etc

The Problem

Some words to explain what the problem is, and what a design system does. The lack of a naming standard for components. Why the need for Design Tokens? etc

Design Systems

Give detailed examples of other successful design systems. etc

Design Tokens

Nathan Curtis. etc

Pipi Design System Engine

Explain how the Design System engine was built over time. Its unique features. Its integration with the CMS. UI component primitives. The engine can automatically lay out the components. No code interface. etc

User Customisation

Ability of users to customise the UI component primitives. etc

Conclusion

Two paragraphs of words go here. etc

References

  • Reference 1
  • Reference 2

Further Reading

  • Book 1
  • Book 2

See Also

  • Design System
  • Etc

External Links

No comments:

Post a Comment