Announcement: we are testing static pages on https://codeberg-test.org/ and are looking for feedback. How this works:
@codeberg going to start testing this today!
@codeberg where will be the best place to recommend changes to this feature? I assume you have a repo set up?
Cool beans. I'll test tomorrow.
@codeberg works. the content is instantly available!
Do you have a plan for repo pages? Or should one use a organization for every project that needs a website? That would be quiet complex for small projects, but maybe also a good practice?
I don't think it makes sense to commit build products (like static HTML) in the same repository as the source, like needed for github pages.
@davidak as creating a user/repo/ subpage is redundant with a dedicated repo page, we thought this would be the simpler approach.
(and having a separate pages repo wont clutter the code repo history with microcommits from the WYSIWYG editor) ...
we would like to hear your thoughts on this tho!
A question to clarify: As you consider the jekyll sources part of your project, wouldn't having the Jekyll sources in your code repo and "deploying" the generated HTML to pages be the consistent approach, giving you the benefits you are asking for?
Put differently, the pages repo is merely a compressed, versioned storage facility for efficient delivery, not so much meant for human inspection (albeit you always can!).
It is by no means intended as full replacement for the development process. Especially when compiling from higher-level markup like Jekyll or Hugo (and the user is free to pick the framework of his choice), maintaining the code in a code repo makes much more sense.
From the browser point of view, the URL hierarchy would be the same as for per-repo pages, or do you have a different layout in mind?
@josealberto4444 @codeberg yeah, that's also what i think. I usually have a source repofor my pages. An elegant technical solution is to have a CI that builds and deploys it to a server. Codeberg could just offer free webspace for static sites with SSH, SFTP and WEBDAV access. But like i said, there is https://neocities.org/ for that. When codeberg would have a CI, it could support publishing the site with it to a separate server. GitLab probably does it this way (i havn't used that).
@davidak :) hehe, nice try!
Please also have a look at the implementation and let us know if you can imagine any possible exploits: https://codeberg.org/Codeberg/build-deploy-gitea/src/branch/master/var/www/pages/index.php
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!