Prepare the web application for compatibility

Before anything else, you should evaluate whether your website or web application is compatible with WEBCAT. There are a few strict requirements:

• The frontend must be fully static (i.e., no server-generated HTML, JavaScript, or CSS).
• No inline JavaScript is allowed.
• A Content Security Policy (CSP) must be provided via an HTTP header and must satisfy specific constraints (see: CSP Guide, explanation blog post).

See the following examples and porting guides (outdated):

• Cryptpad
• Element
• Globaleaks
• Jitsi

At the end, you should have compiled a webcat.config.json base file for your use case.