#56 Init georchestra doc format#57
Merged
Gaetanbrl merged 3 commits intogeorchestra:mainfrom Feb 20, 2026
Merged
Conversation
Member
|
nice ! do we need all the boilerplate sample pages/images that aren't filled with actual content ? |
Contributor
Author
Which ones ? @landryb |
Contributor
Author
|
ok i get it. I can clean useless ressources. |
fd46972 to
45d3d82
Compare
Contributor
Author
|
@landryb this PR is ready after this changes :
|
Member
|
looks great ! i guess @MaelREBOUX will need to do some work to integrate that into https://docs.georchestra.org, and @f-necas for the review ? i had a quick look and didn't spot anything.. maybe for 'useLegacyHeader' we should say 'to keep using the legacy header' for clarity ? |
Contributor
Author
|
Done @landryb ;) |
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR provides documentation using the https://github.com/georchestra/georchestra_documentation_template
format.
The content mainly details the configuration.
I think the “How to install with georchestra” section should be expanded at a later stage, but this PR already makes it possible to have cleaner, more user-friendly documentation.
So, this provides a documentation baseline to build something more complete and polished.
The build and deployment process (via GitHub Pages, I assume) will need to be set up later (configuration still to be done?).