We have currently simple GitHub page, but we need to think about it's update with some better design.

We have a server that is for authenticating to AWS to be able to upload.
That server requires JWT for authentication. The XHR plugin supports custom headers.
Would it be possible to implement the same thing on the AWS plugins as well?

Feature

v1 had a noIndex option: https://docusaurus.io/docs/en/site-config#noindex-boolean

Let's add it to v2 too!

Also need to:

• edit the migration doc: https://v2.docusaurus.io/docs/migrating-from-v1-to-v2/#removed-fields
• edit the migration cli to migrate correctly this config

There are scripts to easily test the migration cli, look at scripts `yarn test:v1Migration:migrate

Sentry Issue: KAP-5KT

TypeError: Cannot read property '1' of null
  File "app:///main/utils/encoding.js", line 17, in getEncoding
    return /.*: Video: (.*?) \(.*/.exec(error.stderr)[1];

This will be an issue to track the changes required to move all the assets in this repository to https://github.com/firstcontributions/assets

🐞 Problem
The size of this repository is around 34MB now. This will keep on increasing. The assets in this repository is about 10MB big. If we move them to another repository, we can reduce size of this repository and the rate at which it increases

The ability to set the language on the user creation form could be something useful on a multi user environment.

current code

        #if !os(watchOS)
        if #available(tvOS 10.0, *) {
            let format = UIGraphicsImageRendererFormat()
            format.scale = scale
            let renderer = UIGraphicsImageRenderer(size: size, format: 

Here it is from original diablo 2:

The keys displayed should reflect the current user keybindings

What is the motivation for adding / enhancing this feature?

Currently, we have ckoWebHookUrl and ctApiUrl attributes inside config. We should get rid of ckoWebHookUrl and replace it to ctApiUrl in each place where old attribute has been used.

What are the acc

Currently we are utilizing features to selectively enable/disable dynamic plugin loading code throughout the bevy codebase. @Dispersia had the good idea to move this to a separate crate, which I think should be possible. This would simplify the cargo features and move all of the dynamic plugin loading code to one spot.