From cb292336e0d1e8a75c49015369bf1a6740d1b619 Mon Sep 17 00:00:00 2001 From: Olli Tietäväinen Date: Thu, 10 Aug 2017 11:09:22 +0300 Subject: Clarify theme compilation instructions (#9685) Paragraph about existing `styles.css` file needed a bit of rephrasing. --- documentation/themes/themes-compiling.asciidoc | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'documentation/themes') diff --git a/documentation/themes/themes-compiling.asciidoc b/documentation/themes/themes-compiling.asciidoc index 97f2d9b317..83db89aafa 100644 --- a/documentation/themes/themes-compiling.asciidoc +++ b/documentation/themes/themes-compiling.asciidoc @@ -29,8 +29,10 @@ all its dependencies to be in the class path of the servlet. At least for production, you must compile the theme to CSS, as described next. NOTE: If the on-the-fly compilation does not seem to work, ensure that your build script has not generated a pre-compiled CSS file. -If [filename]#styles.css# file is found the servlet, the compilation is skipped. -Delete such an existing [filename]#styles.css# file and disable theme compilation temporarily. +If a [filename]#styles.css# file is found by the servlet, the compilation is skipped. +Disable theme compilation in your local development environment and delete the existing +[filename]#styles.css# file to enable on-the-fly compilation. Note that +theme compilation should not be disabled for production builds. [[themes.compiling.eclipse]] == Compiling in Eclipse -- cgit v1.2.3