Welcome to Redakt, and thank you for trying out our product!
This guide is your starting point to setting up and configuring a Redakt-based application from scratch. It mainly serves as a reference overview and links to other guides for more detailed setup instructions. If you've already completed parts of the getting started guide, you can skip to the sections that are relevant for you.
Setup infrastructure resources
When starting development of your Redakt application, you should already know which infrastructure services and resources you will use for it. Redakt has a very flexible modular architecture and contains many data and service integration modules for popular cloud providers and databases, including Azure, Amazon AWS and MongoDB. Redakt can be configured for single-instance on-premises installations all the way to load-balanced, distributed and scalable cloud setups. Check out the module list for a complete overview, or see typical hosting scenarios for common combinations of modules.
The rest of this guide assumes that you have setup and configured any services and resources that you wish to use for your Redakt application.
To create your first Redakt project, follow the separate project setup guide. After completing this guide, you will have a working Redakt project that is configured for single-instance operation, with a local file embedded database.
Once this is done, you should configure your project to connect to the services and resources that you have setup in the previous section. If you haven't done so already as part of the project setup guide, continue with the configuration guide to setup the required modules for your hosting scenario. If you are only trying out Redakt at this moment, the basic project setup works well and you don't have to configure anything else.
The rest of this guide assumes that you have successfully configured your Redakt project to connect to your chosen services and resources.
Although your Redakt project now successfully starts up, it doesn't contain any content models yet, which are required for any sort of content management. Content models define which properties and data can be managed on your website pages and assets. Continue with the content model implementation guide to create your Redakt content models.
Now that you have created your content models, Redakt needs to know how to render them. This is done by creating standard ASP.NET Core Razor views. Check out the layout implementation guide for instructions on how to create Redakt page views. If you plan to consume Redakt content through the Content Delivery API only, you don't need to create any server-size views.
After you have created some layouts, your application is ready for use. You can now start adding pages and content through the Redakt back office.
Deploying your application
At this point, you should have a fully functional Redakt application up and running. Deploying your application is nothing special, and is done through industry-standard DevOps practices. The deployment guide contains more information on the different ways of deploying your application.
You can now start to explore more advanced scenarios. Check out different application setups, such as separating your back office and public-facing web apps, single page applications and console applications. Learn the different ways of setting up a multilingual website, or how you can organize multiple sites on a single platform. Find out all the ways you can extend Redakt with your own customisations. The possibilities are endless.