
A few weeks ago, I wrote an article about Nuxeo Open Source and got some really great feedback! I still think that no matter how you're running Nuxeo-self-hosted or in the cloud-the best part about it being open source is that you (and now, all the AI models out there) have full access to the source code.
That means that any reasonably skilled dev team can learn and accomplish a lot by digging through the codebase, especially with the excellent JUnit test coverage that Nuxeo maintains.
But someone reached out with a great follow-up question: "What if I want to run Nuxeo Open Source... but how do I customize it without using Nuxeo Studio?"
Nuxeo Studio is a fantastic tool that empowers teams to quickly configure things like schemas, document types, workflows, automation, and more. Behind the scenes, Studio generates the necessary configuration files and bundles them into a JAR and Marketplace package. While it doesn't produce Java code (so there's nothing to compile), it creates all the XML and resource files needed to deploy your customizations.
But in some cases, maybe you're:
There's one major feature in Nuxeo that truly benefits from Studio for the initial setup: workflows. Studio's visual editor generates complex XML definitions that would be difficult (and tedious) to handcraft.
But don't worry-outside of Studio, you can still implement powerful workflow-like behavior using automation chains, custom operations, event listeners, and standalone task logic.
So let's look at how to build the rest of Nuxeo's features manually using the Nuxeo CLI, and a bit of XML and Java.
Here's what's in Studio's "Configuration" panel, and how you can build each of those manually:
nuxeo bootstrap multi-module → generates Maven project with nuxeo and marketplace modulesLifeCycleCoreExtensions.xml on GitHubcontent-template-contrib.xml on GitHubresources/scripts/. (But if you're working outside Studio, it's probably better to write Java operations instead-more powerful, testable, and maintainable.) Automation Scripting, Contributing an Operation.ftl templates in automation chains. Template Rendering AddonA great idea is to look at the source code of nuxeo-retention. It includes:
It's a solid example of how to build and maintain a real Nuxeo plugin outside Studio.
Hope this helps! And, remember, while everything here is possible without it, Studio is generally the fastest way to customize Nuxeo.
Keep reading
The official Nuxeo roadmap from Hyland CommunityLIVE: what ships in H2 2025, what’s planned for H1 2026, and what’s coming in H2 2026 and beyond.
Read articleAlready running Nuxeo? You have everything you need to add serious AI capabilities—embeddings, semantic search, MCP, async pipelines. Here’s why and how.
Read articleAlready on AWS? Use AgentCore Gateway as a managed MCP server for Nuxeo. Configure inbound/outbound auth and an OpenAPI schema—no self-hosted MCP needed.
Read articleTell us what you're struggling with, and we'll tell you how we can help you.
Talk to us