Inline `code spans` are now mentioned alongsize bold and italics where it makes the most sense to have them, and the preformatted text document has been updated to show the raw Markdown for each example. Each of these documents also cross-references the other, as an aid to the reader.
Several sections in `preformatted-text.md` have been renamed for clarity, with `<a id="old-section-title"></a>` anchors such that inbound links with [fragment identifiers](https://en.wikipedia.org/wiki/URI_fragment#Basics) (direct section links) should not break as a result.
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/805
Reviewed-by: Robert Wolff <mahlzahn@posteo.de>
The linter enforced one style but the introduction should show both
styles, add a ignore lint and make it show the other style.
Reported-by: @mahlzahn
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/724
Reviewed-by: Bastian Greshake Tzovaras <gedankenstuecke@noreply.codeberg.org>
Reviewed-by: Robert Wolff <mahlzahn@posteo.de>
Co-authored-by: Gusted <postmaster@gusted.xyz>
Co-committed-by: Gusted <postmaster@gusted.xyz>
It could be useful to have this information in the documentation.
Co-authored-by: bgg <bgg@bombe>
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/718
Reviewed-by: Bastian Greshake Tzovaras <gedankenstuecke@noreply.codeberg.org>
Reviewed-by: Robert Wolff <mahlzahn@posteo.de>
Co-authored-by: bgg <bgg@noreply.codeberg.org>
Co-committed-by: bgg <bgg@noreply.codeberg.org>
Fixes#646
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/647
Reviewed-by: Robert Wolff <mahlzahn@posteo.de>
Co-authored-by: Jan Koll <jan.niklas.koll@gmail.com>
Co-committed-by: Jan Koll <jan.niklas.koll@gmail.com>
Use https://www.11ty.dev/docs/plugins/image/ to transform images on build time to avif, webp and jpeg.
Images are moved to `/content/images`.
`<picture>` is no longer needed, the plugin does this automatically.
Remove webp images from the source.
Resolves#152Resolves#368
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/488
Co-authored-by: Gusted <postmaster@gusted.xyz>
Co-committed-by: Gusted <postmaster@gusted.xyz>
Update contact page
Prefer references to Forgejo, more relevant to users
Updates to Getting Started Pages / FAQ
- a lot of content was outdated and generally rewritten or rephrased
- implement procedure for size limits as determined by annual assembly
2023, see Codeberg-e.V./Discussion#92
- people are sometimes confused wheter you need to be a paying member in
Codeberg e.V. in order to use the platform
Update improving Codeberg guides
- reduce redundancy in code contribution guide and reference the
Contributing Issue Tracker instead
- separate (and ideally more appealing) donation page (deserves even
more love IMHO)
- shorten and strip outdated information
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/394
Reviewed-by: Panagiotis "Ivory" Vasilopoulos <git@n0toose.net>
Co-authored-by: Otto Richter <git@otto.splvs.net>
Co-committed-by: Otto Richter <git@otto.splvs.net>
Where possible, changed all references from Gitea to Forgejo.
Wherever documentation mentions specifically Gitea, it is preserved.
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/322
Co-authored-by: f0sh <f0sh@mailbox.org>
Co-committed-by: f0sh <f0sh@mailbox.org>
Add initial version of a Markdown documentation to explain Markdown to new contributors. Also provides a styleguide to guide to a consistent use of the Markdown markup within Codeberg.
Fixes#59
Co-authored-by: Jan Klippel <c0d3b3rg@kl1pp3l.de>
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/221
Co-authored-by: jklippel <jklippel@noreply.codeberg.org>
Co-committed-by: jklippel <jklippel@noreply.codeberg.org>
