Lucas Hinderberger lhinderberger
Loading Heatmap…

lhinderberger commented on issue Codeberg/Documentation#67

What parts of our web interface need further documentation?

For convenience, that would be the one attached below

11 hours ago

lhinderberger commented on issue Codeberg/Documentation#56

Extend "First Repository" article

We should certainly write about all of these topics :) I wasn't aware about citable code yet but I'm very curious about it - I'm looking forward to your article on this 👍 🚀

11 hours ago

lhinderberger commented on issue Codeberg/Documentation#71

Backlink

How would we get back to the home page of the documentation then? (the intent originally was to expand a bit on the home page, e.g. with some tiles to click on)

12 hours ago

lhinderberger commented on issue Codeberg/Documentation#29

Closing the wiki after Deployment of the site

Help is needed from someone with administration permission on this repository. I am not authorized to close the wiki myself. Also, we'd need to update the README of Codeberg/Community

1 day ago

lhinderberger opened issue Codeberg/Documentation#70

Provide more ways to close the menu

1 day ago

lhinderberger commented on issue Codeberg/Documentation#62

Wording "menu on the left" on home page

I like that idea - maybe it can be done with adding a semi-transparent overlay when the menu is open (which would also look very nice). Let's move it to a new issue to keep track of it.

1 day ago

lhinderberger commented on issue Codeberg/Community#280

FR: Add RSS feed to projects

That's a very nice idea :) And there's already a feature request for Gitea: https://github.com/go-gitea/gitea/issues/569 At this moment, to get alerts for repositories there's also the possibility to "watch" a repository by clicking the button with the "eye" icon when in a repository (see enclosed screenshot). When you watch a repo, you'll get an email for example for new issues, PRs and comments.

1 day ago

lhinderberger commented on issue Codeberg/Documentation#66

Write an Article on installing Git (CLI)

> I'm not sure about "our" style [...] I'm sorry, my earlier response was a misleading in that regard. There's currently no such thing like a Codeberg Documentation style/tone that needs to be followed, so no worries 😉 What I meant was to do try to do it similarly to the existing Getting Started Guide to make it feel more like a step-by-step guide.

1 day ago

lhinderberger commented on issue Codeberg/Documentation#67

What parts of our web interface need further documentation?

It has integrated Git support which makes it possible to clone your repo and make commits, pushes and pulls directly from within the editor. Alternatively, if you already have your repository cloned, you can simply point VS Code to the repository's directory and it should work out-of-the-box.

1 day ago

lhinderberger commented on issue Codeberg/Documentation#56

Extend "First Repository" article

The `eleventyNavigation` header is what holds the structure of the site. For a given subsection it can look like this: ``` --- eleventyNavigation: key: WhatIsCodeberg title: What is Codeberg? parent: GettingStarted order: 10 --- ``` Every section and article/subsection has a unique `key`. If `parent` is set to the `key` of another section, the current document will become a subsection of that other section. The other fields are `title` and `order`, where `title` is merely a display name and determines the menu entry label as well as the article's heading but has no other "technical" semantics and `order` is a number that can be used to enforce a specific order of subsections (which is good for step-by-step guides such as Getting Started for example). So to create a new subsection, find the `key` of your desired parent section in its Markdown source code and use it as the `parent` for your new article/subsection.

1 day ago

lhinderberger opened issue Codeberg/Documentation#69

Codeberg Documentation: Contributor FAQ

1 day ago

lhinderberger commented on issue Codeberg/Documentation#67

What parts of our web interface need further documentation?

> I had to commit in the meantime so I committed to (my) master branch... Is there a way to create the PR to another branch [...] [This StackOverflow question](https://stackoverflow.com/questions/1628563/move-the-most-recent-commits-to-a-new-branch-with-git) seems to be the solution, if I understood your question correctly :)

1 day ago

lhinderberger commented on issue Codeberg/Documentation#67

What parts of our web interface need further documentation?

I can warmly recommend Visual Studio Code (or VSCodium) for working on Codeberg Documentation - it's intuitive to use, great for Markdown and as a bonus it's a pleasure to look at. 😉

1 day ago

lhinderberger reopened issue Codeberg/Community#252

relative link in Markdown file

1 day ago

lhinderberger commented on issue Codeberg/Community#252

relative link in Markdown file

As indicated in Codeberg/Documentation#67, treating URLs in Markdown that start with a slash not as relative to the repository root but as relative to the web root could be worth reconsidering. We might want to write a PR to gitea to change that behavior?

1 day ago

lhinderberger commented on issue Codeberg/Documentation#67

What parts of our web interface need further documentation?

Are you editing the documentation using the web interface or do you use a local editor and the `npm run serve` command? In the latter case, that sounds like a bug that needs further investigation. The first case seems to be the same problem as in Codeberg/Community#252 - I think it would be worth the effort to reopen that issue with the goal of modifying Gitea to parse URLs starting with a slash as relative to the repository and not as relative to the web root.

1 day ago

lhinderberger commented on issue Codeberg/Documentation#67

What parts of our web interface need further documentation?

> @lhinderberger How do I insert screenshots in the documentation: > * where should the file(s) be saved? Is it in assets/images? Should I create a folder there? Yes, `assets/images` is the right place for screenshots. Make sure to put them in a directory that matches the path of the article (just like the existing screenshots), to keep a uniform structure. But if they end up in the wrong place, that wouldn't be the end of the world, as it would be fixed when reviewing the PR. :) > * what format? Screenshots should be in the PNG format, as its lossless and does not have artifacts on geometric shapes. **Optionally**, if you want it to be extra nice, feel free to also add a webp version (please use the `-lossless` option), embedding it using `<picture>` tags for smooth fallback on Safari ([as seen here for example](https://codeberg.org/Codeberg/Documentation/raw/branch/master/content/getting-started/issue-tracking-basics.md)). That would be super nice, but it's not required. > * what (minimum) size? It should be large enough that all relevant text can still be recognized. In practice, I have often used a resolution of about 1300x800px > Should I commit to (my) master branch, or should I "create a new branch from this commit and start a pull request"? Creating a new branch is good practise for PRs, because it makes it easier to work on multiple articles in parallel (for example because one article cannot be pulled yet and you want to start to write the next one). If you have any further questions, feel free to ask any time! :)

1 day ago

lhinderberger commented on issue Codeberg/Documentation#67

What parts of our web interface need further documentation?

> EDIT: OK, I've just noticed this referencing is automatic, nice! Yes that's right :) Only creating an issue dependency (so, a "hard" dependency of one issue blocking another) requires write permissions to a repository.

1 day ago

lhinderberger commented on issue Codeberg/Community#271

Suggestion: Add icons to Codeberg sub-organizations

Prefixing the organization names with codeberg would be a good idea, because some names (like fonts) are not possible without a prefix in Gitea.

1 day ago

lhinderberger closed issue Codeberg/Community#173

your password requirements for new users are annoying and put you in a bad light

1 day ago