A few suggestions
- Automatic mentions on the community page - for example,
@gilles would become [@gilles](https://microstudio.io/gilles/). Mentions could also trigger account notifications.
- Private updates to a project - For example, adding a new feature that temporarily breaks the game. Once it's working again, you can publish an update to the project. This uses more storage, so it would probably be an opt-in feature.
- Deploying from a Git repository - There could be a way to use GitHub Actions with credentials or there could be GitHub integration, and the project wouldn't require much account storage.
- Account notifications - Something like MicroStats on the microStudio homepage. There could also be a setting to enable push notifications.
- HTML plugins - microStudio isn't as good for tools as it is for games, especially when it comes to complex GUI.
- A popup for new users on the community page - The first time someone writes a post or reply, a popup can inform them about how to write code in Markdown.
- Modular JavaScript - Using modules can streamline the loading order of files and allow the main script to use the usual JavaScript syntax
export function init() { /* ... */ }.
- TypeScript and linting
Validate your e-mail address to participate in the community
