And you’re awesome for already wanting to contribute @4ong!
On the frontend side, one area where I’d like to improve is our support of features embedded in the raw content of a post.
On top of handling the regular Markdown content of the post, we can also support several features provided by Discourse’s custom markup.
As you might already be familiar, Discourse supports a custom syntax for features like quotes, toggles, dates, and even polls.
In a fairly typical approach, we have carved out some initial support for basic features like code embeds, and then have a " is not supported at this time" block for the features that aren’t implemented yet.
I’d love to completely eliminate those “not supported” blocks from our app. Polls and Toggles would be really great to have supported in particular.
Also, because Lexicon operates off of the raw content of a post, we bypass OneBox support. So at a minimum, it would be good to have basic support for link previews.
One feature I’m stoked to eventually support is deep-linking from emails. This is probably not a trivial feature to implement, and would likely involve building a Discourse plugin in Ruby.
Essentially, this would allow users to tap on a link to a post in an email from Discourse, and have it open the app (if installed) to that exact post via a deep-link through Discourse.
And if the app isn’t installed, or the user is not on a mobile device, it would pass them through to the site as usual.
If anyone wants to tackle this one, reach out to me. It’d be huge to have that working.
EDIT: Also check out the Supported Discourse Features page of our documentation to see which features aren’t yet supported, and feel free to tackle any of those (other than push notifications, which we’re already working on).