| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
| |
Adjusted box-shadow for dark mode to be more readable, unfortunately
this gave it a little neomorphism effect...
|
|\
| |
| |
| | |
hopefully I dont have to do this again
|
| |
| |
| | |
Closes #1026.
|
| |
| |
| |
| | |
Closes #963.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Before the title
- Aligned left - more mobile-friendly
- Simpler page structure
- I personally don't think it makes sense for a simple link to a page's
source be a button. Plus, it's similar to the style of other docs like
VS Code
|
| |
| |
| |
| |
| |
| |
| |
| | |
- Using `if pages` to check whether the page is an article or category
doesn't work for /pages/guides
- I still need to modify the styling and position of the button a bit
- Should probably just use a static method and put src_url as context
instead of having a template tag
|
| |
| |
| |
| | |
Signed-off-by: Hassan Abouelela <[email protected]>
|
| |
| |
| |
| | |
Signed-off-by: Hassan Abouelela <[email protected]>
|
| |
| |
| |
| |
| |
| |
| | |
Uses the commit API to obtain tag metadata such as when it was last
edited, and by whom.
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]>
|
| |
| |
| |
| |
| |
| |
| | |
Move the tag cropping logic to the frontend, which makes it easier to
crop without crossing boundaries such as link or code block boundaries.
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]>
|
| | |
|
|/ |
|
|\
| |
| |
| |
| |
| |
| |
| | |
Signed-off-by: Hassan Abouelela <[email protected]>
# Conflicts:
# poetry.lock
# pyproject.toml
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
On clients with a small viewport width, the content title of pages
overlap the "Sub-Articles" dropdown button due to having the same
z-index, causing the element last positioned in the HTML to show up on
top.
Fixes #643.
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Restructure bot contributing guide
Restructures the bot guide to focus on getting users "through the door" first, and slowly adding additional information and options.
The guide is built in terms of showing ways to run the bot and how to achieve it, rather than listing all of the information for each configuration and environment variable right away.
That said, the attempt was to still present the reader with the full information they need, and to still be able to use as a quick reference for contributors who are already familiar with the project.
As a style choice, this guide incorporates collapsible elements, which required some CSS and JS additions. This could be resolved with the bulma-collapsible extension, but it doesn't seem to function well inside django templates.
The guide includes an optional config.yml to use with the test server template. This is a temporary measure until we get the bootstrapping application going.
This guide additionally splits the bot account creation and obtaining Discord ID's guides and they didn't seem related. The original file is kept for now as it is used by other guides at the moment.
|
| |
|
|
|
|
|
| |
We don't need ReasonML support, and the reasonable theme has a really
ugly neon parameter color.
|
|
|
|
|
|
| |
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 only shows when the page is also a category, since regular pages
have no children and regular categories already list their children.
|
| |
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
| |
Given that there is no "long description", just `description` conveys
the same information with brevity.
|
|
|
|
|
| |
If the `relevant_links` field is not provided in the markdown, do not
restrict contents to 2/3 columns.
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Unifies the highlighting with the events app.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
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.
|