Home

Feature Development

This wiki is used to track the progress of developing feature ideas, collecting the results of investigations, and documenting rationale and decisions about Matterhorn features. This wiki will serve as a reference for users who want to learn about the status of a feature or help with its implementation. Typically features will only end up on this wiki if they don't have patently obvious approaches or where user experience, and interface, and technical risk considerations are especially important.

Feature pages will provide some information about a feature proposal:

• Decision: What is the status of our decision to implement the feature? Some classifications might include:
  • Ready: we've determined that we have everything we need to create tickets and begin work.
  • Needs investigation: more context is needed before a clear implementation plan can be proposed.
  • Needs alignment: there may not yet be Matterhorn development team alignment on the proposed feature or its scope.
• Approach: what is the proposed approach to implement the feature?
• Impact: is there a good understanding of the impact of the new feature? (Required refactoring and redesign, etc.)
• Context: what is the context any reader will need to understand how a feature needs to be implemented? This might include API references, specifications, blog posts, upstream developer exchanges, etc.

Active Feature Pages

• (Always active: Feature Backlog)
• Mouse Support
• Emoji Reactions
• Channel History Search
• Multiple Sessions
• Error Handling
• Multi-Factor Authentication
• Conversation View
• LocalMessageReference

Inactive Feature Pages

These pages are for features that have been completed.

• API V4 Code Generation
• User Name Configurability
• Message Management
• Custom Themes
• Skylighting Syntax Files
• Logging
• Improved Markdown Handling