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

A static website for Codeberg Documentation #20

Merged
hw merged 1 commit from :master into master 2022年03月24日 22:16:15 +01:00
Contributor
Copy link

This pull request contains a basic static website generated from the markdown source files of Codeberg's Documentation.

I have copied the original documentation pages almost verbatim, sorting them into the menu structure of the codeberg-docs-prototype.

Its current state (with an adapted footer and source URL) can be tested here: https://cb-docs-prototype.lhinderberger.com

Closes #17

This pull request contains a basic static website generated from the markdown source files of Codeberg's Documentation. I have copied the original documentation pages almost verbatim, sorting them into the menu structure of the codeberg-docs-prototype. Its current state (with an adapted footer and source URL) can be tested here: https://cb-docs-prototype.lhinderberger.com Closes #17
Author
Contributor
Copy link

@hw This would be ready to be pulled and/or deployed to codeberg-test (for example docs.codeberg-test.org).

@hw This would be ready to be pulled and/or deployed to codeberg-test (for example docs.codeberg-test.org).
Owner
Copy link

give us a few days, then it should be live on codeberg-test ;)

give us a few days, then it should be live on codeberg-test ;)
Author
Contributor
Copy link

What do you think, should I try to integrate the new color palette (Codeberg/Design#2) into this pull request or do that after it has been merged and make a new pull request then?

I would tend to the latter, to keep concerns separated (also for other Issues like #24 or #26).

What do you think, should I try to integrate the new color palette (Codeberg/Design#2) into this pull request or do that after it has been merged and make a new pull request then? I would tend to the latter, to keep concerns separated (also for other Issues like #24 or #26).
Owner
Copy link

You can use the "dependency" feature on the right panel to link PRs

You can use the "dependency" feature on the right panel to link PRs
Author
Contributor
Copy link

I'm afraid I can't edit the dependencies field, probably because I'm lacking permissions.

I'm afraid I can't edit the dependencies field, probably because I'm lacking permissions.
hw merged commit 18d78c22a1 into master 2020年08月19日 21:03:07 +02:00
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
2 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!20
Reference in a new issue
Codeberg/Documentation
No description provided.
Delete branch ":master"

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?