summaryrefslogtreecommitdiffhomepage
path: root/documentation/ModulesHowTo.md
diff options
context:
space:
mode:
authorChristian Schoenebeck <christian.schoenebeck@gmail.com>2015-11-01 17:57:08 +0100
committerChristian Schoenebeck <christian.schoenebeck@gmail.com>2015-11-01 17:57:19 +0100
commit57a949e6383b4675b705d9ac812da3196638b0c5 (patch)
treea9c7210561a5b5c0035f875d2969e3d213b0695f /documentation/ModulesHowTo.md
parentfbc27d1b4840aca80e5ebc89e6261e9e99609412 (diff)
documentation/CBI.md fixed markdown formating
CBI.md: fixed markdown formating ModulesHowTo.md: fixed to make link inside CBI.md work. Signed-off-by: Christian Schoenebeck <christian.schoenebeck@gmail.com>
Diffstat (limited to 'documentation/ModulesHowTo.md')
-rw-r--r--documentation/ModulesHowTo.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/documentation/ModulesHowTo.md b/documentation/ModulesHowTo.md
index 3f70b788c5..c4dbb98205 100644
--- a/documentation/ModulesHowTo.md
+++ b/documentation/ModulesHowTo.md
@@ -101,7 +101,7 @@ Now type */cgi-bin/luci/my/new/template_' ('_[http://localhost:8080/luci/my/new/
You may notice those fancy <% %>-Tags, these are [wiki:Documentation/Templates|template markups] used by the LuCI template processor.
It is always good to include header and footer at the beginning and end of a template as those create the default design and menu.
-## CBI models
+## <a name=cbimodels></a> CBI models
The CBI is one of the uber coolest features of LuCI. It creates a formular based user interface and saves its contents to a specific UCI config file. You only have to describe the structure of the configuration file in a CBI model file and Luci does the rest of the work. This includes generating, parsing and validating a XHTML form and reading and writing the UCI file.
So let's be serious at least for this paragraph and create a real pratical example *_lucidir_/model/cbi/myapp-mymodule/netifaces.lua* with the following contents: