Document how to use Codeberg Pages #27

lhinderberger commented 2020年08月13日 13:05:03 +02:00

We should add a section on how to use Codeberg Pages and link to it from pages.codeberg.org

We should add a section on how to use Codeberg Pages and link to it from pages.codeberg.org

lhinderberger commented 2020年10月05日 01:01:13 +02:00

I think this should be the next section to focus on, because currently, there's not even a link to pages.codeberg.org from the Codeberg site, which makes this very nice service a bit hard to find in the beginning.

I think this should be the next section to focus on, because currently, there's not even a link to pages.codeberg.org from the Codeberg site, which makes this very nice service a bit hard to find in the beginning.

lhinderberger commented 2020年10月05日 01:02:04 +02:00

Also, it might be worth losing a few words about it in the Getting Started section.

Also, it might be worth losing a few words about it in the Getting Started section.

hw commented 2020年10月06日 08:40:31 +02:00

We need to finally launch <username>.codeberg.eu subdomain support on codeberg main.

We need to finally launch `<username>.codeberg.eu` subdomain support on codeberg main.

lhinderberger commented 2020年10月07日 17:49:09 +02:00

See also #95, which gives information about the new codeberg.page domain and the future of pages.codeberg.org.

See also #95, which gives information about the new codeberg.page domain and the future of pages.codeberg.org.

lhinderberger commented 2020年10月07日 17:52:29 +02:00

@hw - With codeberg.page launched, what will be the fate of codeberg.eu?

@hw - With codeberg.page launched, what will be the fate of codeberg.eu?

hw commented 2020年10月07日 18:16:02 +02:00

It is still linked to codeberg-test, so that everything can be tested there, too (including fonts delivery, badges, etc).

We discovered the .page TLD only late, but it seems a much better fit from the perspective of the casual user. Still, knowing that .eu is administered in our jurisdiction, is soothing. (Still, we might not want to signal that codeberg is a EU-only affair, even if we have a strong focus here?). Depending on general feedback we might:

• run it in parallel to .page, and leave the choice to the user what to publish,
• keep it as testing domain and fallback if ever needed.

If there are any preferences please all raise your voice, if appropriate we will organize a poll for decision.

It is still linked to codeberg-test, so that everything can be tested there, too (including fonts delivery, badges, etc). We discovered the .page TLD only late, but it seems a much better fit from the perspective of the casual user. Still, knowing that .eu is administered in our jurisdiction, is soothing. (Still, we might not want to signal that codeberg is a EU-only affair, even if we have a strong focus here?). Depending on general feedback we might: - run it in parallel to .page, and leave the choice to the user what to publish, - keep it as testing domain and fallback if ever needed. If there are any preferences please all raise your voice, if appropriate we will organize a poll for decision.

hw commented 2020年10月08日 10:06:01 +02:00

Please also see Codeberg/Community#303

Please also see https://codeberg.org/Codeberg/Community/issues/303

hjacobs commented 2020年10月14日 21:12:19 +02:00

I just today discovered that https://codeberg.page/ exists, so yes, documentation would be great :-)

I just today discovered that https://codeberg.page/ exists, so yes, documentation would be great :-)

lhinderberger commented 2020年10月14日 21:13:15 +02:00

Contributions are super welcome :)

Contributions are super welcome :)

hjacobs commented 2020年10月14日 21:24:03 +02:00

First attempt: #98

First attempt: https://codeberg.org/Codeberg/Documentation/pulls/98

lhinderberger commented 2020年10月14日 22:01:36 +02:00

With #98 merged, we now have a starting point, using which Pages can be found :)
Thank you @hjacobs!

I'll leave this issue open though, with Priority: High removed, because the next steps would be to go into greater detail about the capabilities and limitations of Pages. For beginners, it might also be a good idea to provide a tutorial and links to static site generators.

With #98 merged, we now have a starting point, using which Pages can be found :) Thank you @hjacobs! I'll leave this issue open though, with `Priority: High` removed, because the next steps would be to go into greater detail about the capabilities and limitations of Pages. For beginners, it might also be a good idea to provide a tutorial and links to static site generators.

hjacobs commented 2020年10月14日 22:25:55 +02:00

@lhinderberger awesome thanks!

@lhinderberger awesome thanks!

n commented 2021年05月14日 12:37:45 +02:00

Adding on, providing basic scripts examples for building static sites would be helpful:

• Here's the one used on the Docs: deploy.sh
• and here's one provided by @momar for the next version of pages: Comment on Codeberg/Community#410
• Build scripts for Drone: Codeberg/Community#498

Adding on, providing basic scripts examples for building static sites would be helpful: - Here's the one used on the Docs: [deploy.sh](https://codeberg.org/Codeberg/Documentation/src/branch/master/deploy.sh) - and here's one provided by @momar for the next version of pages: [Comment on Codeberg/Community#410](https://codeberg.org/Codeberg/Community/issues/410#issuecomment-198362) - Build scripts for Drone: Codeberg/Community#498

Ghost commented 2022年12月24日 11:01:09 +01:00

We have a pages documentation nowadays at https://docs.codeberg.org/codeberg-pages/

But afaik it is outdated as the "new" pages implementation does not need a pages repo anymore - but this should be handled in a separate issue, maybe #51

We have a pages documentation nowadays at https://docs.codeberg.org/codeberg-pages/ But afaik it is outdated as the "new" pages implementation does not need a `pages` repo anymore - but this should be handled in a separate issue, maybe #51

fnetX commented 2022年12月24日 16:01:28 +01:00

IMHO, we should document the pages server behaviour at codeberg.page (e.g. long onepager or subsections there).

It's really hard to keep up2date with what Pages maintainers do, and they also sometimes don't know what their services does and break existing features. IMHO they should take over the responsibility for maintaining proper docs. Also, many users are confused and don't look at the docs.

IMHO, we should document the pages server behaviour at codeberg.page (e.g. long onepager or subsections there). It's really hard to keep up2date with what Pages maintainers do, and they also sometimes don't know what their services does and break existing features. IMHO they should take over the responsibility for maintaining proper docs. Also, many users are confused and don't look at the docs.