WIP: Hugo generated site for documentation #13

Closed
n wants to merge 4 commits from wiki-hugo-website into master
n commented 2 years ago
Collaborator

Forked from gitea/docs and gitea/theme (docs.gitea.io).

  • Fix images
  • Fix search
  • Cleanup theme
  • Cleanup readme
  • Cleanup articles from gitea/docs
  • Remove dependency on Google Fonts
  • Remove dependency on Cloudflare cdnjs
Forked from [gitea/docs](https://gitea.com/gitea/docs) and [gitea/theme](https://gitea.com/gitea/theme) ([docs.gitea.io](https://docs.gitea.io/en-us/)). - [ ] Fix images - [ ] Fix search - [x] Cleanup theme - [ ] Cleanup readme - [ ] Cleanup articles from [gitea/docs](https://gitea.com/gitea/docs) - [x] Remove dependency on Google Fonts - [ ] Remove dependency on Cloudflare cdnjs
Owner

nice! 115 files seems somewhat large tho at this stage .. are generated files also in the PR? (or is this the generated content that should go into pages repo? Do you have a preview set up in your account/org?)

nice! 115 files seems somewhat large tho at this stage .. are generated files also in the PR? (or is this the generated content that should go into pages repo? Do you have a preview set up in your account/org?)
n commented 2 years ago
Poster
Collaborator

nice! 115 files seems somewhat large tho at this stage .. are generated files also in the PR? (or is this the generated content that should go into pages repo? Do you have a preview set up in your account/org?)

Nope, this is just the source. I've uploaded the generated content to n/pages.
Here's a preview: https://pages.codeberg.org/n/codeberg-docs/en-us/

> nice! 115 files seems somewhat large tho at this stage .. are generated files also in the PR? (or is this the generated content that should go into pages repo? Do you have a preview set up in your account/org?) Nope, this is just the source. I've uploaded the generated content to [n/pages](https://codeberg.org/n/pages). Here's a preview: https://pages.codeberg.org/n/codeberg-docs/en-us/
Owner

nice! Keep us updated!

nice! Keep us updated!
Owner

related: #7

related: https://codeberg.org/Codeberg/Documentation/issues/7#issuecomment-72090

@n I've got some time to spare and could help completing this, if my help is needed.

@n I've got some time to spare and could help completing this, if my help is needed.
Owner

Every contribution welcome!

In general: early merge (despite marked as WIP) helpful or rather branch from PR?

Every contribution welcome! In general: early merge (despite marked as WIP) helpful or rather branch from PR?

In general: early merge (despite marked as WIP) helpful or rather branch from PR?

If that's a question for me 😅: I would prefer having this on a separate branch while it is still a Work in Progress.

But in the end it largely depends on @n's preference: If they prefer to work on this on their own, I would respect that. And in case @n wouldn't want to continue the docs using this approach, I would find it much more fun to use Eleventy and design from scratch 😉

> In general: early merge (despite marked as WIP) helpful or rather branch from PR? If that's a question for me 😅: I would prefer having this on a separate branch while it is still a Work in Progress. But in the end it largely depends on @n's preference: If they prefer to work on this on their own, I would respect that. And in case @n wouldn't want to continue the docs using this approach, I would find it much more fun to use Eleventy and design from scratch 😉
n commented 2 years ago
Poster
Collaborator

But in the end it largely depends on @n's preference: If they prefer to work on this on their own, I would respect that. And in case @n wouldn't want to continue the docs using this approach, I would find it much more fun to use Eleventy and design from scratch 😉

I sort of abandoned this approach since the theme I forked was too complex. I tried using MkDocs since but haven't really worked on it much 😅.

A minimal static site made using Eleventy would surely suit our needs better.

I will close this pull request. I look forward to seeing your work!

> But in the end it largely depends on @n's preference: If they prefer to work on this on their own, I would respect that. And in case @n wouldn't want to continue the docs using this approach, I would find it much more fun to use Eleventy and design from scratch 😉 I sort of abandoned this approach since the theme I forked was too complex. I tried using MkDocs since but haven't really worked on it much 😅. A minimal static site made using Eleventy would surely suit our needs better. I will close this pull request. I look forward to seeing your work!
n closed this pull request 2 years ago

I feel honored, and I'll start right away. :)

I will grow the prototype in https://codeberg.org/lhinderberger/codeberg-docs-prototype and will make a pull request here once #15 has been decided on.

I feel honored, and I'll start right away. :) I will grow the prototype in https://codeberg.org/lhinderberger/codeberg-docs-prototype and will make a pull request here once #15 has been decided on.
This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
No reviewers
No Milestone
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Codeberg/Documentation#13
Loading…
There is no content yet.