The source for developer.bigfix.com.
The easiest way to contribute is to edit the markdown files in the site/pages folder.
To preview the site, install both Vagrant and VirtualBox.
Start the virtual machine and build the site by running this command inside the
developer.bigfix.com directory:
$ vagrant up
When that command finishes, the site will be available at localhost:4000.
If you change something and want to preview the change, navigate to the build page at localhost:4000/build, and click the "Build" button.
Alternatively, you can ssh to the machine with:
$ vagrant ssh
Then build the site with:
$ make
The documentation lives in site/pages. Each directory inside the site/pages directory corresponds to a section of the site. For example, all action script documentation is in site/pages/action-script.
Each .md or .html file within site/pages will be rendered and output in the corresponding location in the site. For example, the documentation for wait is at site/pages/action-script/reference/execution/wait.md.
The only exception to that rule is the relevance reference. The pages in the reference are built from site/pages/relevance/_reference/docs in a completely different way. This is because the documentation of each relevance inspector can appear in multiple places. For example, the bit <integer> inspector appears on the bit set page, on the integer page, and also in the search results for "bit set".
To edit the documentation for a relevance inspector, edit the file in the docs directory that contains the inspector's documentation. You easily find the right place to edit by using the source link shown on the site next to every inspector.
The navigation that's displayed in the side bar is defined by the nav property in a defaults.yml file. For example, the navigation for action script is at site/pages/action-script/defaults.yml. It should be possible to generate the side bar automatically as part of the build. This is just something that hasn't been done yet.
The renderSideNav function inside site/build/lib/renderer.js determines the right way to display the page navigation for every page.
The navigation that's shown at the top of the site is part of the page template at site/templates/page.html. The build knows what section every page lives in by the section variable in the defaults.yml file.
The build is defined in the Makefile. The Makefile figures out what needs to be done to build the site, and typically this means that it will invoke site/build render the pages of the site.
The site/build script knows how to render every page in the site. This typically means that it reads the front-matter of a file, combines that with one or more defaults.yml files, and renders a nunjucks template defined in site/templates.
Currently the site can only be deployed by Brian Green. The actual deploy process uses a git post-receive hook.
If the set of relevance inspectors changes, then some work needs to be done to update the site to include the new information. First, follow the instructions in tools/parse-language-reports to import the new relevance information.
Next, try to run a build. If the documentation for any inspectors is missing, you'll see something like:
No documentation found for type: bes webui app
No documentation found for property: <bes webui app> = <bes webui app> : boolean
No documentation found for property: globally allowed flag of <bes webui app> : boolean
No documentation found for property: name of <bes webui app> : string
No documentation found for property: set of <bes webui app> : bes webui app set
No documentation found for property: unique value of <bes webui app> : bes webui app with multiplicity
/home/vagrant/staging/build/relevance-reference/index.js:62
throw new Error('Documentation is incomplete');
^
Error: Documentation is incomplete
To fix this, you need to run the the build script with an argument for it to create stubs for the missing documentation. To do this, go to the site/build directory and run:
$ npm install
$ node . --create-missing ..
This will create stubs for any missing inspectors. Then, try another build. If this build fails, you'll probably see an error like:
Error: Type bes webui app is missing from the relevance reference
This means that you need to update the site/pages/relevance/_reference/index.html file to list the missing inspector type.