KleeneStar 0.0.3‑alpha – New Document Type

With rapid and continuous development, KleeneStar is becoming increasingly complete, making now the ideal time to address deeper technical details that there was no time for in the previous process. A central point concerns the structuring of system components. Some time ago, objects were already divided into four core object types such as Document, Blog, Issue, and Asset, which are provided by default by the core system and can be flexibly expanded with custom categories via plugins if needed. Now, the internal structure of these four main groups should be further subdivided and specified. Since each of these object types is already implemented as its own class in the software, this deeper segmentation can be technically realized without any problems. The next concrete step in the implementation is the integration of a new form view. These forms fundamentally behave like classic documents in the system and are displayed identically in the tree structure. The essential difference lies in the operation. When editing, users are shown a structured input mask instead of the usual WYSIWYG editor, while the reading view converts the content into an unchangeable view, guaranteeing a seamless and logical integration of the various document types into the overall system.


This extension can be implemented in a wonderfully straightforward way because KleeneStar is modularly structured from the ground up and can be flexibly adapted. The new approach involves extending the classes to include the specification of the desired renderer, such as WYSIWYG or Form. The special thing about this is that each object type can define its very own renderers, which can also be flexibly added via plugins. This makes this logic universally applicable to documents as well as to all other object types. Since the renderers themselves are completely modularly extendable, the system remains slim, easy to maintain, and open to future interface concepts, while at the same time the usability for end users is noticeably enhanced.

It is precisely at this architectural interface that the project thrives on the experience and feedback of the entire community, which is why we now need your active support. If you want to actively help shape the future of KleeneStar, now is the perfect moment to join. We are looking for developers who want to implement the class-based renderer mapping in the core and define the plugin interfaces for new renderer types with us. Participate in the current architectural discussions or submit a pull request directly to lift the 0.0.3-alpha release to the next level together.
Location: Cottbus, Deutschland

Comments

Post a Comment

Popular posts from this blog

KleeneStar – Project Launch

Image
What began as an initial idea in 2021 is now taking concrete shape: KleeneStar has officially launched. On May 3, 2021, the project name was chosen, a deliberately selected term from the world of formal languages, symbolizing repetition, modularity, and creative combinability. Since then, time has been used intensively to develop concepts, explore technical feasibility, and lay a solid foundation. KleeneStar is no quick fix, but the result of thoughtful planning and forward-looking architecture. KleeneStar is a modular, extensible platform project for knowledge management, process tracking, and collaborative ecosystems. Its goal is to provide technical and visual structures that foster collaborative work, enable transparent workflows, and support sustainable documentation. A key milestone was the creation of the GitHub organization Kleene-Star, accompanied by an initial project description. This includes foundational concepts, a preliminary requirements definition, and the beginning o...
Read more

KleeneStar – Publication of the Concept as the Foundation for the Next Steps

Image
With the publication of the KleeneStar Concept , a decisive cornerstone has been laid for future development. The concept describes the entire architecture of the system and serves as the conceptual basis for a reference implementation that encompasses data modeling, system architecture, and user interfaces. At its core lies the interaction of all central components required to create a scalable, multi-tenant, and secure environment. The concept defines the principles by which information is structured, instances and attributes are managed, and relationships between objects are established. At the same time, a context-sensitive authorization model is introduced, enabling precise control of access rights and forming the foundation for secure collaboration. From Concept to Implementation The publication of this concept represents the first building block on the path toward full implementation. In the upcoming phases, the individual components will be developed step by step and translate...
Read more

KleeneStar 0.0.1-alpha – A Flexible Data Model with Entity Framework

Image
The development of KleeneStar began with a simple file‑based data storage system that was entirely sufficient for the early phase of UI development. As long as the focus remained on the user interface, this approach proved to be pragmatic and efficient. At the same time, the principle of persistent data storage was a central part of KleeneStar ’s architecture from the very beginning, even if it remained intentionally in the background during the initial stages. A platform like KleeneStar , designed to be modular, open, and extensible in the long term, requires a storage architecture that can reliably support these ambitions. As the feature set grew and the Workspace component became increasingly important, the question of flexible and sustainable data management moved steadily into focus. This evolution led to the consideration of how to design a data model that is not tied to a single database but remains open enough to support different storage technologies in parallel. The goal was...
Read more