Getting Started with Umbraco Heartcore
In this section you can find articles around managing your Umbraco Heartcore project as well as articles helping you getting to know the platforms used to work with Umbraco Heartcore.
A step-by-step guide on how to setup and build a small and basic Umbraco Heartcore project. This is a great place to start if you are new to Umbraco, as it will explain some of the default concepts and you will learn how to create content from scratch.
In this article you can read all about the features that is available on your Umbraco Heartcore project from the Umbraco Cloud Portal. The article will go through the Settings menu and how to get to the backoffice.
Depending on the plan your Heartcore project is on, you might be able to setup and work with multiple environments. You can have up to three environments: Development, Staging and Live.
Having multiple environments can be a great help when you want to test your content structure before your content editors get to work.
When you have multiple environments on your Heartcore project you need to make sure that you follow the correct deployment workflow. In this section you will find more details about the workflow along with descriptions of the two steps: Structure deployments and Content and media transfers.
In this article you can learn more about the Umbraco backoffice which is the interface you will be using for creating and managing the content for your Umbraco Heartcore project. The backoffice contains multiple sections as well as a handful of features specific to the Umbraco Heartcore project.
In the backoffice of your Umbraco Heartcore project you will find an API Browser. This is a tool that lets you explore and inspect the API endpoints based on your data and content you, in order to learn more about what is returned.
Want to know more about the API keys and how to add them to your users in Umbraco Heartcore backoffice? Look no further. In this article you can read about it.
Learn more about how to setup webhooks for various actions in the Umbraco backoffice.