docs: add and refine project documentation #41
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: McPringle/fitpub#41
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "McPringle/docs/add-project-documentation"
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?
Summary
This PR adds and restructures the repository documentation.
I noticed that the project did not have a
README.mdand that contributor-facing guidance was missing or incomplete, so I used this pass to build out the core documentation set and tighten the separation between public project information and contributor workflow.What changed
README.mdCONTRIBUTING.mdDOCKER.mdwithCONTAINERS.md.env.exampleso the available environment variables are documented more completelyIntent
The goal was to make the repository easier to understand for:
I also tried to keep the responsibilities of the files clear:
README.mdexplains what the project isCONTRIBUTING.mdexplains how to work on itCONTAINERS.mdexplains container-based deployment and operationFollow-up
I would also like to add three screenshots to the documentation:
I have not added them yet because I would first like to agree on where they should live in the repository.
Feedback wanted
I would especially appreciate feedback from @javahippie on:
(my suggestion:
docs/screenshots/)View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.