Moved instructions from the SASS file to "contributinng/css.rst"

Author: LittleJ

admin/css/debug-toolbar/toolbar.scss

@@ -8,15 +8,6 @@
  */
 
 
-// GUIDE TO GENERATE THE CSS FILE
-// ========================================================================== */
-
-// 1. Open the Terminal
-// 2. Install SASS: https://sass-lang.com/install
-// 3. Go to the SASS folder: "cd system/Debug/Toolbar/Views/SASS"
-// 4. Generate the CSS file: "sass --no-cache --scss --sourcemap=none toolbar.scss ../toolbar.css"
-
-
 // IMPORTS
 // ========================================================================== */
 

contributing/README.rst

@@ -5,6 +5,7 @@ Contributing to CodeIgniter
 - `Contribution guidelines <./guidelines.rst>`_
 - `Contribution workflow <./workflow.rst>`_
 - `Contribution signing <./signing.rst>`_
+- `Contribution CSS <./css.rst>`_
 - `Framework internals <./internals.rst>`_
 - `CodeIgniter documentation <./documentation.rst>`_
 - `PHP Style Guide <./styleguide.rst>`_
@@ -54,7 +55,7 @@ If you've found a critical vulnerability, we'd be happy to credit you in our
 Tips for a Good Issue Report
 ****************************
 
-Use a descriptive subject line (eg parser library chokes on commas) rather than 
+Use a descriptive subject line (eg parser library chokes on commas) rather than
 a vague one (eg. your code broke).
 
 Address a single issue in a report.
@@ -65,13 +66,13 @@ Explain what you expected to happen, and what did happen.
 Include error messages and stacktrace, if any.
 
 Include short code segments if they help to explain.
-Use a pastebin or dropbox facility to include longer segments of code or 
+Use a pastebin or dropbox facility to include longer segments of code or
 screenshots - do not include them in the issue report itself.
 This means setting a reasonable expiry for those, until the issue is resolved or closed.
 
 If you know how to fix the issue, you can do so in your own fork & branch, and submit a pull request.
 The issue report information above should be part of that.
 
 If your issue report can describe the steps to reproduce the problem, that is great.
-If you can include a unit test that reproduces the problem, that is even better, 
+If you can include a unit test that reproduces the problem, that is even better,
 as it gives whoever is fixing it a clearer target!

contributing/css.rst

@@ -0,0 +1,21 @@
+================
+Contribution CSS
+================
+
+CodeIgniter uses SASS to generate the debug toolbar's CSS. Therefore, you
+will need to install it first. You can find further instructions on the
+official website: https://sass-lang.com/install
+
+Compile SASS files
+==================
+
+Open your terminal, and navigate to CodeIgniter's root folder. To generate
+the CSS file, use the following command: ``sass --no-cache --sourcemap=none admin/css/debug-toolbar/toolbar.scss system/Debug/Toolbar/Views/toolbar.css``
+
+Details:
+- ``--no-cache`` is a parameter defined to disable SASS cache, this prevents
+  a "cache" folder from being created
+- ``--sourcemap=none`` is a parameter which prevents soucemap files from
+  being generated
+- ``admin/css/debug-toolbar/toolbar.scss`` is the SASS source
+- ``system/Debug/Toolbar/Views/toolbar.css`` is he CSS destination