Citable Code #81

For articles in sections that are not a step-by-step guide, let's not use order.

That makes it easier to find articles in the menu once alphabetical sorting is implemented -> #85.

Wording suggestions:

• Share -> refer to your code
• Let’s drop "Obviously" (this article describes what’s wrong with "obviously": https://css-tricks.com/words-avoid-educational-writing/) :)
• Second sentence: "But if you need to reliably refer to a specific version of your code in the long run, for example for scientific writing, this is not really viable, because URLs can change."

(削除) Suggested wording "choose a version number for your new release" because "enter a version" suggests the version already exists. (削除ここまで)

(削除) Maybe also "select the branch that contains the code that you want to release" (削除ここまで)

It's even more complicated - its either choosing an existing Git tag or creating a new one from the latest commit.

Right away, I don't know of a more elegant way of writing it though.

I think that your suggestion is still better than what I wrote. In any case, it constitutes a good starting point for future improvements.
Maybe we should consider adding details about releases in a separate documentation article (we would then link to it in this article about citable code).

That's a good idea -> I created issue nr. #88 for that

already -> outright

Please remove the /content prefix from your link.

Typo: every one -> everyone

Hehe, I threw the idea around, yes - but that's nothing "official" 😉

We should rephrase that to: "It should be possible to write an integration between Codeberg and one of the DOI repositories to make citing code a lot smoother. If you're interested, you may want to have a look at Codeberg/Community#295"

Let's drop "without any risk" and replace it with "in scientific writing".

That is, because statements like "without any risk" might be interpreted as an implied warranty (which we do not provide).

We should add a hyperlink to the issue here.