Clicking the pencil icon next to the title of an article should open up the corresponding markdown file in edit mode in gitea, instead a 404 page is served :(
Clicking the pencil icon next to the title of an article should open up the corresponding markdown file in edit mode in gitea, instead a 404 page is served :(
I'm unsure if /docs/ should be on the end of that? 🤔
Thanks for reporting @cgalo5758! I think it has something to do with:
https://git.coopcloud.tech/coop-cloud/docs.coopcloud.tech/src/commit/8790f95c5300728894b74711dd30bc2ef3f88f17/mkdocs.yml#L82-L84
I'm unsure if `/docs/` should be on the end of that? 🤔
Looking at the docs, it seems that a user would need to be both authenticated and have permission to edit the repo for the link to work on Gitea. If you are authenticated, Gitea will not prompt you to fork the repo to edit the page (e.g. like in Github). I wonder if Gitea has a fork-on-edit feature in the works.
There also seems to be no good fork-and-edit url that Gitea can serve for us to hack the config as the fork repo urls look like this https://git.coopcloud.tech/repo/fork/140
Maybe some other feature/system might make sense to make the site truly editable as intended.
Looking at the docs, it seems that a user would need to be both authenticated and have permission to edit the repo for the link to work on Gitea. If you are authenticated, Gitea will not prompt you to fork the repo to edit the page (e.g. like in Github). I wonder if Gitea has a fork-on-edit feature in the works.
There also seems to be no good fork-and-edit url that Gitea can serve for us to hack the config as the fork repo urls look like this `https://git.coopcloud.tech/repo/fork/140`
Maybe some other feature/system might make sense to make the site truly editable as intended.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Clicking the pencil icon next to the title of an article should open up the corresponding markdown file in edit mode in gitea, instead a 404 page is served :(
Thanks for reporting @cgalo5758! I think it has something to do with:
8790f95c53/mkdocs.yml (L82-L84)I'm unsure if
/docs/should be on the end of that? 🤔Looking at the docs, it seems that a user would need to be both authenticated and have permission to edit the repo for the link to work on Gitea. If you are authenticated, Gitea will not prompt you to fork the repo to edit the page (e.g. like in Github). I wonder if Gitea has a fork-on-edit feature in the works.
There also seems to be no good fork-and-edit url that Gitea can serve for us to hack the config as the fork repo urls look like this
https://git.coopcloud.tech/repo/fork/140Maybe some other feature/system might make sense to make the site truly editable as intended.