🖼️
KASKO Frontend Documentation
  • README
  • Getting started
    • Setting up a new webapp
    • Webapp manifest
    • Building the flow
    • Defining layouts
    • Defining computed values
    • Defining dynamic paths
  • Core concepts
    • Forms
    • Validation
      • Using existing validators
      • Adding custom validators
    • Configuration
      • Price format
      • Date format
    • Performing API calls
    • Toggling visibility of components
    • Translations
    • Rules For Robust Application
  • Guides
    • Using logical statements (JsonLogic)
    • Adding discount codes
    • Developing Custom Plugins
    • Setting required requests
    • Adding save quote for later
    • Transforming request data
    • Manifest merging strategy
    • Knockout flow
    • Local pricing logic
    • Setting up dashboard policy profile
    • Handling offers
    • Repeater
  • Snippets
    • Reset input state
  • Useful resources
    • All component descriptions
    • JsonLogic core documentation
    • Kasko.js documentation
    • Example webapp
    • Example plugins (w/ various frameworks)
Powered by GitBook
On this page

README

Last updated 9 months ago

In KASKO every client-facing app where the customer can purchase an insurance policy is called a webapp. The webapp consists of two important parts:

1. Manifest

Manifest is a JSON structure describing how an application needs to look and function. It has the definition of each individual page of the application and the logic for the flow. Read on in .

2. Field definitions

If the manifest takes care of generating everything that is visible to the end-consumer, the field definitions is the description of the API that the application will interact with. It describes all the required pieces of information that must be collected and the validation rules for them. More about this in .

the manifest guide
the field definitions guide