I don't want to spend 5 minutes getting a feel for it (first link on the page) before I have some clue what it is or whether I care.
Putting one sentence of what Graphiti is on the actual homepage would help adoption enormously. "Graphiti makes RESTful Resources a first-class concept" doesn't count as an explanation of what Graphiti is. "This enables reading and writing a graph of data in a single request, a schema with backwards-compatible gaurantee, end-to-end integration test patterns, seamless microservices and much more" might be a great explanation for the developer who wrote Graphiti but doesn't ease me as a first time visitor to the site into a comfortable understanding of whether Graphiti will solve my problem.
Putting one sentence of what Graphiti is on the actual homepage would help adoption enormously. "Graphiti makes RESTful Resources a first-class concept" doesn't count as an explanation of what Graphiti is. "This enables reading and writing a graph of data in a single request, a schema with backwards-compatible gaurantee, end-to-end integration test patterns, seamless microservices and much more" might be a great explanation for the developer who wrote Graphiti but doesn't ease me as a first time visitor to the site into a comfortable understanding of whether Graphiti will solve my problem.