Justin Smith speaks the truth about Caribou. I'm also one of the team members, and although we did lose our funding, we're all still around and there are a number of active Caribou projects alive and well. It does have everything Justin says, and yes, it's imperfect, but it's also very easy to get a site up and running quickly. But you don't lose the modularity that we all love in the Clojure world. You can use just part of it (we know of numerous people using Polaris for routing, for example, and nothing else at all from the Caribou ecosystem) or all of it if you want. The CRUD UI in the admin tool is handy but a bit on the clunky side (for historical reasons which I won't go into here) but can be customised quite easily if you have a decent UI/UX person to do it. When we had our funding, we were all very invested in the project and are deeply proud of what we were able to achieve in a relatively short timespan. We also have the best URL :)
http://let-caribou.in Cheers! Kyle On Tuesday, May 5, 2015 at 8:41:51 AM UTC-7, Justin Smith wrote: > > Wow, what a thread! > > As one of the authors and designers of Caribou, I have a couple of > clarifications to offer. > > When the initial post compared contributors and commits, it picked our > "caribou" repo, which, while extensive, holds no code, only our docs. The > actual code is in caribou-core (persistence layer via edn abstraction), > polaris (routing via edn data structures), caribou-api (rest api to > caribou-core), antlers (an extended edn friendly mustache for templating), > lichen (automated caching image resizer with optional s3 integration and > stand alone http server), schmetterling (web ui for debugging exceptions, > with in frame evaluation and locals display), caribou-frontend (pulling > together core, antler, lichen, polaris and ring to make a site), and > caribou-admin (crud ui for caribou-core models, including a drag and drop > ui to define routes that can be imported by polaris). > > Caribou is not abandoned, though it did lose funding. I currently use core > plus polaris without the other components at my day job, though working on > Caribou itself is not strictly in scope for my salaried work. > > Which is to say, Caribou is very much a "modular framework" ( though much > of it does rely on the caribou-core persistence abstraction). It's > imperfect but useful, and work is slowed but not abandoned. > > I'm always always in #caribou on freenode, and we have extensive docs. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
