aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRafael G. Martins <rafael@rafaelmartins.eng.br>2015-04-19 16:30:16 -0300
committerRafael G. Martins <rafael@rafaelmartins.eng.br>2015-04-19 16:30:16 -0300
commitd5ae7feec228e88f2c728a1fec2d331c88789a1b (patch)
tree169768352b327e6b77fffd40018ecf39ae2fbd90
parent386f06e161cd8399db6bb715a486ccf788f71d9d (diff)
downloadblogc-d5ae7feec228e88f2c728a1fec2d331c88789a1b.tar.gz
blogc-d5ae7feec228e88f2c728a1fec2d331c88789a1b.tar.bz2
blogc-d5ae7feec228e88f2c728a1fec2d331c88789a1b.zip
fixed design notes wrt content formatting
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index 642f01a..1fe0295 100644
--- a/README.md
+++ b/README.md
@@ -30,7 +30,7 @@ Variables are not available in ``multiple_sources_once`` blocks, because it is n
As the compiler is output-agnostic, Atom feeds and sitemaps should be generated using templates as well.
-The content defined in source files must be written as pre-formatted text. Make sure to enclose the content with ``<pre>`` and ``</pre>`` tags in your templates.
+The content won't touch the content. If the user write pre-formatted text it will stay formatted, and the user may want to enclose the ``{{ CONTENT }}`` statement with ``<pre>`` and ``</pre>`` tags in the templates. For more flexibility, the user can even write raw HTML in the source content.
The compiler is designed to be easily used with any POSIX-compatible implementation of ``make``.