Replace various instances of Riot with Element

This commit is contained in:
J. Ryan Stinnett 2020-11-25 17:01:19 +00:00
parent d05c022d4f
commit f1e89bf833
10 changed files with 11 additions and 11 deletions

View file

@ -74,7 +74,7 @@ Key:
Notes:
+ A task begins when all its dependencies (arrows going into it) are fulfilled.
+ The success of setting up rageshake is never asserted, riot-web has a fallback path for running without IDB (and thus rageshake).
+ The success of setting up rageshake is never asserted, element-web has a fallback path for running without IDB (and thus rageshake).
+ Everything is awaited to be settled before the Modernizr check, to allow it to make use of things like i18n if they are successful.
Underlying dependencies:

View file

@ -152,7 +152,7 @@ decentralised.
Desktop app configuration
=========================
See https://github.com/vector-im/riot-desktop#user-specified-configjson
See https://github.com/vector-im/element-desktop#user-specified-configjson
UI Features
===========

View file

@ -40,7 +40,7 @@ should start a new conference on your Jitsi server.
domain will appear later in the URL as a configuration parameter.
**Hint**: If you want everyone on your homeserver to use the same Jitsi server by
default, and you are using riot-web 1.6 or newer, set the following on your homeserver's
default, and you are using element-web 1.6 or newer, set the following on your homeserver's
`/.well-known/matrix/client` config:
```json
{

View file

@ -43,7 +43,7 @@ When reviewing code, here are some things we look for and also things we avoid:
### Workflow
* Authors should request review from the riot-web team by default (if someone on
* Authors should request review from the element-web team by default (if someone on
the team is clearly the expert in an area, a direct review request to them may
be more appropriate)
* Reviewers should remove the team review request and request review from

View file

@ -52,7 +52,7 @@ other changes:
- skins/vector/themes/foo/css
- skins/vector/themes/foo/img
- skins/vector/themes/foo/fonts
- ideally riot-web would contain almost nothing but skins/vector directory.
- ideally element-web would contain almost nothing but skins/vector directory.
- ability to entirely replace CSS rather than override it for a given theme
- e.g. if we replace `Login.js` with `StatusLogin.js`, then we should similarly be able to replace `_Login.scss` with `_StatusLogin.scss`.