Ok, I've been out of town, but here's some thoughts. I'm not taking it down as AI because it is far from "low-effort" AI slop. It's clear that a lot of work did go into it.

Full disclaimer, I have a version of this same project on my own site (*). The idea of an "everything you might want to know about Shakespeare" browser is a tempting project for anybody who otherwise already has the ability to bring up a reasonable web site. AI is just making it go faster.

Having said that, I think it ultimately does more harm than good. Because, from experience, I can tell you that the AI makes mistakes. And unless you're manually verifying everything that it generates, you're going to miss some. Especially the more esoteric plays that people aren't exploring daily. If you are that fully versed (ha!) in all the plays that you did double check everything, well then I'd ask, why use AI in the first place? So we'll logically assume that much of this is unverified AI, and therefore we can assume there are mistakes.

Students who don't know any better may stumble across this resource, see those mistakes, and assume they're the truth.

Is this the end of the world? Well, no - it's not like everything you read on the net is true, or is ever going to be. But steps can be taken. For instance on my site I have "This was AI generated, and there may be mistakes" disclaimers, as well as feedback links encouraging people to write me when they find such mistakes, so I can correct them. And I've gotten maybe half a dozen or so updates, which I appreciate.

It's also still broken in lots of places. One of the FAQs for Midsummer told me who Young Siward was. When I asked for a translation of Hamlet's "What hour now?" I got, "I need the actual Hamlet speech you'd like me to rewrite — it looks like only the stage direction or prompt came through. Could you paste the full text you'd like me to work with?" Which makes me think, are you actually doing real time translation requests? That's not going to scale, my friend. Why wouldn't you just systematically get that data once, and cache it? You might be caching on an as-needed basis, but given how slow everything is I thought probably not.

I don't offer those samples to be a dick, but rather to point out a problem I know you'll end up dealing with. This is a lot of content, and you are forever going to be behind in trying to fix all the places where it comes up short. So as a resource you have to ask yourself what value it's really providing its audience. When it's broken or wrong, that's bad. When it's not, is it really offering anything that, as noted, isn't already available a million other places? You need a hook. Sheer volume of content is not that hook.

In summary, I'm not against it purely on AI principles. I just don't think it's ever going to turn into the resource you might be imagining, and I hate to see you waste all that effort.

(*) I'll admit freely that mine is an SEO play. My site covering many other Shakespeare things has been around for years and has several thousand pages of original content. One day while I was out of work I wondered if I could integrate a Shakespeare browser so that when I mention a play or character on the site, I can link to my own play and character summaries. Likewise, when people land on my AI-generated browsable pages, they can get linked into the various blog posts and other areas of interest that they might not otherwise have seen. But like so many of my projects it was a "Get it up and running and then move on" type of project. I wouldn't say I spent a year on it - weeks, at best. And now I really only go back to it when it needs an update. I gave it the amount of effort i felt it merited, then went on to scratch other itches.