Codeberg/Documentation
44
152
Fork
You've already forked Documentation
129

WIP: Hugo generated site for documentation #13

Closed
n wants to merge 4 commits from wiki-hugo-website into master
pull from: wiki-hugo-website
merge into: Codeberg:master
Codeberg:main
Codeberg:renovate/cspell-monorepo
Codeberg:renovate/docker.io-woodpeckerci-plugin-surge-preview-1.x
Codeberg:renovate/docker.io-woodpeckerci-plugin-prettier-1.x
Codeberg:git-pages
Codeberg:pr-554
Codeberg:pr/554
Codeberg:gitea-icons-shortcode
Contributor
Copy link

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
Copy link

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?)
Author
Contributor
Copy link

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
Copy link

nice! Keep us updated!

nice! Keep us updated!
Owner
Copy link

related: #7 (comment)

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

@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
Copy link

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?
Contributor
Copy link

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 😉
Author
Contributor
Copy link

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 2020年07月28日 15:42:12 +02:00
Contributor
Copy link

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.

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
No reviewers
Labels
Clear labels
Codeberg Pages

Issues affecting Codeberg Pages
Documentation Usability

Issues related to using and reading docs.codeberg.org
Forgejo
Good First Issue! 👋
Kind: Bug
Kind: Documentation
Kind: Enhancement
Kind: Feature
Kind: Question
Kind: Security
Licensing
Part: Generator

This is related to the generation of the documentation, not to the content itself
Priority: High

The priority is high
Priority: Low

The priority is low
Priority: Medium

The priority is medium
Reviewed: Confirmed

Something has been confirmed
Reviewed: Duplicate

Something exists already
Reviewed: Invalid

Something was marked as invalid
Reviewed: Wontfix

Something won't be fixed
Status: Blocked
Status: Help wanted

Contributions are welcome!
Status: In progress

Work is in progress
Status: Needs feedback

Feedback is needed
Status: Ready for Review

Work is completed
Status: Review

Review is in progress / Reviewers wanted
Status: Stale
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Documentation!13
Reference in a new issue
Codeberg/Documentation
No description provided.
Delete branch "wiki-hugo-website"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?