Sure. No worries and thanks for your reply!
I’m still relatively new to Umbraco so perhaps everything I’ll need to do can be extended from the existing API. At this point I can’t predict features we’ll need in the future, as we have many clients with several needs. One example I can think of is having a new Backoffice page/section that ties in with our internal systems. Another one would be the removal of a feature on a Backoffice page because of a security risk (hypothetically). Our code is often audited, and if we’re recommended a fix, sometimes we have to comply.
The setup I have in place now is this:
My Website, built from scratch through your README:
dotnet new install Umbraco.Templates
dotnet new umbraco --name MyProject
cd MyProject
dotnet run
I’ve customized this application (it generated) through the Backoffice and added a few view templates, and extended by adding a controller that acts as an API that exposes some data. Pretty basic stuff I think.
So now, if I want to modify the core, I have a Powershell scripts that makes nuget packages from all the source and then builds my website by reloading the packages I’ve updated (built) from source.
Does this flow make sense? Is this the best “typical” way? What do you think?
Thanks again!