- Group venv creation and activation by shell, because Windows uses backslashes
- Note that the env folder should be excluded from version control
- Account for the need to specify the directory for `wagtail start` when the directory already exists
- Move the `cd mysite` line to the project dependency instruction, because that's the first time it's really needs
-
In the interest of better diffs:
Instead of breaking by line length, break by sentence. Break lists by item in the list and put some long urls on their own lines.
- Always clarify that the instructions assume a virtual environment
- Add to the tutorial instructions for using venv
- Clarify that Python 3 is required
- Clarify that the tutorial is an alternative to "Getting started" that
assumes less background knowledge
- Remove pip installation instructions because Django only supports
versions of Python that include it
- Make headings in the tutorial instead of an ordered list
This makes the page easier to scan visually and allows linking to
specific headings.
- Add the warning about Pillow dependencies to the tutorial
- In "Getting started" move Pillow's dependencies to the general
dependencies list
- Make language more welcoming (saying "we just do x" alienates people
who have less familiarity with x")
- Other small text changes
* Fetch new translations from Transifex, update contributors, add new languages with >90% coverage to WAGTAILADMIN_PROVIDED_LANGUAGES
* Update transifex config to download Chinese (Simplified) and Chinese (Traditional) translations as zh_Hans and zh_Hant respectively
* Fix get-translator-credits.py to recognise 'tet' as the locale string for Tetum (which Babel doesn't)
Labels for sortable headings need whitespace around them in order for the arrow to be correctly positioned. In addition, some headings had the label outside of the sort link - this is now fixed too.
There was a small bug in the page chooser, where it would display
`page.title` instead of `get_admin_display_title` when loaded on with a
specified parent. This was because the page chooser was falling back to
Page.get_admin_display_title instead of the specific kind
Running `npm install` without `--no-save` can introduce spurious changes to package-lock.json due to differences in platform / node version, and these have been known to accidentally sneak into people's PRs. `npm install` without `--no-save` should only be used when actively updating node dependencies in package.json.
