Documentation
Primary version
Primary version
  • Cubbles documentation
  • First steps
    • Generate a project
    • Create a webpackage
    • Create an elementary component
    • Create a compound component
      • Compound slot initialization
  • Runtime extension - RTE
    • User guide
      • RTE Integration
      • The Cubbles TAG API
        • The Cubbles Dependency API
      • The Cubbles Javascript API
        • Interacting with Cubbles from the outside
        • Adding dynamic connections
        • Interacting with Elementary Cubbles from the inside
      • The RTE Processing
        • RTE initialization and rendering timeline
      • The Cubbles IFrame API
        • The Cubbles IFrame Resizer API
      • The Cubbles mutation based start event API
      • FAQs
        • How to manually resolve dependency conflicts?
        • How to create a component instance dynamically?
        • How to render HTML Markup coming from input slot?
        • How to replace a dependency when declaring a component instance?
        • How to synchronize multiple dataflows between component instances?
        • How to handle the copyValue flag for non serializable instances?
    • Contributor guide
      • CIF processing
  • Developing with the vanilla boilerplate
    • Creating a new project
    • Developing elementaries using the vanilla boilerplate
    • Developing compounds using the vanilla boilerplate
    • Using the vanilla boilerplate scripts
  • Coder devtools - CDT
    • User guide
      • Create Cubbles artifacts
      • Upload a Webpackage
      • Generate a README file
      • Rename an artifact
      • Configure network proxy
      • Validate the manifest.webpackage file
      • Change active webpackage
      • Bulk upload of webpackages
      • Release a webpackage
      • Update the RTE version of a webpackage
      • Prepare a webpackage to be released
      • Update webpackage to the next development version
      • Generate a test environment for a component
      • Testing Cubbles components
      • Validate sources
      • Create a demo webpackage
    • Contributor guide
      • Checklist for releasing a new webpackage.modelVersion
  • Terms and concepts
    • Webpackage
    • Artifacts
    • User roles
    • Base
Powered by GitBook
On this page
  • Composer
  • Page editor
  • App user
  • Coder
  1. Terms and concepts

User roles

PreviousArtifactsNextBase

Last updated 6 years ago

Composer

Composers are component related developers. They can compose (compound-) components using any number of existing components. Cubbles provides a Browser-based development environment (BDE) for composers.

Page editor

A Page Editor makes use of a Cubbles component by embedding the corresponding html tag into the body of a web page.

<body>
    <!--...-->
    <component-c1 cubx-webpackage-id="demo-package@1.0"></component-c1>
    <!--...-->
</body>

App user

Coder

For App Users Cubbles is something that works under the hood. Cubbles components are made to be used within 3rd party web apps. From the users point of view, the Cubbles and Cubbles components are loaded as any other resources when requesting a web app from their local web browser.

Coders are code-related developers. Using a editor of their choice, they can create a webpackage with any type of artifact. Cubbles provides a documented tool-set for coders .

RTE
(Coder DevTools)
Browser-based development environment (BDE)