From 1d114f99ddacd153ac3363bcf9f99ad92a0b3c61 Mon Sep 17 00:00:00 2001 From: karthik-ziffity Date: Tue, 3 Mar 2020 15:38:59 +0530 Subject: [PATCH 1/2] Added grunt exec and watch commands once grunt is setup --- src/guides/v2.3/frontend-dev-guide/tools/using_grunt.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/src/guides/v2.3/frontend-dev-guide/tools/using_grunt.md b/src/guides/v2.3/frontend-dev-guide/tools/using_grunt.md index e2d6d1dd85e..b1125c7b3d7 100644 --- a/src/guides/v2.3/frontend-dev-guide/tools/using_grunt.md +++ b/src/guides/v2.3/frontend-dev-guide/tools/using_grunt.md @@ -77,6 +77,11 @@ Where the following notation is used: - ``: specified in the `code_subtag` format, for example `en_US`. Only one locale can be specified here. To debug the theme with another locale, create one more theme declaration, having specified another value for `language`. - ``: path to the root source file, relative to the `app/design/frontend///web` directory. You need to specify all [root source files of the theme]({{ page.baseurl }}/frontend-dev-guide/css-topics/css-preprocess.html#css_preprocess_terms). If your theme [inherits] from a certain theme, and does not contain its own root source files, specify the root source files of the parent theme. +Once these all are set right you can run grunt to watch your changes. + +- Run `grunt exec:` from the root directory to republish the symlinks +- Run `grunt watch:`, so that grunt will watch for each and every changes you make. + ## Using custom Grunt configuration files There are several ways to declare a custom configuration file. From 280f35bb44fb22c8d7f2445ce15879943b598b44 Mon Sep 17 00:00:00 2001 From: Donald Booth Date: Tue, 3 Mar 2020 08:52:53 -0600 Subject: [PATCH 2/2] Small grammar update --- src/guides/v2.3/frontend-dev-guide/tools/using_grunt.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/guides/v2.3/frontend-dev-guide/tools/using_grunt.md b/src/guides/v2.3/frontend-dev-guide/tools/using_grunt.md index b1125c7b3d7..3b6250ed427 100644 --- a/src/guides/v2.3/frontend-dev-guide/tools/using_grunt.md +++ b/src/guides/v2.3/frontend-dev-guide/tools/using_grunt.md @@ -77,9 +77,9 @@ Where the following notation is used: - ``: specified in the `code_subtag` format, for example `en_US`. Only one locale can be specified here. To debug the theme with another locale, create one more theme declaration, having specified another value for `language`. - ``: path to the root source file, relative to the `app/design/frontend///web` directory. You need to specify all [root source files of the theme]({{ page.baseurl }}/frontend-dev-guide/css-topics/css-preprocess.html#css_preprocess_terms). If your theme [inherits] from a certain theme, and does not contain its own root source files, specify the root source files of the parent theme. -Once these all are set right you can run grunt to watch your changes. +Once these are set correctly, run grunt to watch your changes. -- Run `grunt exec:` from the root directory to republish the symlinks +- Run `grunt exec:` from the root directory to republish the symlinks. - Run `grunt watch:`, so that grunt will watch for each and every changes you make. ## Using custom Grunt configuration files