Code you and us
CMS platforms these days are becoming commoditised. The modelling of most systems lends itself to automation. Giving marketers more flexibility with less need for a developer. This does give developers more room to dive into the real challenges.
It’s what developers love to do most; creating code. So everything from low-code to no-code is what we are not trained, and especially do not live for. However these days with AI and better and better LLMs do come around the corner every day. The world of no-code is exploding and it becomes more promising every day. But ….
When working on Optimizely websites for different clients it is sometimes cumbersome to keep track of all the credentials to use to login to the CMS. Especially when using different databases to test several scenarios, being up-to-date with the latest production data or if the website is using Azure B2C in production.
One of the time-consuming tasks for content editors is filling in of metadata for web pages. But what if we told you there’s a solution that can automate this process?
In this blog post, we’ll explore how LLama, a language model, can help content editors by automatically generating metadata fields in Optimizely CMS 12.
After a consumer of tools like ChatGPT and CoPilot, we as developers like to dive deeper into it. How does it work? Where to start? Can I create my own? etc. In this blog we dive deeper into our first steps to run LLM’s on our local machine
Now we have worked for a while with Chaplin framework, I like to share an example about how easy it is to work with this pattern and show you how you can create a more “customer friendly” conversation while defining and programming the application.
It has been a while since we posted our last blogpost. But not without a reason. Today I am happy to share our thoughts on where we have worked on the last year. Start discovering doing product development in our organisation we felt the need of a more scaleable idea of doing software development. The result is Chaplin (The Movie Pattern Practice).
Finally we are going to put everything together. And share our verdict.
In this post we dive deeper into the `RelationRepository`, `CatalogContentStructureProvider`, `IInventoryService` and `IPriceService`. 4 items you need to be aware of before putting everything together.
As explained in the introduction of this series implementing a custom Catalog is not only overriding / replacing the `CatalogContentProvider`. In this chapter we are dive deeper into the the realted classes which do need some attention.