| Commit message (Collapse) | Author | Age | Lines |
... | |
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
This has a caveat in that there may be additional padding if the first
thing in a list item is an image, but it is very unlikely in practice,
so it's not handled for now.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Dewikification: Content app improvements.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Adds image caption capabilities and documents missing HTML extensions
available.
|
|\| | |
|
| |\ \
| | | |
| | | | |
Dewikification - Create content app
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This allows us to properly escape codeblocks within markdown, permalink
to headers on a page, and decouples getting metadata from a file and
getting generated HTML from the Markdown content.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Articles was a good name, but we want an `articles` category in
the future. `/pages/guides/` and `/pages/articles/` are clearer in name
than `/articles/guides/` and `/articles/articles/`.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This makes it consistent with the django-wiki version of the code
blocks, which looks neater.
|
| | |\ \ |
|
| | |\ \ \ |
|
| | |\ \ \ \ |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
As this system will be used for more than just guides,
I had to do some refactoring to match this system with plans.
Basically now there isn't guides, but articles instead.
|
| | | |_|_|/
| | |/| | | |
|
| | |_|_|/
| |/| | |
| | | | |
| | | | |
| | | | | |
This makes it consistent with the django-wiki version of the code
blocks, which looks neater.
|
| |\ \ \ \
| | | |_|/
| | |/| | |
|
| | | | | |
|
| | | | | |
|
| |/ / /
|/| | | |
|
|\ \ \ \
| |/ / /
|/| | | |
Dewikification - Create app for resources + index page of resources
|
| | | | |
|
| |\ \ \
| | | |/
| | |/| |
|
| | |/
| |/| |
|
| |/
|/| |
|
|/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Hooks added:
* check-merge-conflict - checks for files with merge conflict strings
* check-toml - attempts to load all toml files to verify syntax
* check-yaml - attempts to load all yaml files to verify syntax
* end-of-file-fixer - ensures files end in a newline and only a newline
* mixed-line-ending - replaces mixed line endings with LF
* trailing-whitespace - trims trailing whitespace
* python-check-blanket-noqa - enforces that noqa annotations always
occur with specific codes
Changes made to comply with new hooks:
* Remove trailing whitespaces
* Remove some useless noqa annotations
* Specify errors for noqa annotations
* Add missing newlines at end of files
See: python-discord/organisation#138
|
|\ |
|
| | |
|
| | |
|
|\| |
|
| |
| |
| |
| |
| | |
Any text following the end of a codeblock in the wiki would very closely hug the codeblock, impacting readability and giving poor structure to page content.
This adds in an appropriate margin to the bottom of codeblocks to give a fair buffer that matches typical paragraph spacing.
|
| | |
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
https://github.com/python-discord/site/issues/302
This commit makes newlines in deleted messages visible in the deleted
messages front-end and makes sure they are not stripped during the
conversion to HTML. To represent newlines, I've chosen a commonly
used symbol: `↵`.
In addition, I've kaizened the colour filter that translates integer
representations of colours to their RGB hex-value. The Discord dark
theme shows black colours (int: 0; hex: #000000) as white instead, to
make reading them against the dark background easier. This commit
makes sure our front-end displays the same behavior.
This closes #302
|
|\ |
|
| |\ |
|