Showing posts with label Newsletter. Show all posts
Showing posts with label Newsletter. Show all posts

The i18n Issue

Mike's Notes

This is a copy of the March issue of Ajabbi Research.

It is about the history of the effort to make Pipi available in any language, localisation, or script requested by users (i18n).

Ajabbi Research is published on SubStack on the first Friday of each month, and subscriptions are free.

Each issue is a broad historical overview of a research topic, serving as an index to dozens of previously posted related articles. There are now over 650 articles/posts.

This copy of the issue will be updated with additional information as it becomes available. Check the Last Updated date given below.

Eventually, each issue will be reused on the separate Ajabbi Research website as an introduction to a research area comprising multiple research projects.

Resources

References

  • SIL.
  • Unicode

Repository

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

Last Updated

19/04/2026

The i18n Issue

By: Mike Peters
Ajabbi Research: 6/03/2026

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

This is the story of the effort to make Pipi available in any human language and script. The steps taken have been part of Pipi's development since 2005, spanning 5 versions.

The NZERN Pipi 2003-2005 Development Plan started it all.

Pipi 4 (2005-2008)

The story starts with Pipi 4. It was a big, successful system that supported community-driven Ecological Restoration in NZ. Here is a history of that Pipi version.

Initially, the large websites that Pipi generated were in English only.  Then, as botanical and zoological information was added, Latin, English, and Maori names were used. Eventually, provision for Chinese was planned to support the Chinese community-led conservation programmes. There were no separate language data structures in the 850-table Pipi 4 database; instead, some entities had additional columns for each language.

English

  • The 25,000 pages of websites that Pipi generated were initially in English.

Latin

  • Scientific names used in biological data were written in Latin.

Maori

  • Over time, it was realised that support for the Maori Language, Te Reo Maori, was required. To start, bilingual volunteers provided lists of words for regional areas, towns, etc.

Chinese

  • There was an Auckland-based Chinese Community-driven initiative to reach older residents who didn't speak English about conservation.

    Pipi 6 (2017-2019)

    When Pipi was rebuilt from memory, based on the limited experience with Pipi 4, foundational work was done to prepare Pipi for better multilingual support. This would require extra databases.

    Metadata using international codes was added to every database table to enable future language usage. The codes used were ISO 639-3, Country, Unicode, and CLDR/LDML

    ISO 639-3

    ISO 639 gives comprehensive provisions for the identification and assignment of language identifiers to individual languages, and for the creation of new language code elements or for the modification of existing ones (Terms of Reference of the ISO639/MA). - ISO 639-3

    *** 

    It defines three-letter codes for identifying languages. The standard was published by the International Organisation for Standardisation (ISO) on 1 February 2007. As of 2023, this edition of the standard has been officially withdrawn and replaced by ISO 639:2023.

    ISO 639-3 extends the ISO 639-2 alpha-3 codes with an aim to cover all known natural languages. The extended language coverage was based primarily on the language codes used in the Ethnologue (volumes 10–14) published by SIL International, which is now the registration authority for ISO 639-3.[2] It provides an enumeration of languages as complete as possible, including living and extinct, ancient and constructed, major and minor, written and unwritten. However, it does not include reconstructed languages such as Proto-Indo-European.

    ISO 639-3 is intended for use as metadata codes in a wide range of applications. It is widely used in computer and information systems, such as the Internet, in which many languages need to be supported. In archives and other information storage, it is used in cataloging systems, indicating what language a resource is in or about. The codes are also frequently used in the linguistic literature and elsewhere to compensate for the fact that language names may be obscure or ambiguous. - Wikipedia

    Examples

    • Eng (English
    • Fra (French)

    ISO_3166-1_alpha-3

    ISO 3166-1 alpha-3 codes are three-letter country codes defined in ISO 3166-1, part of the ISO 3166 standard published by the International Organization for Standardization (ISO), to represent countries, dependent territories, and special areas of geographical interest. They allow a better visual association between the codes and the country names than the two-letter alpha-2 codes (the third set of codes is numeric and hence offers no visual association). They were first included as part of the ISO 3166 standard in its first edition in 1974. - Wikipedia

     Examples

    • ABW  (Aruba)
    • AFG  (Afghanistan)
    • AGO  (Angola)

    Unicode

    Unicode (also known as The Unicode Standard and TUS) is a character encoding standard maintained by the Unicode Consortium designed to support the use of text in all of the world's writing systems that can be digitized. Version 17.0[A] defines 159,801 characters and 172 scripts used in various ordinary, literary, academic and technical contexts. - Wikipedia

    Examples

    • Latn (Latin)
    • Lina (Linear B)
    • Hebr (Hebrew)

    CLDR/LDML

    The Common Locale Data Repository (CLDR) is a project of the Unicode Consortium to provide locale data in XML format for use in computer applications. CLDR contains locale-specific information that an operating system will typically provide to applications. CLDR is written in the Locale Data Markup Language (LDML). - Wikipedia

    Example

     <?xml version="1.0" encoding="UTF-8" ?>
    <ldml>
      
        <version number="1.1">ldml version 1.1</version>
        <generation date="2024-03-06"/>
        <language type="en"/>
        <territory type="US"/>
      
      <!-- other locale data sections follow -->
    </ldml>

    Localisation (L10N)

    Language localisation (or language localisation) is the process of adapting a product's translation to a specific country or region. It is the second phase of a larger process of product translation and cultural adaptation (for specific countries, regions, cultures or groups) to account for differences in distinct markets, a process known as internationalisation and localisation. - Wikipedia

    ***

    Pipi internally automatically stores and uses 3-letter language codes, 4-letter Unicode and 3-letter country codes to define Locales.

    Examples

    • eng-Latn-NZD (New Zealand English)
    • eng-Latn-USA (United States English)

    Customers can configure the options for their own websites.

    Examples

    • en-NZ
    • en-uk

    More information

    Pipi 7 (2020)

    Small, simple, static HTML mockups of websites were created to test how different languages could be used. Experiments with HTML and CSS were conducted to display text on a website in Left-to-Right (LTR) and Right-to-Left (RTL) word order.

    Pipi 8 (2021-2022)

    System-wide i18n and L10N namespaces were implemented throughout Pipi to enable reliable automation and rapid scaling across multiple languages.

    Pipi 9 (2023-2026)

    Joining up all the built systems to self-generate documentation and a front-end User Interface (UI).

    Experiments were conducted to determine how to integrate i18n support with Pipi's other features. It was confirmed that the Pipi core is written in British Standard English and checked by Grammarly.

    A source-target data model structure was created to store i18n scripts. It was greatly influenced by the system used by Wikipedia (MediaWiki) and OpenOffice.

    Experiments were done using 23 languages and writing scripts to test the CMS Engine (cms), data storage, UI layout, etc.

    String Translation

    Community translation will require a dedicated workspace.

    Account Settings

    Each Pipi is built in 1 language and script. Each account can have many languages. An account has many deployments, each in only one language. A deployment can have many workspaces.

    Localisation

    API Endpoints

    All API connections include a choice of API version and language/script.

    Script Font

    Noto from Google was chosen as the default font for Ajabbi due to the number of scripts it supports.

    KeyMan

    SIL provides an open-source KeyMan that enables keyboards for 2500 different languages to be added to websites. Pipi will use a Keyboard Engine (kyb) to provide this integration. This will be built as part of Pipi 10.

    Url Naming Pattern

    Many experiments were conducted to determine a URL structure that could accommodate websites in many languages. Wikipedia was the main influence.

    Examples

    • eng.example.com
    • example.com/eng/
    • en-uk.example.com
    • example.com/en-nz/

    Documentation

    Documentation and Learning material will need to be provided in many languages. The data models are ready for this. As the British English documentation is completed, it could be auto-translated into US English using Grammarly and into the 9 world languages using Google Translate. It would then need to be checked by volunteer users. This is speculative and will require trial and error to confirm.

    Language Prioritisation

    English > 9 world languages > 7000 local languages + localisation.

    Priority will be given to English, which will then serve as the source for translation into 9 world languages.

    • Arabic
    • Bhasa Indonesian
    • Chinese
    • French
    • German
    • Japanese
    • Hindi
    • Portugese
    • Russian
    • Spanish

    Carefully edited material in those languages can then be translated into any of the other 7,000 languages by volunteers in response to user requests.

      Model-driven UI

      The User Interface Description Language (UIDL) was an EU-funded project that was abandoned in 2010 after 10 years of excellent work. It was to enable accessibility on different screens and devices. The research results were reverse-engineered to build a User Interface Engine (usi) that would run in reverse to generate accessibility solutions for Pipi. The CSS Engine (css) replaced some redundant components of the UIDL project. Additional engines for localisation and personalisation were created.


      Pipi CMS Engine (cms)

      For a first teaching customer, a decision was made early on to autogenerate a separate website for each language (English, Māori, NZ Sign Language, and AAC picture language). This was the simplest solution for the CMS and the users.

      Creating UI for each natural language, including sign languages (i18n), requires user requests and volunteer testers.

      Sign Language

      The scheme was dreamed up to embed NZ Relay Video Interpreting on any webpage and in user workspaces. This is an ongoing experiment, driven by deaf people.

      Picture Language

      Professor Stephen Hawking used AAC via a computer-generated voice. There are many forms of AAC, including picture language. Providing this as a UI is being explored, with other AAC to follow. Important for the millions of people with Cerebral Palsy and Motor Neurone Disease.

      Invented Languages

      This system will be able to provide support for Klingon, Elvish, and other invented languages from books and movies, upon request and with volunteers prepared to do the work. This could be useful for fan communities.

      Dead Languages

      This system will be able to provide support for long-dead languages often studied by linguists and historians, such as Ancient Egyptian, Sumerian, Sanskrit, and Ancient Greek, upon request, with volunteers prepared to do the work. This could be useful for museums and faith communities.

      Workspace personalisation

      The workspace settings will eventually offer complete personalisation of the UI in other languages. This will use a personalisation form in account settings.

      Future Ajabbi Foundation Sponsorship

      Once Ajabbi has established ongoing sponsorship for Ortus for providing open-source BoxLang, the Ajabbi Foundation will generously sponsor open-source SIL KeyMan on an ongoing basis.

      Whats next

      Pipi 9 is available only in English. However, users can request any other language through their profile. Pipi 10 (2027-) will feature those multiple languages.

      The most useful and inspiring resource has been SIL Global.

      Dedication

      Every child has the right to be educated in the language of their people and of their birth. This is dedicated to those working tirelessly to record, strengthen or revive human languages.

      By , No comments:
      Tags , ,

      The Accessibility Issue

      Mike's Notes

      This is a copy of the February issue of Ajabbi Research.

      It is about the history of the effort to create a fully accessible User Interface (UI) for Pipi.

      Ajabbi Research is published on SubStack on the first Friday of each month, and subscriptions are free.

      Each issue is a broad historical overview of a research topic, serving as an index to dozens of previously posted related articles. There are now 647 articles/posts.

      This copy of the issue will be updated with additional information as it becomes available. Check the Last Updated date given below.

      Eventually, each issue will be reused on the separate Ajabbi Research website as an introduction to a research area comprising multiple research projects.

      Resources

      References

      • Web Accessibility Initiative - Accessible Rich Internet Applications (WAI-ARIA) 1.2, W3C, 6 June 2023.
      • Web Content Accessibility Guidelines (WCAG) 2.2, W3C, 12 December 2024.
      • GOV.UK Design System.

      Repository

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

      Last Updated

      6/03/2026

      The Accessibility Issue

      By: Mike Peters
      Ajabbi Research: 6/02/2026

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

      This is the story of the effort to make Pipi fully accessible to all who need it. The steps taken have been part of Pipi's development since 2005, spanning 5 versions.

      The NZERN Pipi 2003-2005 Development Plan started it all.

      Pipi 4 (2005-2008)

      The story starts with Pipi 4. It was a big, successful system that supported community-driven Ecological Restoration in NZ. Here is a history of that Pipi version.

      During that time, New Zealand (NZ) had dial-up modems. Many NZERN members were working farmers in rural areas, with very slow internet. Many were older with low computer literacy. This was a major factor determining what was possible. Web page sizes had to be kept under 16kb.

      Recently, an archive of Pipi 4 help documentation was discovered and is now available for viewing. It is incomplete, but it gives an idea of how it worked.

      Here is the description taken from the Pipi 4 Help archive. The Screen Reader Edition was designed for the blind members of NZERN by their family members.

      PIPI4 is available in four editions to meet the needs of different groups of NZERN members.

      Basic Edition

        • Designed for the novice computer user who wants a simple cut-down system, with instructions built into every step.
        • Skill level required: Capable of using a simple program like Outlook Express
        • Availability: All members of NZERN

      Standard Edition

        • Designed for the confident computer user who wants a system with help available with one click. The user can ask questions and report bugs to the help desk.
        • Skill level required: Capable of using a program like Microsoft Word
        • Availability: All members of NZERN

      Screen Reader Edition

        • Designed for the confident computer user who uses a screen reader and wants help available with one click. The user can ask questions and report bugs to the help desk.
        • Skill level required: Capable of using a program like Microsoft Word
        • Availability: All members of NZERN

      Professional Edition

        • Designed for the expert computer user capable of self-learning, who wants a fast system with detailed technical documentation available with one click. The user will provide support to other members as a member of the help desk.
        • Skill level required: Capable of using an advanced program like Adobe Photoshop
        • Availability: All members of the help desk

        Pipi 6 (2017-2019)

        When Pipi was rebuilt from memory, some work was done to prepare for a more modular, standardised model-driven User Interface (UI) approach. Metadata was added to every database table to enable future personalisation and meet accessibility requirements.

        Pipi 7 (2020)

        Small, simple, static HTML mockups of workspaces were created as experiments.

        Pipi 8 (2021-2022)

        System-wide namespaces were implemented to enable future complex automated interactions.

        Pipi 9 (2023-2026)

        In 2023, a year-long investigation into model-driven interfaces led to the reuse and hacking of several abandoned EU research efforts in Human-Computer Interaction (HCI).

        Putting a User Interface (UI) on the front end of Pipi 9 was challenging. It had to be

        • Model-driven
        • Adaptive to the users' devices
        • Automated
        • Meet the individual needs of each logged-on user

        Resources used

        1. OMG Interaction Flow Modelling Language (IFML)
        2. The CAMELEON References Framework (CRF)
        3. User Interface Description Language (UIDL)
        4. W3C Model-based UI Incubator

          Model-driven UI

          The User Interface Description Language (UIDL) was an EU-funded project that was abandoned in 2010 after 10 years of excellent work. It was to enable accessibility on different screens and devices. The research results were reverse-engineered to build a User Interface Engine (usi) that would run in reverse to generate accessibility solutions for Pipi. The CSS Engine (css) replaced some redundant components of the UIDL project. Additional engines for localisation and personalisation were created.


          UK Design System

          The UK Government has created a design system for building accessible websites. It includes many templates, components, tools, code, and guidance on achieving this. An excellent resource.

          These templates are being used for the Pipi-generated workspace User Interface (UI)

          Example


          A teaching customer

          Mr G, my coach from Startup Aotearoa, suggested finding a first customer who could be a teaching customer. What a good idea.

          As it happens, a new disability rights organisation emerged in response to funding cuts by the NZ government. The group led a national campaign that resulted in the Minister responsible for the cuts losing her job and the scale of the cuts being reduced. The group had no money and needed a large campaign website that was highly accessible for deaf and blind people. Helping lead this campaign and building the website were deep learning experiences for me.

          Pipi CMS Engine (cms)

          A decision was made early on to autogenerate a separate website for each language (English, Māori, NZ Sign Language, and AAC picture language). This was the simplest solution for the CMS and the users.

          Creating UI for each natural language, including sign languages (i18n), requires user requests and volunteer testers.

          The CMS uses a template engine that builds web pages from reusable components. This means that getting CCS correct only needs to be done once for each component, and so on.

          Sign Language

          The scheme was dreamed up to embed NZ Relay Video Interpreting onto any webpage. This is an ongoing experiment, driven by deaf people.

          Blind and Low Vision

          This didn't get far because blind people in NZ were needed to volunteer to help with testing. However, there are volunteers in other countries. This job depends on ongoing work on the CSS Engine (css). A particular challenge is catering for braille machines.

          Picture Language

          Professor Stephen Hawking used AAC via a computer-generated voice. There are many forms of AAC, including picture language. Providing this as a UI is being explored, with other AAC to follow. Important for the millions of people with Cerebral Palsy and Motor Neurone Disease.

          Workspace personalisation

          The workspace settings will offer complete personalisation of the UI. Similar in purpose to the wonderful AccessWidget from Accessibe.com. Instead of a pop-up, it will use a personalisation form in account settings.

          Keeping it simple

          On paper, WAI-ARIA looks great. However, the reality is that the growing interactive complexity of websites and differences in how browsers work mean that web pages break for people using assistive technology.

          Modern websites present a large attack surface, making them vulnerable. Pipi's solution is to focus on functionality, usability, and maximum simplicity. Small page sizes (Kb), semantic structure, and minimising JavaScript use.

          Standards

          The W3C Web Content Accessibility Guidelines (WCAG) sets the international standard for providing full accessibility. Pipi will endeavour to meet WAIG 2.2 as a new conformance target for all languages.

          Whats next

          Designing the workspaces has made accessibility through personalisation a top requirement. The ongoing 2026 workspace rollout will include further accessibility testing.

          The most useful and inspiring resource has been Smashing Magazine's weekly newsletter, which often covers accessible UI design in great depth.

          Dedication

          Those who have fought all their lives for a world where people with disabilities have equal rights and can fully participate without barriers to the extent they are capable.

          By , No comments:
          Tags , , ,

          The Workspace Issue

          Mike's Notes

          This is a copy of the January issue of Ajabbi Research.

          It is a historical overview of the effort to create a workspace-based UI for Pipi.

          Ajabbi Research is published on SubStack on the first Friday of each month, and subscriptions are free.

          Each issue is a broad historical overview of a research topic, serving as an index to dozens of previously posted related articles. There are now over 600 articles/posts.

          This copy of the issue will be updated with additional information as it becomes available. Check the Last Updated date given below.

          Eventually, each issue will be reused on the separate Ajabbi Research website as an introduction to a research area comprising multiple research projects.

          Resources

          References

          • Reference

          Repository

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

          Last Updated

          31/03/2026

          The Workspace Issue

          By: Mike Peters
          Ajabbi Research: 02/01/2026

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

          This is the story of how Pipi got a workspace-based User Interface (UI). The steps taken have been part of Pipi's development since 2007, spanning 5 versions.

          The NZERN Pipi 2003-2005 Development Plan started it all.

          Pipi 4 (2005-2008)

          The story starts with Pipi 4. It was a big, successful system that supported community-driven Ecological Restoration in NZ. Here is a history of that Pipi version.

          Due to very rapid scaling, a no-code approach was required to build the UI.

          NetSuite was the original inspiration. A database-based framework was constructed to store user interface components, and another database to store the information being displayed and edited.

          Recently, an archive of Pipi 4 help documentation was discovered and is now available for viewing. It is incomplete, but it gives an idea of how it worked.

          Pipi 6 (2017-2019)

          When Pipi was rebuilt from memory, the monolithic architecture was refactored into loosely coupled modules. Many new modules were created to support a rich UI. Each module had its own database.

          Pipi 7 (2020)

          Pipi was converted to microservices. Pipi could self-document. Static HTML mockups of workspaces were created as experiments. They were generic and could be applied to any subject domain, e.g., space, health, film, or experiments.

          Pipi 8 (2021-2022)

          System-wide namespaces were introduced, making Pipi headless, and the microservices were converted into autonomous agents (Engines). Self-documentation broke as a result.

          More agents were created to manage each other. Some were merged, and others split. These agents are large, with 10,000 lines of code common, and they maintain internal, complex databases, messaging, and workflows, all of which maintain state. None of them is stateless.

          Pipi 9 (2023-2026)

          Many of the internal engines were aggregated into complex systems. Some contained up to 20 different engines, all operating independently and interacting. These systems were then combined into more extensive systems, etc. So far, there are 300+ different engines (with multiple copies), and Pipi 9 has emerged.

          Key problems needed to be solved to enable a workspace-based UI to emerge from Pipi. These included;

          • Ontology-driven constraints
          • Domain modelling
          • Model-driven UI to provide automatic accessibility
          • Self-documenting
          • Structured learning
          • i18n for every human language and writing system.
          • Design system
          • Security and permissions
          • Useful URL patterns
          • Naming conventions
          • Ribbon menu

          Ontology-driven constraints

          The Ontolog Forum was a great help. BORO was hacked to run in reverse. This drives the system-wide constraints. The BORO Engine (bor) can also autonomously run forward if needed, similar to the KREB's cycle. This means ontologies can be imported into Pipi by the Ontology Engine (ont) to help provide world models based on primitives supplied by the Physical Law Engine (plw).

          In the Reductionist System (red), the Domain Engine (dmn) and Module Engine (mod) create data models using Domain-Driven Design (DDD) from ontologies.

          Model-driven UI

          The User Interface Description Language (UIDL) was an EU-funded project that was abandoned in 2010 after 10 years of excellent work. It was to enable accessibility on different screens and devices. The research results were reverse-engineered to build a User Interface Engine (usi) that would run in reverse to generate accessibility solutions for Pipi. The CSS Engine (css) replaced some redundant components of the UIDL project. Additional engines for localisation and personalisation were created.

          Self-documenting

          With the help of Alex Shkotin from the Ontolog Forum, templates were designed for the Wiki Engine (wik) and Docs Engine (doc) to automatically populate and generate system documentation from hundreds of agents and thousands of processes. There are some test examples to look at.

          Structured learning

          IEEE Learning Objects were an inspiration for the Learning Object Engine (lob). This engine was used to structure learning materials using Diataxis to address users' diverse learning needs. The Help Engine (hlp) takes the same material to provide in-context help in the UI.

          i18n for every human language and writing system

          Using SIL and Unicode naming conventions, the Language Engine (lng) stores UI translations in multiple languages and writing systems, enabling Pipi capable of supporting all 7,000 known languages. Then the Locale User Interface Engine (lui) creates localised UI.

          Design System

          A Design System Engine (dsg) was built to handle multiple design systems, including a default one for the initial workspace UI. The design system includes UI components and design tokens.

          Security and permissions

          Role-based Access Control (RBAC) was implemented to manage security and user permissions. This applies to different types of user accounts and to finer-grained access.

          Useful URL patterns

          Clear URL patterns were established.

          Naming conventions

          A naming convention was adopted for output directories and filenames based on simple predictive rules.

          Ribbon menu

          A ribbon navigation menu (Tab Group) outline was created that could also be a non-ribbon navigation. One source, many formats.

          Workspace Version 1 (October - November 2025)

          A roadmap was first created to provide focus and clarity.

          Batch processes created 15,000 files and directories to form workspaces containing static HTML web pages for testing. Each workspace had a ribbon menu and used iframes to organise navigation and content. Testing is successful.

          The  industry-based enterprise workspaces created for testing were:

          The Workspace Version 1 trial revealed that the UI is a thin wrapper around Pipi.

          Workspace Version 2 (April 2026)

          Changes to Workspace Version 2 include;

          Additional role-based user account types were added.

          Changes to the workspace engine model.

          Changes to deployment naming convention.

          Documentation for standard Enterprise workspaces.

          Documentation for customer support.

          Documentation for account settings.

          Documentation for Developer Account.

          Documentation for Agent Account.

          The Render Engine (rnd) then uses a database to create workspaces made of static HTML web pages.

          • Test
          • Feedback
          Setting up data centre automation has revealed that workspace deployments need to be performed in this order of account types due to the permissions cascade.
          • Agent Accounts (to admin Pipi)
          • Researcher Accounts (to edit UoM, ontologies and physical laws)
          • Developer Accounts (to create enterprise workspaces)
          • Personal Accounts (to sort out personal profiles - UI fonts, etc)
          • Enterprise Accounts (to test and use the system for work)
          • etc

          Workspace Version 3 (May 2026)

          The Render Engine (rnd) uses a database to generate workspace ribbon menus as static HTML web pages.

          • Test
          • Feedback

          Workspace Version 4 (June 2026)

          The Render Engine (rnd), Learning Object Engine (lob) and Help Engine (hlp) use databases to generate workspace user in-context documentation as static HTML web pages.

          • Test
          • Feedback

          Workspace Version 5 (July 2026)

          The Render Engine (rnd) and Form Engine (frm) use databases to generate workspace forms as static HTML web pages. See the Pipi 4 example, which will also be used here.

          Workspace Version 6

          The Render Engine (rnd), Form Engine (frm) and Docs Engine (doc) use databases to generate a complete HTML workspace demo with connected initial developer documentation rendered without errors.

          • Test
          • Feedback

          Workspaces for Pipi & Developers

          Working Workspaces for System Admin and DevOps use are deployed in the Pipi Core Data Centre. This will speed up development and production x10.

          Then

          The process of providing cloud workspaces for customers will begin.

          Whaikaha Access Activator

          An application to attend the 8-week Whaikaha Access Activator 2026 May intake is being submitted to kick this off. Using the Govt.UK Design System as an example, a simple paper-based process to design and test workable UI templates for;

          • Autism
          • Colour-blind
          • Irlen
          • Dyslexia
          • Physical or Motor Disability
          • Epilepsy
          Blind and deaf folks will be catered for with later separate projects.

          By , No comments:
          Tags , ,
          Subscribe to: Posts (Atom)