Doc

Sub-sections here in Doc:

Components
An overview and descriptions of the Boxxd components.
Building boxxds
Topics around building components and boxxds.
Style Guide
A guide to writing styles, naming conventions, logo.
Wiring | API
A description of Wiring and the API.
Licensing
A guide to the myBoxxd licensing and the use of Boxxd assets

By Dev | 27 August, 2017

Packages

A list of packages is available under /packages.

List of other topics

Components

A brief overview A boxxd is available pre-packaged as well as separate components which can be used DIY style to build your own boxxd. A structural overview of the components: Boxxd family | |-- myBoxxd (the digital containers or boxxds) | |-- Instant°Boxxd - Off-the-shelf solutions | |-- Boxxdlets - such as myProject, mySell | |-- B2 Sets - Boxxds in a boxxd sets | |-- Tool°Boxxd - myBoxxd building components |-- Bases - Base components |-- Utils - Utilities such as javascripts |-- Plugins - The apps, active and passive such as a repository |-- Templates - File to use to create docs, work faster |-- Insights - Learning materials |-- Seeds - pre-packaged boxxds ready to be extended An overview of each type of component is described in separate sections: See the section list above.

Continue reading

Building boxxds

Building components and boxxds The posts below describe how to build a boxxd or a new component. Use of existing parts The library of existing parts is growing. See the: components section for more detail or the software components used. General guidelines The way things are named Styles used Keeping track of Terms and names used Certain user types have been defined Articles on building

Continue reading

Style Guide

A brief overview To facilitate the use of Boxxd, the documentation should be consistent in the use of terms and how “things” are called. The following documents have been written to act as guidelines for documentation writers. List of contents

Continue reading

Wiring | API

A brief description wiring is the name for the stuff that wires the various boxxd parts together. A myBoxxd package has a .wiring directory which contains meta data for the various packages, but it also contains components such as javascript libraries, fonts, css for the plugables. Wiring is being conceived so that automation scripts can run on top of a myBoxxd container and perform various functions such as extra meta information, do maintenance work or build new components.

Continue reading

Licensing

Use The terms of use are based on the License Apache 2.0 The use of the logo and terms of use are defined here

Continue reading

Tools and credits

Boxxd uses several tools and specs for it to work. This doc lists the tools, links and authors.

Continue reading

Generic user types

To provide a framework for Boxxd’s development, various individual user profiles have been defined, specifying their knowledge, expectations and their use of tools.

Continue reading