Hi,

Everything done with Nuxeo Studio can be manually done because Nuxeo Studio only generates an XML contribution (and optionally some binary resources like images, icons…).

The documentation generally points to Nuxeo Studio because:

• it's the easier way to write contributions
• it manages automatic contributions upgrade.
  If an extension point changes from a Nuxeo version to another, then changing the target version in the project properties is enough, Nuxeo Studio will automatically generate the right contribution for a give version.
• it would not be possible to maintain handwritten documentation about such technical details. For that purpose, we provide automatically generated documentation:
• Javadoc
• Tag Library Documentation
• APIDoc (aka Platform Explorer)

Note you can use Studio to do some customization then analyze the generated contributions in the downloadable JAR.

Here is a step by step tutorial to develop with nuxeo. Hope it helps.

Step 1: Pull nuxeo code from git repository (https://github.com/nuxeo/nuxeo.git) and update the code by using python clone.py master -a

Step 2: Import the code into IntelliJ IDEA IDE.

Step 3: Build the project and create a maven run configration with following parameters: clean -DskipTests=true install -Paddons,distrib

You will find the executable built project under /YOUR_PATH_TO_NUXEO/nuxeo/nuxeo-distribution/nuxeo-server-tomcat/target/nuxeo-server-tomcat-9.2-SNAPSHOT/bin/

For detail tutorial you can see this link: https://github.com/epicprojects/nuxeo-tutorial

As a small example of Julien Carsique's claim, we have the beginnings of a document-type-only Marketplace package at https://github.com/courseload/nuxeo-schema-dot-org that works for us. Having done both, it is much quicker to use the Nuxeo Studio UI to make progress on business-specific data and workflow requirements, but it is true that everything can be done manually.

We didn't use Studio for the above project to prove that it could be done without Studio, to allow others to use that portion of our code without needing our whole Studio project, and because the document schema definitions were so repetitive that writing code to generate them was faster than manually updating them in a GUI.