Roadmap

[okaerin]

Hi
I am very much interested into texlyre, as I am a typst enthusiast. It looks like a good alternative to typst.app which is actually selfhostable.
I can only congratulate on how far you already are and I'll keep following this project.
I do realize that the project just started and might not yet have a roadmap as such. I wanted to make a few suggestions to what kind of features would be beneficial to be an even more amazing collaborative writing platform. Of course they can be also ignored if they are out of scope or not planned:

• Tracking changes (if collaborating, see if some user modified a part of the text. A simple git diff style would already be something)
• Different storage backends (github is great and all, but gitea or others are too)
• Different authentication methods (instead of only texlyre )
• Spellchecking with e.g. languagetool

[fabawi]

Thank you, It's always great to receive such kind words of support. As for your suggestions:

• I'm considering the review features, but I'm still contemplating how to implement it without degrading performance
• TeXlyre will hopefully support Gitlab and Codeberg by the end of November. Gitea could be supported too, but will have to see what kind of issues it may run into with self-hosted providers
• The login system is actually not related to TeXlyre. The account is stored on your browser, and we don't receive your data or credentials. One reason you need an account is to encrypt your API keys (GitHub only for now) with your password. For now, we don't provide such a service, but there are plans to support (optional) some cloud features if there is demand. The other reason we need you to set up an account is to confirm your age and that you read the privacy info since you do connect to our signaling servers, which require your IP to establish the communication with peers for collaboration
• Spell-checking is an important feature. Problem is, powerful libraries like languagetools are not designed to run in the browser and need a server. I have some ideas on how to approach this, but need to explore possible solutions before I proceed with implementation

[fabawi]

• Different storage backends (github is great and all, but gitea or others are too)

Added support for GitLab, Gitea, and Forgejo (Codeberg) backup in #111