The PJRC website is far from ideal, and that's all my fault. Well, except for the relatively new blog section. Robin deserves the credit for making a blog post every other day to show someone's project. Everything else on the site it my doing.
Most of these matters really are documented on the website. But just because they exist *somewhere* doesn't necessarily mean beginners (or even experts) can find them. For example, the SPI pins and SPI library usage are explained here:
https://www.pjrc.com/teensy/td_libs_SPI.html
For years we've been planning to massively redesign the website. We've also been planning to migrate this forum from vbulletin to xenforo. I've also long planned a number of software features, some partially implemented and perpetually "experimental" (like EventResponder), others so far untouched (like native Ethernet on Teensy 3.5 & 3.6), and still more pretty well implemented not yet documented beyond library examples & readme files (like USBHost_t36 & WS2812Serial).
The harsh reality is there are never enough hours & funding to do everything.
The other reality of websites & documentation in general, which is becoming a bigger issue as 32 bit microcontrollers become ever more capable, is how to make the right info discoverable when there are so many topics & details to cover.
My optimistic hope is to spend serious time on the website after Teensy 4 is released. Realistically, there will be several months of fairly urgent software work to do, since we're switching to a completely new chip. PJRC is probably also going to have to make at least 1 or 2 other very similar products, and a few more accessory shields... all of which will eat up precious time. If we don't focus our effects first on keeping Teensy competitive in the crowded market for dev boards & tools, then there won't be any viable business model to keep all this going. Even the very best case scenario is looking like 2020 before really serious work can happen on redesigning the website.
Another huge ongoing challenge, which I believe we're also seeing manifest in this thread, is how to encourage beginners to ask effective questions. Recently I wrote
this article and made this graphic... as the first step in a long-planned process. Eventually we're going to replace the "Forum Rule" with some version of this, and revamp how we communicate with customers throughout the sale process (and maybe try to affect similar changes with the many distributors), and, well... I still don't know all the answers, but somehow we've just got to get this message across to people *before* they ask for help:
I believe it's fair to say, in this particular case, things have gone off the rails on all 3 of these.
The last thing I want to do is deny the website needs work. It does. These complaints about lack of documentation, even if they're technically incorrect, are indeed valid in a practical sense if the information isn't discoverable.
But in terms of making a good first impression, well, maybe venting this frustration with the website isn't the best way to get help with a specific problem.
Likewise, to actually help you get that Adafruit display working, we need to know details. Which specific product and how you've actually connected the wires is the bare minimum. A photo of the connections is usually needed. I see you already started a
thread about the display problem. Like the website, your post is far from ideal. I'm going to comment on it right now. Let's focus on getting your display issue solved. Eventually I will redesign the website, but that's going to come much farther in the future...