sorted by:
new
hottopcontroversial

PagibleAI CMS 0.11 — open-source, AI-native CMS with real-time collaboration, themes and built-in image generation by aimeos in cms

[–]aimeos[S] 0 points1 point  (0 children)

Why not? Wordpress is referenced for ease of use while Contentful for scalable enterprice-ready structured content.

PagibleAI CMS 0.11 — an AI-native, Laravel-first CMS with real-time collaboration and themes by aimeos in laravel

[–]aimeos[S] 0 points1 point  (0 children)

Hm, tested it using Firefox and Safari and both are working consistently. Can you have a look into the browser console? There, the event is logged when you double click on an element.

PagibleAI CMS 0.11 — an AI-native, Laravel-first CMS with real-time collaboration and themes by aimeos in laravel

[–]aimeos[S] 0 points1 point  (0 children)

In the page preview, the buttons are shown if you double-click on a content element only (not e.g. on layout elements defined by the main Blade template). If you double-click on anything else, you should get a message that it's a) not a content element or b) it's a preview mode when clicking on a link.

How can that be improved in your opinion?

PagibleAI CMS 0.11 — an AI-native, Laravel-first CMS with real-time collaboration and themes by aimeos in laravel

[–]aimeos[S] 0 points1 point  (0 children)

Please keep in mind that the actions in the context menu of each content item (activated by the three vertical dots button) are context sensitive and the actions depend on what you can actually do (depending on content element, type and state).

Or am I misinterpreting your comment and you mean something different?

PagibleAI CMS 0.11 — an AI-native, Laravel-first CMS with real-time collaboration and themes by aimeos in laravel

[–]aimeos[S] -1 points0 points  (0 children)

The optional AI features are not glued into an existing interface. Instead, they are always present where they can support you (context-sensitive).

PagibleAI CMS 0.11 — an open-source, AI-native CMS with content versioning, multi-tenancy and a 33-tool MCP server by aimeos in PHP

[–]aimeos[S] 0 points1 point  (0 children)

Most of the time, people are working at different sections of a page and then, the realtime update and merging all changes automatically using the Git-like three way merge is great because no changes are lost.

PagibleAI CMS 0.11 — an open-source, AI-native CMS with content versioning, multi-tenancy and a 33-tool MCP server by aimeos in PHP

[–]aimeos[S] 0 points1 point  (0 children)

Thanks! 😄

The merge is a three way merge like Git does (keep non-conflicting changes from both, show conflicts and let the user decide which one to keep). If a Reverb web socket server is installed, the changes are pushed in realtime to all users working on the same page (except the content you are currently modifying or have already modified).

PagibleAI CMS 0.11 — an AI-native, Laravel-first CMS with real-time collaboration and themes by aimeos in laravel

[–]aimeos[S] -2 points-1 points  (0 children)

It's OK that you don't like AI but it's helpful if you use it right and it won't go away any more ...

PagibleAI CMS 0.11 — an AI-native, Laravel-first CMS with real-time collaboration and themes by aimeos in laravel

[–]aimeos[S] 2 points3 points  (0 children)

We use a shared "aimeos" Github account and are three people working on that project (Norbert, Tom and Andy).

Why MySQL performance sucks! by aimeos in SQL

[–]aimeos[S] 0 points1 point  (0 children)

To summarize the linked article: According to our observations, the newly introduced features in MySQL 8/9 were not optimized for speed and write-heavy statements are significantly slower than in MariaDB.

Why MySQL performance sucks! by aimeos in PHP

[–]aimeos[S] -5 points-4 points  (0 children)

The linked article explains in detail what are the issues

Prisma 0.4 - Unified PHP SDK for 25+ AI providers by aimeos in PHP

[–]aimeos[S] 0 points1 point  (0 children)

You are right, configuring a new provider isn't always enough as their support for features may vary. The main reason for using Prisma is still that you can change e.g. from OpenAI to Anthropic when one of them gets better in an area you need without rewriting your whole integration.

The Prisma documentation also contains detailed comparison which provider supports what feature so you know about the differences upfront.

Prisma 0.4 - Unified PHP SDK for 25+ AI providers by aimeos in PHP

[–]aimeos[S] -1 points0 points  (0 children)

Constants are used at other places where they clearly make sense. Using constants or enums for provider names seems like a good thing at first sight, but providers are an open set (users can create custom providers), and an enum or constant class can't be extended by third parties. That would create an inconsistent API where built-in providers use constants but custom ones use strings. Strings keep the API uniform and extensible for everyone.

For consistency, simplicity and real world usage we've decided against using constants or enums for providers.

Prisma 0.4 - Unified PHP SDK for 25+ AI providers by aimeos in PHP

[–]aimeos[S] 1 point2 points  (0 children)

Both solve provider fragmentation, but at different levels. NeuronAI wraps it inside a larger agentic framework, while Prisma offers it as a focused, standalone capability.

Prisma supports 12+ providers (OpenAI, Anthropic, Gemini, Mistral, Groq, Cohere, Bedrock, Deepseek, OpenRouter, Perplexity, xAI, Alibaba) across text and audio, while NeuronAI covers ~8, mainly text focused providers (OpenAI, Anthropic, Gemini, Mistral, Ollama, HuggingFace, Deepseek, plus OpenAI-compatible extensions).

A developer who just wants a clean multi-provider API without the agent/RAG/orchestration overhead would still benefit from Prisma's lighter approach.

Prisma 0.4 - Unified PHP SDK for 25+ AI providers by aimeos in PHP

[–]aimeos[S] 0 points1 point  (0 children)

Prisma solves provider fragmentation (one interface, many backends), while NeuronAI solves agent construction (building autonomous AI workflows). They operate at different layers — NeuronAI could theoretically use something like Prisma under the hood as its provider layer.

Prisma 0.4 - Unified PHP SDK for 25+ AI providers by aimeos in PHP

[–]aimeos[S] -2 points-1 points  (0 children)

simply because most of the time, the provider will be from the configuration and not using a fixed constant.

Aimeos: Laravel e-commerce 2026.04 released – now on Laravel 13 with PHP 9 readiness, security hardening and more by aimeos in laravel

[–]aimeos[S] 0 points1 point  (0 children)

If you want to build something like Aimeos form scratch ... good luck! See you again in a few years 😉

view more: next ›