Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

README: Add intentional differences from web client to Feature status. #1224

Merged
merged 1 commit into from
May 19, 2022

Conversation

neiljp
Copy link
Collaborator

@neiljp neiljp commented May 16, 2022

What does this PR do?

The About part of the README already has details of the project focus/scope, and features considered only for longer-term resolution.

This specifies other intentional design choices which might be useful, or cause users to stumble or being surprised if having used the web app.

Fixes #547 (Document intentional design choices where different from webapp/mobile)

Tested?

  • Manually
  • Passed linting & tests (each commit)

Notes & Questions

I've noted down a set of elements that differ; we can amend these here or update them later.

Interactions

Related to #731, but that is for incomplete features which we intend to implement, rather than intentional choices to implement differently (or not implement).

@neiljp neiljp added the area: documentation Requires changes in documentation label May 16, 2022
@neiljp neiljp added this to the Next Release milestone May 16, 2022
@zulipbot zulipbot added size: S [Automatic label added by zulipbot] difficult high priority should be done as soon as possible labels May 16, 2022
@neiljp neiljp merged commit 5776528 into zulip:main May 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: documentation Requires changes in documentation difficult high priority should be done as soon as possible size: S [Automatic label added by zulipbot]
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Document intentional design choices where different from webapp/mobile
2 participants