htmldocs | Pre-built HTML Git documentation

Hostek has a pretty good write up on the subject over on their site - How to Encrypt or Compile ColdFusion Files.

Basically, from that article:

Using cfcompile.bat
The cfcompile.bat utility will compile all .cfm and .cfc files within a given directory into Java bytecode. This has the effect of making your source code unreadable, and it also prevents ColdFusion from having to compile your ColdFusion files on first use which provides a small performance enhancement.

More details about using cfcompile.bat can be found in ColdFusion's Documentation

Using cfencode.exe
The cfencode.exe utility will apply basic encryption to a specific file or directory. If used to encrypt a directory, it will apply encryption to ALL files in the directory which can break any JS, CSS, images, or other non-ColdFusion files.

They do also include this note at the bottom:

Note: Encrypting your site files with cfencode does not guarantee absolute security of your source code, but it does add a layer of obfuscation to help prevent unauthorized individuals from viewing the source.

The article goes on to give basic instructions on how to use each.

Adobe has this note on their site regarding cfencode:

Note: You can also use the cfencode utility, located in the cf_root/bin directory, to obscure ColdFusion pages that you distribute. Although this technique cannot prevent persistent hackers from determining the contents of your pages, it does prevent inspection of the pages. The cfencode utility is not available on OS X.

I would also add that it will be trivial for anyone familiar with ColdFusion to decode anything encoded with this utility because they also provide the decoder.

Your syntax is incorrect. I think you want to use field lists, or possibly definition lists, depending on whether or not you want the result to be visible to the reader when rendered. Try them out on https://livesphinx.herokuapp.com/.

I've been having some issues (10.11) as well with the git--html download. If you open finder and hit command + shift + G and type in /usr/local/cellar you will hopefully find your package's folder. After that find the bin folder and launch the executable file inside the bin folder (it will have the terminal icon). What it should look like (bin folder inside 1.3.5 folder)