Authoring content
+ +Please select one of the topic in this section:
+ + + +diff --git a/Authoringcontent.htm b/Authoringcontent.htm new file mode 100644 index 0000000..301393f --- /dev/null +++ b/Authoringcontent.htm @@ -0,0 +1,107 @@ + + + + + +
+ + + + + block
+```
+
+##Linking
+`Docnet` doesn't transform links. This means that any link to any document in your documentation has to use the url it will get in the destination folder. Example: you want to link to the file `How to\AddEntity.md` from a page. In the result site this should be the link `How%20to/AddEntity.htm`, which you should specify in your markdown. In the future it might be `docnet` will be updated with link transformation, at the moment it doesn't convert any links besides the usual markdown ones. The markdown parser also doesn't allow spaces to be present in the urls. If you need a space in the url, escape it with `%20`.
\ No newline at end of file
diff --git a/MarkdownSource/search.md b/MarkdownSource/search.md
new file mode 100644
index 0000000..d56a4ea
--- /dev/null
+++ b/MarkdownSource/search.md
@@ -0,0 +1,6 @@
+Search
+======
+
+`Docnet` will generate a search_data.json file in the root of the destination folder which is used with the javascript based search. It's a simple text search which can locate pages based on the word/sentence specified and will list them in first come first served order. For general purposes of locating a general piece of documentation regarding a topic it's good enough.
+
+*NOTE*: Search locally on a file:/// served site won't work in Chrome, due to cross-origin protection because the search loads the search index and a template from disk in javascript. Either use Firefox or use the site with a server.
diff --git a/MarkdownSource/themes.md b/MarkdownSource/themes.md
new file mode 100644
index 0000000..a39d5ff
--- /dev/null
+++ b/MarkdownSource/themes.md
@@ -0,0 +1,27 @@
+Themes
+======
+
+`Docnet` uses themes to produce output in a certain form. A theme is a folder within the `Themes` folder which contains a `PageTemplate.htm` file and a `Destination` folder which contains zero or more folders and files which have to be copied to the `Destination` folder specified in the `docnet.json` file.
+
+## Themes folder
+`Docnet` expects the `Themes` folder to be located in the folder where the executable is started from. This means that if you build `Docnet` from source, you have to manually copy the Themes folder to the folder your binary is located. To make development easier, you could create a `junction` in the bin\debug or bin\release folder to the Themes folder in the source repository, using `mklink` on a windows command prompt.
+
+## Default theme
+The default theme is called `Default` and is chosen if no theme has been specified in the [docnet.json](docnetjson.htm) file. It is based on the theme from ReadTheDocs, and is created from the one shipped with MkDocs.
+
+## PageTemplate.htm
+The `PageTemplate.htm` file is a simple HTML file, located in each `theme` folder, which is used as the template for all generated `.htm` files. You can place whatever you like in there, including references to css/js files, headers, footers etc. DocNet however expects a couple of *markers* which are replaced with the data created from the markdown files. These markers are described below. The markers have to be specified as-is.
+
+* `{{Name}}`. This is replaced with the value specified in `Name` in the `docnet.json` file.
+* `{{Content}}`. This is replaced with the HTML generated from the markdown file.
+* `{{ToC}}`. This is replaced with a `