Currently the only way to request data from the APIs is to send the appropriate data via the "request" parameter. While this gives a lot of control it's also quite cumbersome to create a request. To make this simpler the requests should also support "direct parameters".  Examples https://host.name/api/json/?m=categories&a=view&e=all&title=textView all categories that match the title "text".If the "m" parameter is set it should set up a Data object and setRequestValues, i....

The CMS should support "wizard" mode (yes the good ol' windows wizards...). This can be done using the "groups" to only display the fields in the relevant group. By clicking next, it goes to the next page (i.e. group). Once all required  fields are filled or it reaches the last group it'll shows the "submit" button.

The current MD5 file signatures allows end users to check whether the file is still in tact. However it doesn't garanty the file (and MD5) haven'/files/ field and API should support PGP signatures.

It seems the captcha is too easy to parse for a "computer", so:Add (slightly) rotated characters Multi colored lines Picture / character morphing

Question is how do you show closed issues in case they're always filtered. Maybe a "Show closed" option could somehow do the trick.

The password generator + validator should exclude certain characters from the character sets to avoid confusion and potential bugs, e.g.:capital i and lower l are confusing capital o and zero are confusing @ and : may ruin passwords in URL As none of the values are per se incorrect it may make sense to just remove them from the generator but still leave them as "valid" values.