This contains the source for https://contribute.liquibase.com, written using https://squidfunk.github.io/mkdocs-material/
- The
docsdirectory contains the main content for the site - The
overridesdirectory contains custom template configurations - The
snippetsdirectory contains reusable documentation blocks
The fastest way to contribute changes is to use the "How was your experience?" button on the bottom of each page. This let you suggest changes directly from your browser, and they will be reviewed by the team.
Suggestions can range from simple "This sentence is confusing" to larger "I'm trying to understand X, and am not able to find the content I need. What I'd really like is...".
This works great for small and/or scattered suggestions
An alternative to the "feedback" button for general suggestions is to open an issue on this repository.
It's a bit more work than the feedback button, but it will be publicly visible and trackable, which allows for easier collaboration with the overall community.
On the top right of every page is a grey "Edit this Page" icon.
The button will open a web editor for the page you are on, allowing you to make changes directly in your browser. The changes you suggest will be submitted as a pull request for review.
It requires no local setup, but only allows you to include a single page's changes in your PR and you can't really see the final content as you work. That means it works well for small and/or scattered suggestions, but if you are making larger changes that cross pages and/or add significant content you will likely want to make and test the changes locally.
Your first step will be to fork this repository and clone your copy locally. Create a branch for your changes and switch to it.
- Run
docker run --rm -it -p 8080:8000 -v ${PWD}:/docs $(docker build -q .)in bash or powershell. If successful, you should seeServing on http://0.0.0.0:8000/in the output. - Open a browser to
http://localhost:8080to view the site
Edit the markdown files in the docs directory using whatever editor your prefer. Generally one with spelling and grammar check is good. Markdown syntax highlighting is helpful, but it does not need "markdown preview" support.
Each time you save a file, the site will automatically rebuild and refresh in your browser. The cycle of edit, save, refresh is very fast and works well.
Commit your changes and push them to your fork as you work.
When you are ready for the team to review your changes, open a pull request from your fork's branch to this repository's master branch.
The team will review your changes and provide feedback, and as soon as it's merged to master your changes will be live.