01b2e16f7d
* Improved topic cards now show three articles, with new design (#6408) * Improved topic card now show three top articles * Alter the help_topics macro to support showing three articles * Add show more section with sectional line above * Add logic to the product_landing view to return docs and counts * A utility function builds the topics_context for the cards * Fix card scroll for topic cards on mobile * Topics can only wrap once before being cut off with ellipses * Use query annoation in `utils.py` to gather topics * Use `chain` and `islice` to ensure proper doc order and count * Removed unneeded comments * Improved db impact of `get_featured_articles` by handling filters in memory. * Corrected various other requested items * Accept all topics in call to get_featured_articles and limit db hits * Remove unneeded distinct() |
||
|---|---|---|
| .circleci | ||
| .devcontainer | ||
| .github | ||
| .vscode | ||
| bin | ||
| configs | ||
| docker | ||
| docs | ||
| jsi18n | ||
| kitsune | ||
| media | ||
| playwright_tests | ||
| scripts | ||
| styleguide | ||
| svelte | ||
| webpack | ||
| wsgi | ||
| .adr-dir | ||
| .dockerignore | ||
| .editorconfig | ||
| .env-build | ||
| .env-dist | ||
| .env-test | ||
| .eslintrc | ||
| .gitignore | ||
| .nvmrc | ||
| .pre-commit-config.yaml | ||
| .stylelintrc | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTORS.rst | ||
| Dockerfile | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| babel.cfg | ||
| babeljs.cfg | ||
| contribute.json | ||
| docker-compose.yml | ||
| manage.py | ||
| mkdocs.yml | ||
| newrelic.ini | ||
| package-lock.json | ||
| package.json | ||
| poetry.lock | ||
| postcss.config.js | ||
| pyproject.toml | ||
| setup.cfg | ||
| webpack.common.js | ||
| webpack.dev.js | ||
| webpack.pre-render.js | ||
| webpack.prod.js | ||
| webpack.test.js | ||
README.md
Kitsune
Kitsune is the platform that powers SuMo (support.mozilla.org)
Usage
It is a Django application. There is documentation online.
Releasing a new version
-
Create a signed tag for the new version.
We are using semantic versioning.
Given a version number MAJOR.MINOR.PATCH, increment the:
MAJOR version when you make incompatible API changes MINOR version when you add functionality in a backward compatible manner PATCH version when you make backward compatible bug fixesExample:
git tag -s 1.0.1 -m "Bump version: 1.0.0 to 1.0.1 -
Draft a new release in GitHub for the new tag. Document the highlights of the release and also use the option to automatically document the release through the commit history.
-
Trigger the release for the specified tag in the deploy repository.
[!TIP] You can access the staging site at https://support.allizom.org/.
Code of Conduct
By participating in this project, you're agreeing to uphold the Mozilla Community Participation Guidelines. If you need to report a problem, please see our Code of Conduct guide.
Contribute
See our contribution guide, or dive into setting up your development environment.
Issues
We use Bugzilla for submitting and prioritizing issues.