Skip to content

Commit

Permalink
Add furl image
Browse files Browse the repository at this point in the history
  • Loading branch information
PEZ committed Jul 21, 2021
1 parent 87a7e28 commit 342b769
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -107,15 +107,15 @@ Also: Congratulations! Now take on the next problem!
#### Stuck?
The `#4clojure`, `#beginners` and `#clojure` channels at the Cljurian's Slack might be places to ask for hints. You might try the [Discussions](https://github.com/PEZ/rich4clojure/discussions) feature. Also: _Each problem has a **gist** linked at the bottom._ The gist's comment section might contain solutions from other users. Sometimes a peek is enough to give some guidance. But, yeah, major **spoiler alert**.
The `#4clojure`, `#beginners` and `#clojure` channels at the [Clojurian's Slack](http://clojurians.net/) might be places to ask for hints. You might try the [Discussions](https://github.com/PEZ/rich4clojure/discussions) feature. Also: _Each problem has a **gist** linked at the bottom._ The gist's comment section might contain solutions from other users. Sometimes a peek is enough to give some guidance. But, yeah, major **spoiler alert**.
## What about the name?
The name, **Rich 4Clojure**, comes from the fact that it relies on [Rich Comments](https://calva.io/rich-comments/) and also uses a test utillity called [RCF](https://github.com/hyperfiddle/rcf) which is building on the same philosophy. (Also reading it like ”rich forclosure” builds on the joke that the original site was pulling. 😄)
## Work in progress
This is the first version from a quite automated translation of the orginal problems. There'll be dragons. Please consider filing issues, starting [discussions](https://github.com/PEZ/rich4clojure/discussions), or chat me up on the Clojurian's Slack.
This is the first version from a quite automated translation of the orginal problems. There'll be dragons. Please consider filing issues, starting [discussions](https://github.com/PEZ/rich4clojure/discussions), or chat me up on the [Clojurian's Slack](http://clojurians.net/) (I'm **@pez**, there).
PR:s are also welcome. If it is the content of a particular problem you want to suggest changes for, edit the `problems.edn` file.
Expand Down
Binary file added rich4clojure-header.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit 342b769

Please sign in to comment.