Karl Traunmüller

using Wix; see [this example](https://github.com/fbarbat/fellmonger)

Create a skeleton app that - has all major panes (sidebars, WYSIWYG and source code panes) in place (without any detailed functionality) - uses the CompositorCore Swift package

- link the package version to the Windows App SDK version? - use branches (1.5, 1.6, etc) and [brach-based requirements](https://docs.swift.org/package-manager/PackageDescription/PackageDescription.html#package-dependency-requirement)?

The [geometry package](https://ctan.org/pkg/geometry) uses some non-standard way of declaring package options. Because of this, code completion currently fails to provide known values for options in a `\usepackage[...]{geometry}` command. Figure out...

It would be nice to have additional information/help about the available document classes: 

Now that Microsoft is sunsetting [App Center](https://appcenter.ms), we need an alternative crash reporting system. [Sentry](https://sentry.io/for/native/) looks promising.

Catch `\@missingfileerror` invocations and integrate with Compositor's error & warning reporting ``` \gdef\@missingfileerror#1#2{% \typeout{^^J! LaTeX Error: File `#1.#2' not found.^^J^^J% Type X to quit or to proceed,^^J% or enter new...

The [Troubleshooting Guide](https://compositorapp.com/blog/2018-02-12/TroubleshootingGuide/) is quite outdated and should be updated to reflect the current state of the app.