From 25168ab2f01631c0fc3a0c5d665dfe1cb7eeb4a1 Mon Sep 17 00:00:00 2001 From: Jason Prothero Date: Fri, 11 Oct 2024 12:53:21 -0700 Subject: [PATCH 1/2] Added extra clarity for the Getting Started section --- contributing/umbraco-cms/build.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/contributing/umbraco-cms/build.md b/contributing/umbraco-cms/build.md index 7b24fac940c..6df857e4f16 100644 --- a/contributing/umbraco-cms/build.md +++ b/contributing/umbraco-cms/build.md @@ -17,7 +17,9 @@ If the answer is yes, please read on. Otherwise, make sure to head on over [to t To run umbraco, we first need to initialize the client git submodule: -* Execute `git submodule update --init` to get the files into Umbraco.Web.UI.Client project +* Execute `git submodule update --init` to get the files into Umbraco.Web.UI.Client project. + * This can be executed in the root folder of your cloned repository. +* If you are going to run Umbraco for testing, execute `dotnet run` inside the \src\Umbraco.Web.UI folder. * If you are going to work on the Backoffice, you can either go to the Umbraco.Web.UI.Client folder and check out a new branch or set it up in your IDE, which will allow you to commit to each repository simultaneously: * **Rider**: Preferences -> Version Control -> Directory Mappings -> Click the '+' sign * If you get a white page delete Umbraco.Cms.StaticAssets\wwwroot\umbraco folder and run `npm ci && npm run build:for:cms` inside Umbraco.Web.UI.Client folder to clear out any leftover files from older versions. From 3764028700b7ba09f2ddcb0fb2fd4f2fb61c3ec9 Mon Sep 17 00:00:00 2001 From: Sebastiaan Janssen Date: Tue, 15 Oct 2024 09:25:54 +0200 Subject: [PATCH 2/2] Clarified paths --- contributing/umbraco-cms/build.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/contributing/umbraco-cms/build.md b/contributing/umbraco-cms/build.md index 6df857e4f16..38d5f8138e1 100644 --- a/contributing/umbraco-cms/build.md +++ b/contributing/umbraco-cms/build.md @@ -17,12 +17,12 @@ If the answer is yes, please read on. Otherwise, make sure to head on over [to t To run umbraco, we first need to initialize the client git submodule: -* Execute `git submodule update --init` to get the files into Umbraco.Web.UI.Client project. +* Execute `git submodule update --init` to get the files into `\src\Umbraco.Web.UI.Client` folder. * This can be executed in the root folder of your cloned repository. -* If you are going to run Umbraco for testing, execute `dotnet run` inside the \src\Umbraco.Web.UI folder. -* If you are going to work on the Backoffice, you can either go to the Umbraco.Web.UI.Client folder and check out a new branch or set it up in your IDE, which will allow you to commit to each repository simultaneously: +* If you are going to run Umbraco for testing, execute `dotnet run` inside the `\src\Umbraco.Web.UI` folder. +* If you are going to work on the Backoffice, you can either go to the `\src\Umbraco.Web.UI.Client` folder and check out a new branch or set it up in your IDE, which will allow you to commit to each repository simultaneously: * **Rider**: Preferences -> Version Control -> Directory Mappings -> Click the '+' sign -* If you get a white page delete Umbraco.Cms.StaticAssets\wwwroot\umbraco folder and run `npm ci && npm run build:for:cms` inside Umbraco.Web.UI.Client folder to clear out any leftover files from older versions. +* If you get a white page, delete `\src\Umbraco.Cms.StaticAssets\wwwroot\umbraco` folder and run `npm ci && npm run build:for:cms` inside the `src\Umbraco.Web.UI.Client` folder to clear out any leftover files from older versions. ### Latest version