LispCookbook / LispCookbook/cl-cookbook

Updated books

Open
#557 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1.1k
Forks
158
Avg merge
6d 3h
Merged PRs (30d)
2

Description

I noticed the books section could be expanded with a lot more entries, do you think it'd be worthwhile to do so? Are there any kind of criteria you think there should be, like mostly available to read freely online (would exclude *Common Lisp Recipes*), or one book per author (so having to pick between keeping PG's *On Lisp* vs. his more complete *ANSI Common Lisp*), or only English (ruling out linking to the Japanese *Survival Common Lisp*), or mostly about introducing Lisp the language (so not more subject-specific books like phoe's on the condition system or *Land of Lisp* or a handful of others on webdev/calendars/AI/...)?

I kind of like the self-promotion going on with the udemy course, I'm wondering if it'd be good to use the cookbook home page to further promote book authors. A lot of Lisp books not linked are easy enough to find, but a lot aren't, e.g. I don't think many people have noticed or read something like the very focused [Common Lisp in the Wild - Deploying Common Lisp Applications](https://www.darkchestnut.com/book-common-lisp-application-deployment/) ebook, but I quite enjoyed it. We once briefly talked about something similar though on how there's a line between linking to too much (like blog posts and perhaps small ebooks like that one) when that content could better just be in the cookbook directly. A possible cookbook addition might be a page with code usage notes or notes on how "dated" sections of particular books are. For example, with *Land of Lisp*, which isn't linked either, I could write a few notes on running some of the examples in a modern SBCL. Or with that mentioned ebook, it uses Buildapp, which is fine though as the [cookbook briefly notes](https://lispcookbook.github.io/cl-cookbook/scripting.html#with-roswell-or-buildapp) not necessarily the best option anymore.

(Additionally, what initially spawned thinking about this issue, I noticed and was going to fix a deadlink for *Successful Lisp*. A functioning one is hosted by [strandh](https://dept-info.labri.fr/~strandh/Teaching/MTP/Common/David-Lamkins/contents.html)...)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the books section and the cookbook homepage, including the existing Successful Lisp link and the scripting.html notes on Roswell or Buildapp. The issue needs agreement on inclusion criteria, promotion, and whether book usage notes belong in the cookbook before any concrete documentation change can be defined.

Written by the indexing model from the issue text.

Assessment

Domain
content, documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.