Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

renamed .wiki to .md #26

Merged
merged 1 commit into from

2 participants

@d1rk

as discussed UnionOfRAD/lithium#5

@nateabele
Owner

Looks like you deleted the block on searching.

@d1rk d1rk referenced this pull request in UnionOfRAD/lithium
Merged

renamed .wiki to .md #708

@d1rk

fixed.

@nateabele nateabele merged commit b1dd56b into UnionOfRAD:master
@jails jails referenced this pull request in UnionOfRAD/manual
Merged

resubmit previous PR into restructure branch #45

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Dec 12, 2012
  1. @d1rk

    renamed .wiki to .md

    d1rk authored
This page is out of date. Refresh to see the latest.
View
25 README.md
@@ -1,5 +1,3 @@
-# Li3 Docs
-
Li3_docs is a **Lithium plugin**, NOT a Lithium app. Furthermore, by itself it is a VIEWER ONLY and contains no actual documentation other than its own.
Once installed in your existing application, however, it generates documentation from your app's docblocks in real-time, which is all accessible from http://yourapp.tld/docs/. Not only that, but it will generate documentation for your plugins, too. Including itself; so it is self-replicating in a way. In this vein, it becomes part of a series of plugins required in order to obtain various documentation volumes of interest.
@@ -16,7 +14,7 @@ So the Lithium documentation plugin (Li3 Docs) is a tool for creating automatica
For generating documentation, Li3 Docs relies on PHP documentation blocks, or _docblocks_. These docblocks can appear above classes, methods, properties, etc., and contain three things: a short description, a longer description (often including usage examples), and docblock _tags_, which are denoted by an `@` symbol, followed by a keyword. A typical docblock might look something like this:
-```php
+{{{
/**
* Contains an instance of the `Request` object with all the details of the HTTP request that
* was dispatched to the controller object. Any parameters captured in routing, such as
@@ -27,7 +25,7 @@ For generating documentation, Li3 Docs relies on PHP documentation blocks, or _d
* @var object
*/
public $request = null;
-```
+}}}
This docblock documents a class property, and contains a short description and two docblock tags. The tags to be used in a docblock vary by what is being documented. A property docblock should contain a `@var` tag that describes what type of value the property holds, while methods have a series of `@param` tags and a `@return` tag.
@@ -35,19 +33,15 @@ There are also general tags which can be added to any docblock. These include th
### Markdown syntax
-Docblock descriptions are written in Markdown format, with a few conventions. Namely, any code references or identifiers should be enclosed in backticks. This includes namespaces, classes, variable names, and keywords like `true`, `false` and `null`. Extended code examples should be written enclosed in three sets of curly braces, i.e.:
-
-```php
-{{{ // Code goes here }}}
-```
+Docblock descriptions are written in Markdown format, with a few conventions. Namely, any code references or identifiers should be enclosed in backticks. This includes namespaces, classes, variable names, and keywords like `true`, `false` and `null`. Extended code examples should be written enclosed in three sets of curly braces, i.e.: {‍{{ // Code goes here }}}.
### Code embedding
In order to improve the testability of documented code examples, and to help ensure that code and documentation stay in sync, Li3 Docs supports a special syntax that allows code from class methods to be embedded inline inside Markdown text. Consider the following:
-```php
+{{{
{{{ embed:lithium\tests\cases\core\EnvironmentTest::testSetAndGetCurrentEnvironment(1-3) }‍}}
-```
+}}}
This will embed code from the `testSetAndGetCurrentEnvironment()` method of the `Environment` test case, from line 1 through line 3 as an inline code example in the Markdown text. This way, whenever the code changes, the tests change to match it, and the documentation stays up-to-date with what's in the test.
@@ -57,11 +51,11 @@ Finally, since explanations and descriptions of code can fall out of sync with e
Once loaded into your application the plugin will enable browsing for all added libraries. In some cases it may be desired to disable browsing for certain libraries. In order to do so pass the `'index'` option in the second parameter when adding Li3 Docs:
-```php
+{{{
Libraries::add('li3_docs', array(
'index' => array('lithium', 'li3_bot')
));
-```
+}}}
### Searching
@@ -73,6 +67,7 @@ The plugin now features a symbol-based live search. Search for classes, methods
To update the search database, run the symbol harvesting task:
-```
+{{{
$ li3 harvest
-```
+}}}
+
View
2  config/docs/index.json
@@ -1,5 +1,5 @@
{
"category": "libraries",
"title": "Lithium Documentation Tool",
- "description": "The Lithium documentation tool provides automated documentation display and extraction from class API documentation and from `readme.wiki` files."
+ "description": "The Lithium documentation tool provides automated documentation display and extraction from class API documentation and from `readme.md` files."
}
View
2  controllers/ApiBrowserController.php
@@ -40,7 +40,7 @@ class ApiBrowserController extends \lithium\action\Controller {
*
* @var string
*/
- public $docFile = array('readme.wiki', 'readme.md');
+ public $docFile = array('readme.md');
protected function _init() {
parent::_init();
View
58 readme.wiki
@@ -1,58 +0,0 @@
-Li3_docs is a **Lithium plugin**, NOT a Lithium app. Furthermore, by itself it is a VIEWER ONLY and contains no actual documentation other than its own.
-
-Once installed in your existing application, however, it generates documentation from your app's docblocks in real-time, which is all accessible from http://yourapp.tld/docs/. Not only that, but it will generate documentation for your plugins, too. Including itself; so it is self-replicating in a way. In this vein, it becomes part of a series of plugins required in order to obtain various documentation volumes of interest.
-
-such as:
-
- * https://github.com/UnionOfRAD/manual
- * https://github.com/UnionOfRAD/lithium
- * https://github.com/UnionOfRAD/framework
-
-So the Lithium documentation plugin (Li3 Docs) is a tool for creating automatically browse-able documentation of your application's codebase. In addition to simple descriptions and tables of contents, Li3 Docs allows application and code to be embedded with metadata and testable code examples to provide richer and more comprehensive documentation.
-
-### Documentation structure
-
-For generating documentation, Li3 Docs relies on PHP documentation blocks, or _docblocks_. These docblocks can appear above classes, methods, properties, etc., and contain three things: a short description, a longer description (often including usage examples), and docblock _tags_, which are denoted by an `@` symbol, followed by a keyword. A typical docblock might look something like this:
-
-{{{
-/**
- * Contains an instance of the `Request` object with all the details of the HTTP request that
- * was dispatched to the controller object. Any parameters captured in routing, such as
- * controller or action name are accessible as properties of this object, i.e.
- * `$this->request->controller` or `$this->request->action`.
- *
- * @see lithium\action\Request
- * @var object
- */
-public $request = null;
-}}}
-
-This docblock documents a class property, and contains a short description and two docblock tags. The tags to be used in a docblock vary by what is being documented. A property docblock should contain a `@var` tag that describes what type of value the property holds, while methods have a series of `@param` tags and a `@return` tag.
-
-There are also general tags which can be added to any docblock. These include the `@see` tag, which allows you to link to another class, method or property, and the `@link` tag, which allows you to link to an arbitrary URL.
-
-### Markdown syntax
-
-Docblock descriptions are written in Markdown format, with a few conventions. Namely, any code references or identifiers should be enclosed in backticks. This includes namespaces, classes, variable names, and keywords like `true`, `false` and `null`. Extended code examples should be written enclosed in three sets of curly braces, i.e.: {‍{{ // Code goes here }}}.
-
-### Code embedding
-
-In order to improve the testability of documented code examples, and to help ensure that code and documentation stay in sync, Li3 Docs supports a special syntax that allows code from class methods to be embedded inline inside Markdown text. Consider the following:
-
-{{{
-{{{ embed:lithium\tests\cases\core\EnvironmentTest::testSetAndGetCurrentEnvironment(1-3) }‍}}
-}}}
-
-This will embed code from the `testSetAndGetCurrentEnvironment()` method of the `Environment` test case, from line 1 through line 3 as an inline code example in the Markdown text. This way, whenever the code changes, the tests change to match it, and the documentation stays up-to-date with what's in the test.
-
-Finally, since explanations and descriptions of code can fall out of sync with examples presented, Li3 Docs can be configured with a storage backend which retains hash values which represent the embedded code examples. When the underlying code changes, the hash values will fall out-of-sync, and corresponding documentation can be reviewed for accuracy.
-
-### Browsing
-
-Once loaded into your application the plugin will enable browsing for all added libraries. In some cases it may be desired to disable browsing for certain libraries. In order to do so pass the `'index'` option in the second parameter when adding Li3 Docs:
-
-{{{
-Libraries::add('li3_docs', array(
- 'index' => array('lithium', 'li3_bot')
-));
-}}}
Something went wrong with that request. Please try again.