Some instances of Github and Gitlab have been changed to GitHub and GitLab
respectively.
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/425
Reviewed-by: Panagiotis "Ivory" Vasilopoulos <git@n0toose.net>
Co-authored-by: Skye <skyeforeverblue@outlook.com>
Co-committed-by: Skye <skyeforeverblue@outlook.com>
Add the SSH commit signing section to the SSH key management page. Git has had this feature for a while now and SSH keys are easier to manage since they can be used for both authentication and signing, so I think it makes sense to document this.
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/420
Reviewed-by: Panagiotis "Ivory" Vasilopoulos <git@n0toose.net>
Co-authored-by: Sergey Volkov <ser121512@yandex.ru>
Co-committed-by: Sergey Volkov <ser121512@yandex.ru>
Resolves#407
Co-authored-by: I <igor@its.rel.pl>
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/408
Reviewed-by: Otto <otto@codeberg.org>
Co-authored-by: Igor <309631@noreply.codeberg.org>
Co-committed-by: Igor <309631@noreply.codeberg.org>
The URL for the man page of Git LFS migrate was broken. This is fixed in this PR.
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/404
Co-authored-by: Andre601 <github@andre601.ch>
Co-committed-by: Andre601 <github@andre601.ch>
It fixes a small typo on the "First repository" document.
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/402
Reviewed-by: Panagiotis "Ivory" Vasilopoulos <git@n0toose.net>
Co-authored-by: And4po <anderromeroaldana@proton.me>
Co-committed-by: And4po <anderromeroaldana@proton.me>
I believe the "pip" in front is extraneous. This is a small change.
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/397
Co-authored-by: kouett <lou@ynh.kouett.net.eu.org>
Co-committed-by: kouett <lou@ynh.kouett.net.eu.org>
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>
This should make it comply a bit more with the style guide.
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/392
Reviewed-by: Panagiotis "Ivory" Vasilopoulos <git@n0toose.net>
Co-authored-by: thatonecoder <thatonecoder@noreply.codeberg.org>
Co-committed-by: thatonecoder <thatonecoder@noreply.codeberg.org>
Main changes include switching language from ISP to domain registrar, and standardization around the phrase "Codeberg Pages".
Signed-off-by: Mark Pitblado <mark@pitblado.me>
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/391
Reviewed-by: crapStone <codeberg@crapstone.dev>
Co-authored-by: Mark Pitblado <mark-pitblado@noreply.codeberg.org>
Co-committed-by: Mark Pitblado <mark-pitblado@noreply.codeberg.org>
The current text refers to CommonMark 0.30, but the latest version of CommonMark is 0.31.2, and the latest version of GoldMark is compatible with that version of CommonMark.
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/390
Reviewed-by: Gusted <gusted@noreply.codeberg.org>
Co-authored-by: ToaKraka <toakraka@noreply.codeberg.org>
Co-committed-by: ToaKraka <toakraka@noreply.codeberg.org>
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/380
Reviewed-by: Panagiotis "Ivory" Vasilopoulos <git@n0toose.net>
Co-authored-by: A Frederick Christensen <fauxmight@noreply.codeberg.org>
Co-committed-by: A Frederick Christensen <fauxmight@noreply.codeberg.org>
Increase the contrast of the placeholder text in the search input, so it's actually readable.
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/375
Co-authored-by: Gusted <postmaster@gusted.xyz>
Co-committed-by: Gusted <postmaster@gusted.xyz>
This should solve #23.
This is a fully static search implementation powered by [Pagefind](https://pagefind.app/).
In terms of UI, I found and implemented a section in the sidebar for searching the documentation. It was hidden presumably waiting for implementation. It mentioned using the slash (/) key for searching, so I implemented the hotkey as well.
I made the indexing command required by Pagefind run after Eleventy finishes building using the `.after` hook.
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/370
Co-authored-by: oatbiscuits <oatbiscuits@noreply.codeberg.org>
Co-committed-by: oatbiscuits <oatbiscuits@noreply.codeberg.org>
This PR adds docs on WebAuthn usage on Codeberg. It attempts to cover:
- using WebAuthn as a 2FA option on web logins
- using FIDO2 over SSH using the OpenSSH client
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/367
Co-authored-by: Alex <alex@blueselene.com>
Co-committed-by: Alex <alex@blueselene.com>
- Formatting fixes, relevant text adjustments
- Some more complicated cases (e.g. attribution), as well as outdated
information that should be removed in a later commit were
deliberately left unchanged.
- Some minor mistakes (speling, trailing whitespaces, punctuation)
in the admonition boxes were also fixed.
Added an entry to the troubleshooting page for Codeberg pages that addresses the situation with Cloudflare, where you should turn DNS entries pointing to Codeberg pages to **DNS only** for it to work reliably.
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/351
Co-authored-by: Andre601 <andre601@noreply.codeberg.org>
Co-committed-by: Andre601 <andre601@noreply.codeberg.org>
Also clarifies language about custom domains and codeberg.page
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/357
Co-authored-by: crystal <crystal@noreply.codeberg.org>
Co-committed-by: crystal <crystal@noreply.codeberg.org>
Related issue: https://codeberg.org/Codeberg/Documentation/issues/330
This is my attempt at adding admonition-like boxes to the documentation. The goal is to make important stuff stand out more (especially warnings and alike).
The system uses a custom `<admonition>` box which allows classes for further customization. I.e. `<admonition class="warning">` to display a warning box.
I first wanted to make individual boxes (`<warning>`, `<note>`, ...) but decided against it, as it would've created a lot of duplicate CSS.
The CSS is designed in such a way that the first paragraph of the box is made bold (font-weight 700) while any subsequent ones are not.
The following forms of admonitions are included:
- Info (default)
- Note
- Tip
- Warning
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/337
Co-authored-by: Andre601 <github@andre601.ch>
Co-committed-by: Andre601 <github@andre601.ch>
The language was simplified, some explanations as to which methods are
preferred for which situations were provided, and I also added an
explanation for the new "tag @moderation to report spam" feature.
I tried to make the content less ambiguous and easier to read.
This change was made because of the following issue in the Community
repository: https://codeberg.org/Codeberg/Community/issues/1293
- Create two sections, "Codeberg's Structures" and "Before I move..."
- Explain that Codeberg is not necessarily *just* a Forgejo instance
by mentioning / crediting more open-source projects in a
non-exhaustive manner.
- Improve wording and phrasing of some questions
- Update Forgejo version instructions
- Private repositories: Split into two questions that are separately
meant for collaborative projects and ordinary users respectively.
- Use words as "most likely" and "probably" in order to *not* make the
reader immediately worry about potentially breaking the rules,
especially as the ToS itself mentions that the platform reserves
the right to take strict action without a warning. If the user
choose Codeberg to begin with, it is very likely that "our" values
align.
- Explain what "fair use" is as far as the repository size is concerned
better.
- Break text into new lines depending on columns and the ideas that
each part of a sentence gets across.
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/347
* Improve references to Forgejo and Gitea
* Point reader to potentially good first issues
* Be more specific as to what kinds of patches can be submitted to the
`Codeberg/forgejo` repository
* Explain how easy Go can be for beginners better
* Include some advice as to what a prospective contributor can work on
based on personal experiences
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/326
This was added because a user was not sure where they could request an
increase to the repository limit of an organization that they intended
to use for a hackathon.
We may want to consider creating a more detailed page about this later.
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/336
Some language tweaks.
* remove capital letters from some words
* fix typos
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/338
Co-authored-by: rtn <rtn@noreply.codeberg.org>
Co-committed-by: rtn <rtn@noreply.codeberg.org>
