I broke the CMS

Mike's Notes

The best way to learn is to make mistakes. Oops.

Resources

• https://wiki.ajabbi.com/eng/9/engines.html
• https://www.blog.ajabbi.com/2025/03/learning-object-integration-with-cms.html
• https://www.blog.ajabbi.com/2025/03/embedding-wolfram-notebooks.html
• https://www.blog.ajabbi.com/2025/03/creating-environment-for-plug-ins.html
• https://developer.ajabbi.com/eng/9/report/roadmap.html

References

• 
  

Repository

• Home > PipiWiki > Engines

Last Updated

24/03/2025

I broke the CMS

By: Mike Peters

21/03/2025

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

The integration experiment running live data through the Plug-in Engine (plu) and Learning Object Engine (lob) with the Content Management Engine (cms) didn't work.

It led me to discover a previously hidden issue with the CMS data model, which yesterday led to the model's change and the CMS's now-broken state.

To get the CMS working again, a lot of code must be revised. The Template Engine (tem) and the Render Engine (rnd) will also need minor altering.

However, with these complex changes, the integration to enable plug-ins and learning objects should now work in future.

I have been using a temporary workaround to successfully work with all 3 engines.

Plug-ins are necessary for two current projects;

• my first customer needs live-sign language interpreters via Relay (a video service) embedded on their static website
• Embedding Wolfram Notebooks on Pipi documentation pages

Learning objects are necessary for these tasks on the roadmap;

• User documentation
• the UI help system

I also realised that adding plug-ins and learning objects is not on the published roadmap. A job that is now done. (Roadmap wbs 4.1 - 4.5)