Contributing to Practicalli Clojure

practicalli/clojure is written in markdown and uses GitBook to generate the website via a GitHub action.

By submitting content ideas and corrections you are agreeing they can be used in this workshop under the Creative Commons Attribution ShareAlike 4.0 International license. Attribution will be detailed via GitHub contributors.

All content and interaction with any persons or systems must be done so with respect and within the Practicalli Code of Conduct.

Book status

GitHub commit activity Content ideas and other issues Pull requests GitHub Super-Linter GitBook publish

Submit and issue or idea

If something doesn't seem quite right or something is missing from the book, please raise an issue via the GitHub repository explaining in as much detail as you can.

Considering a Pull request?

Before investing any time in a pull request, please raise an issue explaining the situation. This can save you and the maintainer time and avoid rejected pull requests.

Please keep pull requests small and focused, as they are much quicker to review and easier to accept. Ideally PR's should be for a specific page or at most a section.

A PR with a list of changes across different sections will not be merged, it will be reviewed eventually though.

Thank you to everyone that has contributed

A huge thank you to Rich Hickey and the team at Cognitect for creating and continually guiding the Clojure language. Special thank you to Alex Miller who has provided excellent advice on working with Clojure and the CLI tooling.

The Clojure community has been highly supportive of everyone using Clojure and I'd like to especially thank Sean Corfield for all the feedback and contributions made to the community. I would also like to thank everyone that has joined in with the London Clojurians community, ClojureBridgeLondon, Clojurians Slack community, Clojurians Zulip community and Clojureverse community.

Thank you to everyone who sponsors the Practicalli websites and videos and for the recent Clojurists Together sponsorship, it helps me continue the work at a much faster pace.

Special thanks to Bruce Durling for getting me into Cloure in the first place.

GitHub contributors

results matching ""

    No results matching ""