chore: set up cookiecutter template

.adr-dir

@@ -0,0 +1 @@
+docs/adr

.editorconfig

@@ -0,0 +1,20 @@
+# Editor Configuration (http://editorconfig.org)
+root = true
+
+[*]
+charset = utf-8
+indent_style = space
+indent_size = 4
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+max_line_length = 88
+
+[*.{json,yml}]
+indent_size = 2
+
+[*.{md,rst}]
+trim_trailing_whitespace = false
+
+[Makefile]
+indent_style = tab

.gitattributes

@@ -0,0 +1 @@
+src/structurizr/_version.py export-subst

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and
+expression, level of experience, education, socio-economic status, nationality,
+personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, or to ban temporarily or permanently any
+contributor for other behaviors that they deem inappropriate, threatening,
+offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at
+[midnighter@posteo.net](mailto:midnighter@posteo.net). All complaints will be
+reviewed and investigated and will result in a response that is deemed necessary
+and appropriate to the circumstances. The project team is obligated to maintain
+confidentiality with regard to the reporter of an incident.  Further details of
+specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor
+Covenant](https://www.contributor-covenant.org), version 1.4, available at
+https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

.github/CONTRIBUTING.rst

@@ -0,0 +1,120 @@
+============
+Contributing
+============
+
+Contributions are welcome, and they are greatly appreciated! Every
+little bit helps, and credit will always be given.
+
+You can contribute in many ways:
+
+Report Bugs
+===========
+
+Report bugs at https://github.com/Midnighter/structurizr-python/issues.
+
+If you are reporting a bug, please follow the template guide lines. The more 
+detailed your report, the easier and thus faster we can help you.
+
+Fix Bugs
+========
+
+Look through the GitHub issues for bugs. Anything tagged with "bug"
+and "help wanted" is open to whoever wants to implement it.
+
+Implement Features
+==================
+
+Look through the GitHub issues for features. Anything tagged with "enhancement"
+and "help wanted" is open to whoever wants to implement it.
+
+Write Documentation
+===================
+
+structurizr-python could always use more documentation, whether as part of the
+official documentation, in docstrings, or even on the web in blog posts,
+articles, and such.
+
+Submit Feedback
+===============
+
+The best way to send feedback is to file an issue at
+https://github.com/Midnighter/structurizr-python/issues.
+
+If you are proposing a feature:
+
+* Explain in detail how it would work.
+* Keep the scope as narrow as possible, to make it easier to implement.
+* Remember that this is a volunteer-driven project, and that contributions
+  are welcome :)
+
+Get Started!
+============
+
+Ready to contribute? Here's how to set up structurizr-python for
+local development.
+
+1. Fork the https://github.com/Midnighter/structurizr-python
+   repository on GitHub.
+2. Clone your fork locally
+
+   .. code-block:: console
+   
+       git clone git@github.com:your_name_here/structurizr-python.git
+
+3. Install your local copy into a a Python virtual environment.
+   You can `read this guide to learn more
+   <https://realpython.com/python-virtual-environments-a-primer/>`_
+   about them and how to create one. Alternatively, particularly if you are a 
+   Windows or Mac user, you can also use
+   `Anaconda <https://docs.anaconda.com/anaconda/>`_. Assuming you have 
+   virtualenvwrapper installed, this is how you set up your fork for local development
+
+   .. code-block:: console
+   
+       mkvirtualenv my-env
+       cd structurizr-python/
+       pip install -e .[development]
+
+4. Create a branch for local development using the ``devel`` branch as a 
+   starting point. Use ``fix`` or ``feat`` as a prefix
+
+   .. code-block:: console
+   
+       git checkout devel
+       git checkout -b fix-name-of-your-bugfix
+
+   Now you can make your changes locally.
+
+5. When you're done making changes, apply the quality assurance tools and check 
+   that your changes pass our test suite. This is all included with tox
+
+   .. code-block:: console
+   
+       make qa
+       tox
+
+   You can run all tests in parallel using detox. To get detox, just
+   pip install it into your virtualenv.
+
+6. Commit your changes and push your branch to GitHub. Please use `semantic
+   commit messages <http://karma-runner.github.io/2.0/dev/git-commit-msg.html>`_.
+
+   .. code-block:: console
+   
+       git add .
+       git commit -m "fix: Your summary of changes"
+       git push origin fix-name-of-your-bugfix
+
+7. Open the link displayed in the message when pushing your new branch 
+   in order to submit a pull request.
+
+Pull Request Guidelines
+=======================
+
+Before you submit a pull request, check that it meets these guidelines:
+
+1. The pull request should include tests.
+2. If the pull request adds functionality, the docs should be updated. Put
+   your new functionality into a function with a docstring.
+3. The pull request should work for Python 3.6 and 3.7. This is also ensured 
+   by our Travis CI.

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,33 @@
+#### Problem description
+
+Please explain:
+* **what** you tried to achieve,
+* **how** you went about it (referring to the code sample), and
+* **why** the current behaviour is a problem and what output
+  you expected instead.
+
+#### Code Sample
+
+Create a [minimal, complete, verifiable example
+](https://stackoverflow.com/help/mcve).
+
+```python
+# Paste your code here or link to a gist.
+```
+
+```
+# If there was a crash, please include the traceback here.
+```
+
+### Context
+
+Please run the following code and paste the output inside the details
+block.
+
+```
+python -c "import structurizr;structurizr.show_versions()"
+```
+
+<details>
+
+</details>

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,4 @@
+* [ ] fix #(issue number)
+* [ ] description of feature/fix
+* [ ] tests added/passed
+* [ ] add an entry to the [next release](../CHANGELOG.rst)

.github/SUPPORT.rst

@@ -0,0 +1,6 @@
+=======
+Support
+=======
+
+* structurizr-python `gitter chat <https://gitter.im/Midnighter/structurizr-python>`_
+

.gitignore

@@ -0,0 +1,126 @@
+# Created by .ignore support plugin (hsz.mobi)
+### Python template
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+pip-wheel-metadata/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+.hypothesis/
+.pytest_cache/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+.python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# celery beat schedule file
+celerybeat-schedule
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+