update a number of pages, fix backslashed underscores

Author: mpictor

_docs/Attributes_in_fedex_plus.md

@@ -1,9 +1,11 @@
 ---
+layout: docs
+permalink: 
 title: Attributes in fedex plus
 ---
 
 This comes from
-[classes\_misc.c:709](https://github.com/stepcode/stepcode/blob/master/src/fedex_plus/classes_misc.c#L709).
+[classes_misc.c:709](https://github.com/stepcode/stepcode/blob/master/src/fedex_plus/classes_misc.c#L709).
 It should be formatted such that doxygen sees it.
 
 Attributes are divided into four categories: these are not exclusive as
@@ -12,11 +14,11 @@ far as I can tell! I added defs below DAS
 -   simple explicit
 -   type shifters
     -   not DERIVEd - redefines type in ancestor
-    -   VARget\_initializer(v) returns null
+    -   VARget_initializer(v) returns null
 
 -   simple derived
-    -   DERIVEd - is calculated - VARget\_initializer(v)
-    -   returns non-zero, VARis\_derived(v) is non-zero
+    -   DERIVEd - is calculated - VARget_initializer(v)
+    -   returns non-zero, VARis_derived(v) is non-zero
 
 -   overriding
     -   includes type shifters and derived

_docs/BRL-CAD_patches.md

@@ -10,7 +10,7 @@ Cross Platform
 ctest/cdash (testing)
 ---------------------
 
--   install cmake/ctest, then run 'ctest -S run\_ctest.cmake'
+-   install cmake/ctest, then run 'ctest -S run_ctest.cmake'
 -   test submission to my.ctest.org requires creation of a file in the
     dir above the STEPcode source; read the messages from the above
     command

_docs/Code_analysis.md

@@ -33,21 +33,21 @@ application that wants to read or write STEP data.
 
 #### Tools
 
-The tools are fedex\_plus, fedex\_python, check\_express, and exppp.
+The tools are fedex_plus, fedex_python, check_express, and exppp.
 
--   **check\_express** uses libexpress (below) to check an EXPRESS
+-   **check_express** uses libexpress (below) to check an EXPRESS
     schema for errors. Formerly named **express**, it is the simplest
     possible use of libexpress.
--   **fedex\_plus** parses an EXPRESS schema using libexpress, analyzes
+-   **fedex_plus** parses an EXPRESS schema using libexpress, analyzes
     the in-memory representation of the EXPRESS, and writes
     schema-specific C++ source code that is the compiled into one of the
     aforementioned schema-specific libraries.
--   **fedex\_python** is a work in progress. It is similar to
-    fedex\_plus but writes Python code instead.
+-   **fedex_python** is a work in progress. It is similar to
+    fedex_plus but writes Python code instead.
 -   **exppp**, the EXPRESS Pretty Printer, formats EXPRESS in a way that
     is easy to read. The executable is currently not built because it is
     rarely used, but the library is still built and is used by
-    fedex\_plus and fedex\_python.
+    fedex_plus and fedex_python.
 
 #### Other libraries
 
@@ -60,7 +60,7 @@ also used at runtime~~, along with a few hashing functions in
     implementations of malloc, calloc, realloc, free, new, and delete
     that warn of improper use and record the file and line number.
 -   **libexppp** formats EXPRESS so that it is easy to read. It is used
-    to format some things that fedex\_plus and fedex\_python do not
+    to format some things that fedex_plus and fedex_python do not
     currently translate into C++ or Python, such as FUNCTIONs and RULEs.
 -   **libexpress** parses an EXPRESS schema in a file and builds a model
     of the schema in memory.

_docs/Files_and_directories.md

@@ -1,77 +1,50 @@
 ---
+layout: docs
+permalink: /docs/usage2/
 title: How to use STEPcode in an application
 ---
 
-CMake Integration
------------------
+## CMake Integration
 
--   Use **SC\_IS\_SUBBUILD** and **SC\_BUILD\_SCHEMAS**
--   **SC\_SDAI\_ADDITIONAL\_EXES\_SRCS** can be used to have SC build
+-   Use **SC_IS_SUBBUILD** and **SC_BUILD_SCHEMAS**
+-   **SC_SDAI_ADDITIONAL_EXES_SRCS** can be used to have SC build
     single-file executables (similar to p21read)
     -   this will not work for applications with more than one source
         code file or that need to link other libs.
 
-#### See also: [STEPcode CMake variables](STEPcode_CMake_variables.html)
+#### See also: [CMake variables used by STEPcode](/docs/cmake_vars/)
 
-C++ examples
-------------
+## C++ examples
 
--   [Minimal Part 21 C++
-    example](Minimal_Part_21_C++_example.html)
--   doxygen documentation of [apps using
-    STEPcode](http://stepcode.org/stepcode-use-doxygen/)
+-   [Minimal Part 21 C++ example](Minimal_Part_21_C++_example.html)
+-   doxygen documentation of [apps using STEPcode](http://stepcode.org/stepcode-use-doxygen/)
 -   [sc/src/express/test](https://github.com/stepcode/stepcode/tree/master/src/express/test/)
-    - tests executables for the express parser
+    - tests for the express parser
 -   [sc/test/cpp/](http://github.com/stepcode/stepcode/tree/master/test/cpp/)
-    - tests written in c++; these can be built when ENABLE\_TESTING is
-    set to ON, but are excluded from 'make all'
+    - tests written in c++; these can be built when ENABLE_TESTING is set to ON, but are excluded from 'make all'
 -   [sc/src/test](http://github.com/stepcode/stepcode/tree/master/src/test)
-    - tests written by NIST; all are up-to-date, but
-    [p21read](https://github.com/stepcode/stepcode/blob/master/src/test/p21read/p21read.cc#L138)
-    is the most frequently used. See the README in sc/src/test for more.
+    - tests written by NIST; all are up-to-date, but [p21read](https://github.com/stepcode/stepcode/blob/master/src/test/p21read/p21read.cc#L138) is the most frequently used. See the README in sc/src/test for more.
 -   [sc/src/clprobe-ui](http://github.com/stepcode/stepcode/tree/master/src/clprobe-ui)
-    - remnants of a UI known as dataProbe; requires the
-    [InterViews](http://www.ivtools.org/ivtools/interviews.html)
-    toolkit, which predates X windows. An attempt has been made to
-    resurrect it, but without success.
--   TODO: Example using lazy loading code. For now, see
-    [lazy\_test.cc](http://github.com/stepcode/stepcode/blob/master/src/cllazyfile/lazy_test.cc)
-    in the repo.
+    - remnants of a UI known as dataProbe; requires the [InterViews](http://www.ivtools.org/ivtools/interviews.html) toolkit, which predates X windows. An attempt has been made to resurrect it, but without success.
+-   TODO: Example using lazy loading code. For now, see [lazy_test.cc](http://github.com/stepcode/stepcode/blob/master/src/cllazyfile/lazy_test.cc) in the repo.
 
-C++ applications that are not in the GitHub repository
-------------------------------------------------------
+## C++ applications that are not in the GitHub repository
 
-The BRL-CAD
-[step-g](http://brlcad.svn.sourceforge.net/viewvc/brlcad/brlcad/trunk/src/conv/step/)
-converter, documented
-[here](http://stepcode.org/stepcode-use-doxygen/step-g_8cpp.html) (Note
-- currently, the BRL-CAD version of STEPcode differs slightly from the
-version on GitHub)
+The BRL-CAD [step-g](http://brlcad.svn.sourceforge.net/viewvc/brlcad/brlcad/trunk/src/conv/step/) converter, documented [here](http://stepcode.org/stepcode-use-doxygen/step-g_8cpp.html) (Note - currently, the BRL-CAD version of STEPcode differs slightly from the version on GitHub)
 
 Laurent Bauer's [SCView](https://github.com/LaurentBauer/SCView/wiki)
 
-Python
-------
+## Python
 
--   [Python
-    Generator](http://github.com/stepcode/stepcode/wiki/python-generator)
+-   [Python Generator](http://github.com/stepcode/stepcode/wiki/python-generator)
 
-TODO
-----
+## TODO
 
--   describe use of [lazy loading
-    code](http://github.com/stepcode/stepcode/blob/master/src/cllazyfile/lazyInstMgr.h)
--   create a page with a small Part 21 file, with description of format
-    and links to relevant classes - SDAI\_Application\_instance,
-    STEPcomplex, generated code (?)
--   run doxygen on parts of STEPcode (libexpress + exppp + fedex\_plus,
-    fedex\_python, cllazyfile, cleditor, clstepcore + cldai + clutils +
-    base ) **and automate doxygen with a script**
+-   describe use of [lazy loading code](http://github.com/stepcode/stepcode/blob/master/src/cllazyfile/lazyInstMgr.h)
+-   create a page with a small Part 21 file, with description of format and links to relevant classes - SDAI_Application_instance, STEPcomplex, generated code (?)
+-   run doxygen on parts of STEPcode (libexpress + exppp + fedex_plus, fedex_python, cllazyfile, cleditor, clstepcore + cldai + clutils + base ) **and automate doxygen with a script**
 
-See also
---------
+## See also
 
--   [Building STEPcode](Building_STEPcode.html)
--   [How to test with CTest](How_to_test_with_CTest.html)
-
-[Category:Code discussion](Category:Code_discussion.html)
+-   [Building STEPcode](/docs/building/)
+-   [Testing](/docs/testing)

_docs/How_to_use_STEPcode_in_an_application.md

@@ -78,7 +78,7 @@ struct Statement_ {
 };
 `
 
-### Case\_Statement
+### Case_Statement
 
 `
 struct Case_Statement_ {
@@ -87,7 +87,7 @@ struct Case_Statement_ {
 };
 `
 
-### Compound\_Statement
+### Compound_Statement
 
 `
 struct Compound_Statement_ {
@@ -116,7 +116,7 @@ struct Loop_ {
 };
 `
 
-### Procedure\_Call
+### Procedure_Call
 
 `
 struct Procedure_Call_ {
@@ -125,7 +125,7 @@ struct Procedure_Call_ {
 };
 `
 
-### Return\_Statement
+### Return_Statement
 
 `
 struct Return_Statement_ {
@@ -281,7 +281,7 @@ struct Procedure_ {
 Others
 ------
 
-### Case\_Item
+### Case_Item
 
 ``
 
@@ -352,7 +352,7 @@ struct Expression_ {
 };
 `
 
-### Linked\_List
+### Linked_List
 
 ``
 

_docs/Libexpress_structs.md

@@ -3,7 +3,7 @@ title: List of projects
 ---
 
 |---|
-|\_\_TOC\_\_|
+|__TOC__|
 
 STEPcode is participating in GSoC again!
 ========================================

_docs/List_of_projects.md

@@ -1,11 +1,13 @@
 ---
+layout: docs
+permalink: 
 title: List of tasks
 ---
 
 On the wiki
 -----------
 
--   Document the data structures in *libexpress*, *fedex\_plus*
+-   Document the data structures in *libexpress*, *fedex_plus*
 -   Copy content from github wiki?
 -   More external links
 -   Logo, background

_docs/List_of_tasks.md

@@ -15,8 +15,8 @@ Important Classes
     file)
 -   [STEPfile](http://stepcode.org/doxygen/class_s_t_e_pfile.html)
     (takes care of reading and writing Part 21 files, and creates an
-    SDAI\_Application\_instance for every instance read)
--   [SDAI\_Application\_instance](http://stepcode.org/doxygen/class_s_d_a_i___application__instance.html)
+    SDAI_Application_instance for every instance read)
+-   [SDAI_Application_instance](http://stepcode.org/doxygen/class_s_d_a_i___application__instance.html)
     (the base class for every type of instance that STEP deals with)
 
 Code
@@ -90,11 +90,11 @@ Linking
 Your executable will need to link to various libraries, likely including
 a generated library, specific to the schema you are interested in. Once
 generated, this lib can be found in build/lib with a prefix of
-libsdai\_.
+libsdai_.
 
 It will also need to link with cldai, cleditor, clstepcore, and clutils - all found in build/lib.
 
-If you get stuck, consider examining the compile/link commands used for one of the p21read executables. This can be done with **make VERBOSE=1\_**:
+If you get stuck, consider examining the compile/link commands used for one of the p21read executables. This can be done with **make VERBOSE=1_**:
 
 `make VERBOSE=1 p21read_sdai_ap214e3`
 

_docs/Minimal_Part_21_C++_example.md

@@ -4,9 +4,6 @@ title: Welcome
 permalink: /docs/home/
 ---
 
-STEPcode • Data Exchange with the technologies of ISO 10303
-
-# Welcome
 ----
 
 The **STEPcode** project is a collection of open source libraries, tools, and resources that revolve around the technologies of [ISO 10303](http://en.wikipedia.org/w/index.php?title=ISO_10303), a.k.a. STEP, the **ST**andard for the **E**xchange of **P**roduct model data.
@@ -19,32 +16,21 @@ STEPcode provides a cross-platform (Linux, OSX, **and** Windows) implementation
 -   a library that allows STEP Part 21 files to be read and written
 -   various utilities, test routines, and test schemas
 
-  
+
 The [BSD license](http://github.com/stepcode/stepcode/blob/master/COPYING) allows commercial use. In addition, STEPcode is used in other open source projects such as [BRL-CAD](http://www.brl-cad.org) and [SCView](http://github.com/LaurentBauer/SCView).  
-  
+
 STEPcode traces its roots to the NIST STEP Class Library (SCL) which was developed between ~1987 and 1998.
 
 See also: [History](History.html), [List of external resources](List_of_external_resources.html), [List of OSS or free STEP programs](List_of_OSS_or_free_STEP_programs.html)
 
-### GSoC 2014
-
-We're participating again!
-
-See the [Checklist](http://brlcad.org/wiki/Summer_of_Code/Checklist) and the BRL-CAD [project ideas](http://brlcad.org/wiki/Google_Summer_of_Code/Project_Ideas). If those ideas don't interest you, you can also look at the longer [list of projects](List_of_projects.html) on this wiki.
-
 ### Quick Start
 
--   See the [getting started](Getting_started.html) page
+-   See the [basic usage](/docs/usage) page
 
 ### Communication
 
--   **[STEPcode
-    mailing list](https://groups.google.com/forum/#!forum/scl-dev)** on google groups (new users are moderated to
-    discourage spam)
--   **#stepcode** on freenode - use an IRC client or [your
-    browser](http://webchat.freenode.net/?channels=stepcode). There is
-    also a [log](http://ibot.rikers.org/%23stepcode/) thanks to Tim
-    Rikers.
+-   **[STEPcode mailing list](https://groups.google.com/forum/#!forum/scl-dev)** on google groups (new users are moderated to discourage spam)
+-   **#stepcode** on freenode - use an IRC client or [your browser](http://webchat.freenode.net/?channels=stepcode). There is also a [log](http://ibot.rikers.org/%23stepcode/) thanks to Tim Rikers.
 
 STEP & Other Standards
 ----------------------