| Commit message (Collapse) | Author | Age | Lines |
| |
|
| |
|
|
|
|
| |
Signed-off-by: Hassan Abouelela <[email protected]>
|
|
|
|
|
|
|
| |
Adds support for tag groups in content. This involves some modification
to the routing, and templating.
Signed-off-by: Hassan Abouelela <[email protected]>
|
|
|
|
|
| |
Co-authored-by: ChrisJL <[email protected]>
Signed-off-by: Hassan Abouelela <[email protected]>
|
|
|
|
| |
Signed-off-by: Hassan Abouelela <[email protected]>
|
|
|
|
|
|
| |
Add a template for the tag page itself, and add a route to use it.
Signed-off-by: Hassan Abouelela <[email protected]>
|
|
|
|
|
|
|
| |
Adds bot tags to the content page, as well as a model to go along with
it.
Signed-off-by: Hassan Abouelela <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps flake-bandit to v3 to fix an incompatibility with the bandit
package.
This also bumps flake8-annotations to a legally acceptable version,
which introduces ANN401, which disallows `typing.Any` annotations (for
the most part, refer to the docs).
Signed-off-by: Hassan Abouelela <[email protected]>
|
|
|
|
|
|
|
|
|
|
| |
Due to an optimization in CPython that is amended in 3.10, coverage.py
is sometimes unable to determine the coverage of continue statements in
branches. See: https://github.com/nedbat/coveragepy/issues/198
Adding a no-op like a print or an empty statement would solve the
coverage issue, but I've opted to just ignore the line. This should be
tested and the line removed when the site is updated to Python 3.10.
|
|
|
|
|
|
|
|
| |
We have to add another check since `subarticles` is actually a list of
dictionaries and not a dictionary, so key overriding does not work.
We want the categories to take precedence over the pages in case of
future feature expansion involving showing sub-sub-articles.
|
|
|
|
|
|
| |
This allows us to keep filenames (thus URLs) as concise as possible,
while having a more descriptive entry in the Sub-Articles dropdown for
category pages.
|
|
|
|
|
| |
This was causing mysterious 404s because while migrating a feature to
dewikification, the same variable would be placed in the settings file.
|
|
|
|
|
| |
This only shows when the page is also a category, since regular pages
have no children and regular categories already list their children.
|
| |
|
| |
|
|
|
|
|
|
| |
This is useful for our /contributing pages, which have a main
contributing page at /contributing but project pages under the same
path, /contributing/bot etc.
|
|
|
|
|
|
|
| |
Make category `title` consistent with page `title`.
Simplify `icon` key, since there is no benefit to defining the icon
class and the icon separately.
Allow overriding the `icon` for category entries just like page entries.
|
|
|
|
|
|
| |
The tests uses pyfakefs to simulate a fake filesystem that is reused
over the content app tests.
Test coverage for the app is brought to 100%.
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Rather than having two views for the base page and all other pages, all
pages now use the same view.
The view context handler is simplified to take advantage of pathlib
features.
The markdown folder is now /content/resources/* rather than
/content/resources/content/*, as the latter is unnecessary nesting.
|
|
|
|
|
|
| |
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 feature is still under implementation debate, so it will be further
discussed in another issue and implemeneted in a future PR.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
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.
|