change standard struct

.babelrc.json

-{
-
-}

.flowconfig

-[ignore]
-
-.*/playground
-.*/node_modules
-.*/node_modules/
-/node_modules/
-
-[include]
-
-[libs]
-
-[lints]
-
-[options]
-
-[strict]

.gitignore

-.phpunit.result.cache 
-.nyc_output
-coverage
-/process
-
-
-#####################ALLGEMEINER TEIL
-
-
-
-# yarn v2
-.yarn/cache
-.yarn/unplugged
-.yarn/build-state.yml
-.yarn/install-state.gz
-.pnp.*
-
-.cache
-
-# Optional npm cache directory
-.npm
-
-# Optional eslint cache
-.eslintcache
-
-# Microbundle cache
-.rpt2_cache/
-.rts2_cache_cjs/
-.rts2_cache_es/
-.rts2_cache_umd/
-
-# Dependency directories
-node_modules/
-jspm_packages/
-
-# Snowpack dependency directory (https://snowpack.dev/)
-web_modules/
-
-# Logs
-*.log
-npm-debug.log*
-yarn-debug.log*
-yarn-error.log*
-lerna-debug.log*
-
-# Cloud9 IDE - http://c9.io
-.c9revisions
-.c9
-
-##Exclipse
-.metadata
-tmp/
-*.tmp
-*.bak
-*.swp
-*~.nib
-local.properties
-.settings/
-.loadpath
-.recommenders
-
-# External tool builders
-.externalToolBuilders/
-
-# Locally stored "Eclipse launch configurations"
-*.launch
-
-# PyDev specific (Python IDE for Eclipse)
-*.pydevproject
-
-# CDT-specific (C/C++ Development Tooling)
-.cproject
-
-# CDT- autotools
-.autotools
-
-# Java annotation processor (APT)
-.factorypath
-
-# PDT-specific (PHP Development Tools)
-.buildpath
-
-# sbteclipse plugin
-.target
-
-# Tern plugin
-.tern-project
-
-# TeXlipse plugin
-.texlipse
-
-# STS (Spring Tool Suite)
-.springBeans
-
-# Code Recommenders
-.recommenders/
-
-# Annotation Processing
-.apt_generated/
-.apt_generated_test/
-
-# Scala IDE specific (Scala & Java development for Eclipse)
-.cache-main
-.scala_dependencies
-.worksheet
-
-# Uncomment this line if you wish to ignore the project description file.
-# Typically, this file would be tracked if it contains build/dependency configurations:
-#.project
-
-##Kate
-# Swap Files #
-.*.kate-swp
-.swp.*
-
-## KDEDevelop
-*.kdev4
-.kdev4/
-
-## LibreOffice
-# LibreOffice locks
-.~lock.*#
-
-
-### LINUX
-*~
-
-# temporary files which can be created if a process still has a handle open of a deleted file
-.fuse_hidden*
-
-# KDE directory preferences
-.directory
-
-# Linux trash folder which might appear on any partition or disk
-.Trash-*
-
-# .nfs files are created when an open file is removed but is still being accessed
-.nfs*
-
-## Patches
-*.orig
-*.rej
-
-# Private key
-*.ppk
-
-## Sublime
-# Cache files for Sublime Text
-*.tmlanguage.cache
-*.tmPreferences.cache
-*.stTheme.cache
-
-# Workspace files are user-specific
-*.sublime-workspace
-
-# Project files should be checked into the repository, unless a significant
-# proportion of contributors will probably not be using Sublime Text
-# *.sublime-project
-
-# SFTP configuration file
-sftp-config.json
-sftp-config-alt*.json
-
-# Package control specific files
-Package Control.last-run
-Package Control.ca-list
-Package Control.ca-bundle
-Package Control.system-ca-bundle
-Package Control.cache/
-Package Control.ca-certs/
-Package Control.merged-ca-bundle
-Package Control.user-ca-bundle
-oscrypto-ca-bundle.crt
-bh_unicode_properties.cache
-
-# Sublime-github package stores a github token in this file
-# https://packagecontrol.io/packages/sublime-github
-GitHub.sublime-settings
-
-## VIM
-# Swap
-[._]*.s[a-v][a-z]
-!*.svg  # comment out if you don't need vector files
-[._]*.sw[a-p]
-[._]s[a-rt-v][a-z]
-[._]ss[a-gi-z]
-[._]sw[a-p]
-
-# Session
-Session.vim
-Sessionx.vim
-
-# Temporary
-.netrwhist
-
-# Auto-generated tag files
-tags
-# Persistent undo
-[._]*.un~
-
-# Windows thumbnail cache files
-Thumbs.db
-Thumbs.db:encryptable
-ehthumbs.db
-ehthumbs_vista.db
-
-# Dump file
-*.stackdump
-
-# Folder config file
-[Dd]esktop.ini
-
-# Recycle Bin used on file shares
-$RECYCLE.BIN/
-
-# Windows Installer files
-*.cab
-*.msi
-*.msix
-*.msm
-*.msp
-
-# Windows shortcuts
-*.lnk
-
-# gitignore template for AWS Serverless Application Model project
-# website: https://docs.aws.amazon.com/serverless-application-model
-
-# Ignore build folder
-.aws-sam/
-
-# Netbeans
-**/nbproject/private/
-**/nbproject/Makefile-*.mk
-**/nbproject/Package-*.bash
-build/
-nbbuild/
-nbdist/
-.nb-gradle/
-
-
-
-# Covers JetBrains IDEs: IntelliJ, RubyMine, PhpStorm, AppCode, PyCharm, CLion, Android Studio, WebStorm and Rider
-# Reference: https://intellij-support.jetbrains.com/hc/en-us/articles/206544839
-
-# User-specific stuff
-.idea/**/workspace.xml
-.idea/**/tasks.xml
-.idea/**/usage.statistics.xml
-.idea/**/dictionaries
-.idea/**/shelf
-
-# Generated files
-.idea/**/contentModel.xml
-
-# Sensitive or high-churn files
-.idea/**/dataSources/
-.idea/**/dataSources.ids
-.idea/**/dataSources.local.xml
-.idea/**/sqlDataSources.xml
-.idea/**/dynamic.xml
-.idea/**/uiDesigner.xml
-.idea/**/dbnavigator.xml
-
-# Gradle
-.idea/**/gradle.xml
-.idea/**/libraries
-
-# Gradle and Maven with auto-import
-# When using Gradle or Maven with auto-import, you should exclude module files,
-# since they will be recreated, and may cause churn.  Uncomment if using
-# auto-import.
-# .idea/artifacts
-# .idea/compiler.xml
-# .idea/jarRepositories.xml
-# .idea/modules.xml
-# .idea/*.iml
-# .idea/modules
-# *.iml
-# *.ipr
-
-# CMake
-cmake-build-*/
-
-# Mongo Explorer plugin
-.idea/**/mongoSettings.xml
-
-# File-based project format
-*.iws
-
-# IntelliJ
-out/
-
-# mpeltonen/sbt-idea plugin
-.idea_modules/
-
-# JIRA plugin
-atlassian-ide-plugin.xml
-
-# Cursive Clojure plugin
-.idea/replstate.xml
-
-# Crashlytics plugin (for Android Studio and IntelliJ)
-com_crashlytics_export_strings.xml
-crashlytics.properties
-crashlytics-build.properties
-fabric.properties
-
-# Editor-based Rest Client
-.idea/httpRequests
-
-# Android studio 3.1+ serialized cache file
-.idea/caches/build_file_checksums.ser
-
-

.gitlab-ci.yml

-image: node:16
-
-cache:
-  paths:
-    - node_modules/
-
-stages:
-  - setup
-  - test
-
-test:
-  stage: test
-  script:
-    - apt-get update && apt-get install -y jq  gawk plantuml
-    - make test        
-
-
-include:
-  - template: Security/Secret-Detection.gitlab-ci.yml
-
-    

.gitlab/issue_templates/Bug.md

-<!---
-
-USE THIS TEMPLATE TO DESCRIBE AN ERROR.
-
-- Check whether the error has already been documented.
-- Be as precise as possible.
-- Write in such a way that someone else can understand the error.
-- Describe only one bug per ticket.
-- Separate facts from assumptions.
-
---->
-
-### Current bug
-
-<!-- 
-
-- Describe the misbehaviour as precisely as possible.
-- What is not working, how does the misbehaviour manifest itself.
-- What is the expected *correct* behaviour?
-- Can you add screenshots?
-- How can you reproduce the error?
-- Describe the steps that lead to the error.
-    
--->
-
-### Affected environment
-
-<!-- 
-
-- Which components are affected?
-- On which operating system in which version did the error occur?
-- Which version of PHP, browser, operating system is affected?
-    
--->
-
-- (No environment documented yet)
-
-
-### Possible solutions
-
-<!-- 
-
-- Suggest bug fixes here
-- If you have code, submit a merge request
-
--->
-
-- (no solution defined yet)
-
-### References
-
-<!-- 
-
-- Link to solutions (stackoverflow, documentation, etc)
-- Link to related tickets, quotes, lines of code.
-
--->
-
-- (no links yet)
-
-
-<!-- Commands -->
-
-/label ~bug

.gitlab/issue_templates/Enhancement.md

-<!---
-
-WITH THIS TEMPLATE YOU DESCRIBE AN IMPROVEMENT OF AN EXISTING FUNCTION.
-
-- Check if the improvement is already documented.
-- Be as precise as possible.
-- Write in such a way that someone else understands the improvement.
-- Describe only one improvement per ticket.
-
---->
-
-### Objectives & requirements
-
-<!--
-
-- Describe as precisely as possible what should be improved.
-- Also describe what should not be implemented.
-- Name the target group of the improvement: developer, customer, user ...
-- If possible, create a sketch or UML diagram of the improvement.
-    
--->
-
-### Conception & implementation
-
-<!-- 
-
-- How can the improvement be achieved.
-- If possible, create a wireframe, UML diagrams or sketches.
--
-
--->
-
-### Dependencies & side effects
-
-<!-- 
-
-- Is this an overarching function?
-- Are other projects affected?
-
--->
-
-- (No dependencies defined yet)
-
-### References
-
-<!-- 
-
-- Link to solutions (stackoverflow, documentation, etc)
-- Link to related tickets, quotes, lines of code.
-
--->
-
-- (no links yet)
-
-
-<!-- Commands -->
-
-/label ~enhancement
-

.gitlab/issue_templates/Feature-Request.md

-<!---
-
-WITH THIS TEMPLATE YOU DESCRIBE A NEW FUNCTION THAT DOES NOT YET EXIST.
-
-- Check whether the new function is already documented.
-- Be as precise as possible.
-- Write in a way that someone else will understand the new feature.
-- Describe only one feature per ticket, if you are describing something bigger use the 
-  the story template
-
---->
-
-### Objectives & requirements
-
-<!--
-
-- Describe as precisely as possible what you intend to do.
-- Also write what is not to be implemented.
-- Name the target group of the new function: developer, customer, user ...
-- If possible, create a sketch or UML diagram of the function.
-    
--->
-
-### Conception & implementation
-
-<!-- 
-
-- How can the function be implemented.
-- If possible, create a wireframe, UML diagrams or sketches.
--
-
--->
-
-### Dependencies & side effects
-
-<!-- 
-
-- Is this an overarching function?
-- Are other projects affected?
-
--->
-
-- (No dependencies defined yet)
-
-### References
-
-<!-- 
-
-- Link to solutions (stackoverflow, documentation, etc)
-- Link to related tickets, quotes, lines of code.
-
--->
-
-- (no links yet)
-
-
-<!-- Commands -->
-
-/label ~feature
-

.gitlab/merge_request_templates/Bugfix.md

-## References
-
-<!-- 
-
-    Every merge request needs at least one reference!
-
-    Mention the ticket, include links to
-    further information, processes, etc.
-
--->
-
-- (no link inserted yet)
-
-## Author's checklist (required)
-
-- [ ] **In the "References" section above**, link to at least one issue, ticket or process.
-- [ ] Confirm that your merge request contains an appropriate test case.
-- [ ] Confirm that you have followed the [Code Style Guide](https://about.schukai.com/de/intern/handbuch/referenzen/best-practices-code-styleguide/).
-- [ ] Confirm that you have followed the [Documentation Style Guide](https://about.schukai.com/de/intern/handbuch/leitfaden/uebersicht/).
-
-## Checklist for the reviewer (if possible)
-
-- [ ] Confirm that the merge request meets the requirements of the linked issues.
-- [ ] Confirm that the merge request contains appropriate test cases.
-- [ ] Code analysis has been performed.
-- [ ] Set the merge request to approved.
-
-## Release Manager Checklist (required)
-
-- [ ] Assign this merge request to a milestone.
-- [ ] Record the changes in the changelog (changelog.md).
-
-
-<!-- Commands -->
-
-/label ~bugfix

.gitlab/merge_request_templates/Enhancement.md

-## References
-
-<!-- 
-
-    Every merge request needs at least one reference!
-
-    Mention the ticket, include links to
-    further information, processes, etc.
-
--->
-
-- (no link inserted yet)
-
-## Author's checklist (required)
-
-- [ ] **In the "References" section above**, link to at least one issue, ticket or process.
-- [ ] Confirm that your merge request contains an appropriate test case.
-- [ ] Confirm that you have followed the [Code Style Guide](https://about.schukai.com/de/intern/handbuch/referenzen/best-practices-code-styleguide/).
-- [ ] Confirm that you have documented the change.
-- [ ] Confirm that you have followed the [Documentation Style Guide](https://about.schukai.com/de/intern/handbuch/leitfaden/uebersicht/).
-
-## Checklist for the reviewer (if possible)
-
-- [ ] Confirm that the merge request meets the requirements of the linked issues.
-- [ ] Confirm that the merge request contains appropriate test cases.
-- [ ] Code analysis has been performed.
-- [ ] Set the merge request to approved.
-
-## Release Manager Checklist (required)
-
-- [ ] Assign this merge request to a milestone.
-- [ ] Record the changes in the changelog (changelog.md).
-
-
-<!-- Commands -->
-
-/label ~enhancement

.gitlab/merge_request_templates/Feature.md

-## References
-
-<!-- 
-
-    Every merge request needs at least one reference!
-
-    Mention the ticket, include links to
-    further information, processes, etc.
-
--->
-
-- (no link inserted yet)
-
-## Author's checklist (required)
-
-- [ ] **In the "References" section above**, link to at least one issue, ticket or process.
-- [ ] Confirm that your merge request contains an appropriate test case.
-- [ ] Confirm that you have followed the [Code Style Guide](https://about.schukai.com/de/intern/handbuch/referenzen/best-practices-code-styleguide/).
-- [ ] Confirm that you have documented the function.
-- [ ] Confirm that you have followed the [Documentation Style Guide](https://about.schukai.com/de/intern/handbuch/leitfaden/uebersicht/).
-
-## Checklist for the reviewer (if possible)
-
-- [ ] Confirm that the merge request meets the requirements of the linked issues.
-- [ ] Confirm that the merge request contains appropriate test cases.
-- [ ] Code analysis has been performed.
-- [ ] Set the merge request to approved.
-
-## Release Manager Checklist (required)
-
-- [ ] Assign this merge request to a milestone.
-- [ ] Record the changes in the changelog (changelog.md).
-
-
-<!-- Commands -->
-
-/label ~feature

.gitlab/merge_request_templates/Release.md

-## References
-
-<!-- 
-
-    Every merge request needs at least one reference!
-
-    Mention the ticket, include links to
-    further information, processes, etc.
-
--->
-
-- (no link inserted yet)
-
-## Author's checklist (required)
-
-- [ ] **In the "References" section above**, link to at least one issue, ticket or process.
-- [ ] Confirm that your merge request contains an appropriate test case.
-- [ ] Confirm that you have followed the [Code Style Guide](https://about.schukai.com/de/intern/handbuch/referenzen/best-practices-code-styleguide/).
-- [ ] Confirm that you have documented the change.
-- [ ] Confirm that you have followed the [Documentation Style Guide](https://about.schukai.com/de/intern/handbuch/leitfaden/uebersicht/).
-
-## Checklist for the reviewer (if possible)
-
-- [ ] Confirm that the merge request meets the requirements of the linked issues.
-- [ ] Confirm that the merge request contains appropriate test cases.
-- [ ] Code analysis has been performed.
-- [ ] Set the merge request to approved.
-
-## Release Manager Checklist (required)
-
-- [ ] Assign this merge request to a milestone.
-- [ ] Record the changes in the changelog (changelog.md).
-
-
-<!-- Commands -->
-
-/label ~release

LICENSE

-LICENSE
-
-* All content residing under the "docs/" directory of this repository is licensed under "Creative Commons: CC BY-SA 4.0 license".
-* All content that resides under the "packages/" directory of this repository, if that directory exists, is licensed under the license defined in "packages/*/LICENSE".
-* All third-party components that are integrated into our software are licensed under the original licence provided by the owner of the respective component.
-* Content outside the above directories or restrictions is available under the "AGPL 3.0" licence as defined here: https://www.gnu.org/licenses/agpl-3.0.en.html
-

README.md

@@ -19,38 +19,7 @@ Monster was built with ES6 modules and uses [import](https://developer.mozilla.o
 There is a version in the `/dist` folder that was built via [webpack](https://github.com/webpack/webpack) and  
 thus supports all browsers that are compatible with [ES5](https://caniuse.com/es5).
 
-## Build & Development
-
-```
-// create documentation
-make doc
-
-// create documentation and push to aws
-make doc-2-aws
-
-// build all packages
-make build
-
-// test all packages
-make test
-
-// build packages
-PACKAGE=monster
-make build-${PACKAGES}
-make build-browser-test-${PACKAGES}
-make test-${PACKAGES}
-make npm-publish-${PACKAGES}
-
-```
-
-to make compatibility with the older browsers [polyfill.io](https://cdn.polyfill.io/v3/url-builder/) is a good choice.
-
-
-## Packages
-
-| Package | Description                             | NPM                                                                                  |
-|:--------|:----------------------------------------|:-------------------------------------------------------------------------------------|
-| monster | Standard library with general functions | [npmjs.com/package/@schukai/monster](https://www.npmjs.com/package/@schukai/monster) |
+To make compatibility with the older browsers [polyfill.io](https://cdn.polyfill.io/v3/url-builder/) is a good choice.
 
 ## Documentation
 
@@ -77,3 +46,26 @@ Please make sure to read the Issue Reporting Checklist before opening an issue.
 
 Detailed changes for each release are documented in the corresponding CHANGELOG files.
 
+## Build & Development
+
+```
+// create documentation
+make doc
+
+// create documentation and push to aws
+make doc-2-aws
+
+// build all packages
+make build
+
+// test all packages
+make test
+
+// build packages
+PACKAGE=monster
+make build-${PACKAGES}
+make build-browser-test-${PACKAGES}
+make test-${PACKAGES}
+make npm-publish-${PACKAGES}
+
+```

carbon-config.json

-{"paddingVertical":"74px","paddingHorizontal":"56px","backgroundImage":null,"backgroundImageSelection":null,"backgroundMode":"color","backgroundColor":"rgba(239,40,44,1)","dropShadow":true,"dropShadowOffsetY":"20px","dropShadowBlurRadius":"68px","theme":"one-light","windowTheme":"boxy","language":"htmlmixed","fontFamily":"Hack","fontSize":"14px","lineHeight":"143%","windowControls":true,"widthAdjustment":true,"lineNumbers":false,"firstLineNumber":1,"exportSize":"2x","watermark":false,"squaredImage":false,"hiddenCharacters":false,"name":"Monster Version","width":680}
\ No newline at end of file