Merge remote-tracking branch 'origin/main' into feature/theme-service

src/Umbraco.Web.UI.Client/.github/CONTRIBUTING.md

@@ -13,15 +13,12 @@ Here is the LIT documentation and playground: [https://lit.dev](https://lit.dev)
 
 ### What is the process of contribution?
 
-* Umbraco HQ owns the Management API on the backend
-* Features can be worked on in the frontend when there is an API, or otherwise, if no API is required
-* A contribution should be made in a fork of the backoffice repository
-* Once a contribution is ready, a pull request should be made towards the backoffice repository, where HQ will assign a reviewer
-* A pull request should always indicate what part of a feature it tries to solve, i.e. which labels can be removed from the issue on the projects board
-
-### How to work with Github Projects
-
-TBD
+- Read the [README](README.md) to learn how to get the project up and running
+- Find an issue marked as [community/up-for-grabs](https://github.com/umbraco/Umbraco.CMS.Backoffice/issues?q=is%3Aissue+is%3Aopen+label%3Acommunity%2Fup-for-grabs) - note that some are also marked [good first issue](https://github.com/umbraco/Umbraco.CMS.Backoffice/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) which indicates they are simple to get started on
+- Umbraco HQ owns the Management API on the backend, so features can be worked on in the frontend only when there is an API, or otherwise, if no API is required
+- A contribution should be made in a fork of the repository
+- Once a contribution is ready, a pull request should be made towards this repository and HQ will assign a reviewer
+- A pull request should always indicate what part of a feature it tries to solve, i.e. does it close the targeted issue (if any) or does the developer expect Umbraco HQ to take over
 
 ## Contributing in general terms
 

src/Umbraco.Web.UI.Client/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

src/Umbraco.Web.UI.Client/.github/README.md

@@ -39,3 +39,7 @@ See the Main branch in action here as an [Azure Static Web App](https://ashy-bay
 ### Storybook
 
 Storybook is also being built and deployed automatically on the Main branch, including a preview URL on each pull request. See it in action on this [Azure Static Web App](https://ambitious-stone-0033b3603.1.azurestaticapps.net/).
+
+## Contributing
+
+We accept contributions to this project. However be aware that we are mainly working on a private backlog, so not everyone will be immediately obvious. If you want to get started on contributing, please read the [contribute space](https://github.com/umbraco/Umbraco.CMS.Backoffice/contribute) where you will be able to find the guidelines on how to contribute as well as a list of good first issues.

src/Umbraco.Web.UI.Client/.github/pull_request_template

@@ -0,0 +1,30 @@
+<!--- Provide a general summary of your changes in the Title above -->
+
+## Description
+
+<!--- Describe the changes in detail -->
+
+## Types of changes
+
+<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
+
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to change)
+- [ ] Chore (minor updates related to the tooling or maintenance of the repository, does not impact compiled assets)
+
+## Motivation and context
+
+<!--- Why is this change required? What problem does it solve? -->
+
+## How to test?
+
+## Screenshots (if appropriate)
+
+## Checklist
+
+<!--- Go over all the following points, and put an `x` in all the boxes that apply.  If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
+
+- [ ] If my change requires a change to the documentation, I have updated the documentation in this pull request.
+- [ ] I have read the **[CONTRIBUTING](<(https://github.com/umbraco/Umbraco.CMS.Backoffice/blob/main/.github/CONTRIBUTING.md)>)** document.
+- [ ] I have added tests to cover my changes.

src/Umbraco.Web.UI.Client/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2023 Umbraco HQ
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

src/Umbraco.Web.UI.Client/src/backoffice/users/current-user/current-user.store.ts

@@ -1,11 +1,12 @@
+import { umbUsersData } from '../../../core/mocks/data/users.data';
 import { umbracoPath } from '@umbraco-cms/utils';
 import type { UserDetails } from '@umbraco-cms/models';
 import { UmbContextToken } from '@umbraco-cms/context-api';
 import { ObjectState } from '@umbraco-cms/observable-api';
 
 export class UmbCurrentUserStore {
-
-	private _currentUser = new ObjectState<UserDetails | undefined>(undefined);
+	//TODO: Temp solution to get a current user. Replace when we have a real user service
+	private _currentUser = new ObjectState<UserDetails | undefined>(umbUsersData.getAll()[0]);
 	public readonly currentUser = this._currentUser.asObservable();
 
 	/**