# documentation, tests, makecsl

**URL:** <https://discourse.citationstyles.org/t/documentation-tests-makecsl/642>\
**Category:** CSL Development\
**Created:** [May 24, 2009, 5:08pm UTC](https://discourse.citationstyles.org/t/documentation-tests-makecsl/642 "2009-05-24T17:08:37Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bruce\_D\_Arcus1](https://avatars.discourse-cdn.com/v4/letter/b/4bbf92/32.png) [@Bruce\_D\_Arcus1](https://discourse.citationstyles.org/u/Bruce_D_Arcus1)\
**Post date:** [May 24, 2009, 5:08pm UTC](https://discourse.citationstyles.org/t/documentation-tests-makecsl/642/1 "2009-05-24T17:08:37Z")

</div>

Some interesting ideas percolating in this thread …

[http://forums.zotero.org/discussion/7151/quick-start-guide-for-csl/](http://forums.zotero.org/discussion/7151/quick-start-guide-for-csl/)

… about having a positive feedback loop between the test suite,  
documentation, and makecsl.

Given the licensing discussion as well, I guess I’m wondering about a  
"master.csl" style file that consists only of macros, and then some  
way to integrate that into the test suite. Perhaps master.csl is in  
fact created from the test suite?

Bruce