Resources

This page collects links to documentation, downloads and the source repositories for JoinedWorkz. It is meant to be the starting point for both architects and developers when they want to go deeper into modeling, generators and build integration.

Documentation

The documentation explains the concepts behind JoinedWorkz, the modeling DSL, the standard generators and how to integrate generation into your build and repositories.

Product & concepts

Overview of the JoinedWorkz toolchain: modeling studio, model transformation, generators and Maven integration. Recommended for architects, technical leads and project owners who want to understand where JoinedWorkz fits.

Downloads

JoinedWorkz Studio is available as a standalone modeling studio for Windows, macOS and Linux. Select the release first, then choose the package for your platform. Maven generation does not require Studio or a Studio license.

Current release

JoinedWorkz Studio 1.3.81

Use Studio, the Maven plugin and facilities from the same JoinedWorkz release.

Release notes

To evaluate JoinedWorkz Studio 1.3.81, use its release-specific trial license key:

Download the 1.3.81 trial license key

Installation and first steps are described in the Install JoinedWorkz Studio guide.

Previous release JoinedWorkz Studio 1.3.80 Downloads

Use these packages only with JoinedWorkz 1.3.80 projects. The 1.3.80 Studio requires its own legacy trial key; the 1.3.81 key is not compatible with it.

Download the 1.3.80 trial license key Read the 1.3.80 documentation

Source code & issue tracking

The JoinedWorkz source code and related projects are hosted on GitLab. Depending on your setup, you may use the public repository, a mirror or an internal fork managed by your organization.

GitLab repositories

Browse the source code, inspect generator templates and follow the evolution of the toolchain and example projects.

Issues & enhancements

Depending on how you use JoinedWorkz (evaluation, commercial use, internal fork), issue tracking and feature requests can be handled either via GitLab or via direct support.

Where to start

Depending on your role and your goals, different entry points make sense: