DocBox reads component metadata and structured comments and outputs documentation in an HTML, JSON, or UML (diagram) format.

SYSTEM REQUIREMENTS

• Lucee 5+

• Adobe ColdFusion 2018+

Versioning

DocBox is maintained under the Semantic Versioning guidelines as much as possible. Releases will be numbered in the following format:

<major>.<minor>.<patch>

And constructed with the following guidelines:

• Breaking backward compatibility bumps the major (and resets the minor and patch)

• New additions without breaking backward compatibility bumps the minor (and resets the patch)

• Bug fixes and misc changes bumps the patch

License

Apache 2 License: http://www.apache.org/licenses/LICENSE-2.0​

Important Links

• Code: https://github.com/ortus-solutions/docbox​

• Issues: https://ortussolutions.atlassian.net/jira/software/c/projects/DOCBOX/issues/

• Community: https://community.ortussolutions.com/

Professional Open Source

DocBox is professional open source software backed by Ortus Solutions, Corp offering services like:

• Custom Development

• Professional Support & Mentoring

• Training

• Server Tuning

• Security Hardening

• Code Reviews

• Much More

HONOR GOES TO GOD ABOVE ALL

Because of His grace, this project exists. If you don't like this, don't read it; it's not for you.

"Therefore being justified by faith, we have peace with God through our Lord Jesus Christ: By whom also we have access by faith into this grace wherein we stand, and rejoice in hope of the glory of God." Romans 5:5

In this section, you will find the release notes for each version we release under this major version. If you are looking for the release notes of previous major versions, use the version switcher at the top left of this documentation book. Here is a breakdown of our major version releases.

Version 4.0

This major bump was to deprecate some CFML engines

Version 3.0

Added a JSON strategy in preparation for multiple output strategies we will support. Updated build processes and a new outlook for the future of the project.

Version 2.0

The migration from ColdDoc into DocBox.

Added

• Adobe 2023 Testing and Support

• New Github Actions

• New supporting files

• New build/Docs.cfc task for building the documentation using itself, before we where getting away with it because there was a previous DocBox version. Now we need to build the docs with the current version of DocBox.

Fixed

• Build Versions and changelog

• Removal of box.zip in root from old scripts

BREAKING

• Dropped support for Adobe 2016. Adobe doesn't support ACF 16 anymore, so neither do we.

NEW

• Added support for Adobe 2021

• Added support for @myCustomTag custom docblock tags on methods. (Already supported on components and properties, but missing on methods).

• Added GitHub Actions CI for automated testing, format checking, releases and more

FIX

• Fixes support for Adobe 2018. (Mainly in the CommandBox strategy.)

There are several ways you can help in the development of DocBox!

• Send a pull request

• Submit a bug or feature request to our Jira issue tracker

• Write a test

Send a Pull Request

• Fork DocBox or the DocBox documentation repo

• Clone the repository fork to your machine - git clone git@github.com:ME/DocBox.git

• Create a feature/ or patch/ branch: git checkout -b patch/syntax-error-in-html-output

• Make your changes, commit as normal, and use git push to sync your commits to Github.

• Please target all PRs at the development branch.

Testing DocBox

DocBox has a suite of Testbox specs validating that it works as expected. New features and bug fix PRs should (ideally) contain accompanying tests. Here's how to do that via CommandBox:

1. After cloning the repo, run box install to install development dependencies

2. Run box start to boot a test server

3. Run box testbox run to run the suite of DocBox tests.

4. Edit test specs in tests/specs as necessary, and run box testbox run again to validate tests pass.