Konstrukt
🚨 Konstrukt is now Umbraco UI Builder 🚨
  • Konstrukt Documentation
  • Getting Started
    • Overview
    • Installation
    • Configuration
    • User Interface
  • Guides
    • Creating your first integration
  • Areas
    • Overview
    • Sections
      • Summary Dashboards
    • Trees
      • Folders
    • Dashboards
    • Context Apps
  • Collections
    • Overview
    • The Basics
    • List Views
      • Field Views
    • Editors
    • Child Collections
      • Child Collection Groups
  • Searching
    • Overview
    • Searchable Properties
  • Filtering
    • Overview
    • Global Filters
    • Data Views
      • Data Views Builders
    • Filterable Properties
  • Actions
    • Overview
    • The Basics
    • Action Visbility
    • Inbuilt Actions
  • Cards
    • Overview
    • Count Cards
    • Custom Cards
  • Property Editors
    • Overview
    • Entity Picker
  • Advanced
    • Virtual Sub Trees
    • Encrypted Properties
    • Value Mappers
    • Repositories
    • Events
  • Extras
    • Conventions
    • Umbraco Aliases
    • Konstrukt vs UI-O-Matic
    • Known Issues
    • Changelog
Powered by GitBook
On this page
  • System Requirements
  • Versioning
Edit on GitHub
  1. Getting Started

Overview

Getting Started with Konstrukt, the back office UI builder for Umbraco.

PreviousKonstrukt DocumentationNextInstallation

Last updated 2 years ago

In this section we will guide you through the key steps necessary to get you started with Konstrukt.

It is assumed that before we begin that you already have an Umbraco v10+ website configured, ready to install Konstrukt into. If you are unsure how to setup a basic Umbraco install, you should review the documentation on the main Umbraco developer portal and return once you have this in place.

System Requirements

At this time, the minimum requirements for using Konstrukt are as follows:

  • Umbraco 10.0+

  • SQL Server Database (SQLite is fine for testing, but not recommend for live deployments)

Versioning

It's important to understanding Konstrukt's versioning strategy so that you can perform informed upgrades during the life of a project. For Konstrukt, our version numbers can be interpreted as follows Product.Feature.Patch.

  • Product - A distinct version of the Konstrukt product which has significant breaking changes from the product version before it.

  • Feature - A version with one or more new features that have been added. The release could be breaking or non-breaking so it is important to review the changelog before upgrading to a new feature release.

  • Patch - A version consisting of minor, non-breaking bug fixes.

A note about SemVer: It is common within the development community that version numbers should follow the specification, however we don't feel that SemVer fits with how we wish to portray our versioning information. It is important then that developers understand the differences, especially when upgrading to a Feature/Minor release where the SemVer expectation would be for it to be non-breaking which may not be the case.

Getting Started
SemVer