open-source-umbraco-cloud

I have an Umbraco (16) Cloud site running at https://opensourcecloud.lotte.dev. Or least I do for now, I won't keep this site running for ever!

I'm using this public GitHub repository as the "working" directory for that project: all development on the site should be done here, not committed directly to the Cloud git repo. There's a GitHub Action that gets everything it needs from GitHub Secrets to push to Cloud and update the live site!

I've written this blog post explaining the background to this project and it's limitations.

If you want to try this on your own Umbraco Cloud site, then follow the instructions in Setup.md.

But first we'd love people to try running the site locally and contributing back - see the steps below. Would a workflow like this enable the community to contribute to the new Umbraco Community site that we're currently building on Cloud?

Working Locally

1. Fork this repository
2. Clone locally
3. Open OpenSourceTest.sln in Rider|Visual Studio and start the website project
4. In the browser click the Open Umbraco without restore link
5. Log in using community@umbraco.com and community!
6. Settings section > Deploy dashboard > press the Update Umbraco schema from data files button
7. Content section > Click ... top-left > select the Import option
8. Click to upload and navigate to the content-import folder off root
9. Import each file separately working in alphabetical (i.e. date) order:
   1. Leave all options ticked and press Import
   2. If it complains about signatures, try clearing the signatures in Settings section > Deploy dashboard > press the Clear Signatures button
10. Confirm that now have a working home page at https://localhost:44390

Contributing Back

I've raised issues for specific things I'd like people to test. But you're welcome to try whatever you like to have a go at the workflow contribution yourself.

In your fork, work in a new branch and a raise a pull request targetting the default branch of develop.

If you're creating new Document Types, Templates or Data Types you should see a corresponding .uda file for each item in your list of changes to commit. Make sure you commit those!

If you have new/updated content in the content tree that would be useful to share with others to review/test your changes, then find the content node in the Content section and:

1. Click the three dots ...
2. Select Export
3. Tick Include all items below, Include content dependencies, and Include content file dependencies. Do not tick the schema-related options as these you should have already committed.
4. Download the resulting zip file and save in the content-import folder using the naming convention of YYYYMMDD-nodename.zip
5. Commit this zip file and create your pull request!

If you have issues, or any thoughts in general on this set up, please let me know!

SuperTak 😀