Rikki

Woohoo 🎉 It's nice to see this become public after a long time being an internal tool.
Given one of the big selling points is the type system, it would make sense for you to include the type of each field in the documentation. Personally I wouldn't even bother hand-rolling documentation - let a tool parse the schema and just make the output available to developers (and include docs on using Graphiql GUI tool too). The docs you've put together are losing the inherent relationships that GraphQL has; I think it'd be frustrating to use them as a reference (for example, here's the query to get a club, but it doesn't tell you what fields are returned, what types they are, if they have sub-fields etc.)
When I worked on customer sites at IPS I spent a lot of effort trying to query stuff in Pages blocks using raw PHP blocks and the IPS framework. Being able to write a GraphQL query to fetch everything I needed would have been great.

Woohoo 🎉 It's nice to see this become public after a long time being an internal tool.
Given one of the big selling points is the type system, it would make sense for you to include the type of each field in the documentation. Personally I wouldn't even bother hand-rolling documentation - let a tool parse the schema and just make the output available to developers (and include docs on using Graphiql GUI tool too). The docs you've put together are losing the inherent relationships that GraphQL has; I think it'd be frustrating to use them as a reference (for example, here's the query to get a club, but it doesn't tell you what fields are returned, what types they are, if they have sub-fields etc.)
When I worked on customer sites at IPS I spent a lot of effort trying to query stuff in Pages blocks using raw PHP blocks and the IPS framework. Being able to write a GraphQL query to fetch everything I needed would have been great.

Unless it has changed since I worked on this, I think one really important thing to call out is the GraphQL API respects permissions. The REST API treats requests as admin requests (unless you specifically use the OAuth flow to get a token). The GraphQL API uses the logged in member. So you can query a list of topics and it'll be accurate for that member, which is really handy.

Woohoo 🎉 It's nice to see this become public after a long time being an internal tool.
Given one of the big selling points is the type system, it would make sense for you to include the type of each field in the documentation. Personally I wouldn't even bother hand-rolling documentation - let a tool parse the schema and just make the output available to developers (and include docs on using Graphiql GUI tool too). The docs you've put together are losing the inherent relationships that GraphQL has; I think it'd be frustrating to use them as a reference (for example, here's the query to get a club, but it doesn't tell you what fields are returned, what types they are, if they have sub-fields etc.)
When I worked on customer sites at IPS I spent a lot of effort trying to query stuff in Pages blocks using raw PHP blocks and the IPS framework. Being able to write a GraphQL query to fetch everything I needed would have been great.

Woohoo 🎉 It's nice to see this become public after a long time being an internal tool.
Given one of the big selling points is the type system, it would make sense for you to include the type of each field in the documentation. Personally I wouldn't even bother hand-rolling documentation - let a tool parse the schema and just make the output available to developers (and include docs on using Graphiql GUI tool too). The docs you've put together are losing the inherent relationships that GraphQL has; I think it'd be frustrating to use them as a reference (for example, here's the query to get a club, but it doesn't tell you what fields are returned, what types they are, if they have sub-fields etc.)
When I worked on customer sites at IPS I spent a lot of effort trying to query stuff in Pages blocks using raw PHP blocks and the IPS framework. Being able to write a GraphQL query to fetch everything I needed would have been great.

Unless it has changed since I worked on this, I think one really important thing to call out is the GraphQL API respects permissions. The REST API treats requests as admin requests (unless you specifically use the OAuth flow to get a token). The GraphQL API uses the logged in member. So you can query a list of topics and it'll be accurate for that member, which is really handy.

Unless it has changed since I worked on this, I think one really important thing to call out is the GraphQL API respects permissions. The REST API treats requests as admin requests (unless you specifically use the OAuth flow to get a token). The GraphQL API uses the logged in member. So you can query a list of topics and it'll be accurate for that member, which is really handy.

Woohoo 🎉 It's nice to see this become public after a long time being an internal tool.
Given one of the big selling points is the type system, it would make sense for you to include the type of each field in the documentation. Personally I wouldn't even bother hand-rolling documentation - let a tool parse the schema and just make the output available to developers (and include docs on using Graphiql GUI tool too). The docs you've put together are losing the inherent relationships that GraphQL has; I think it'd be frustrating to use them as a reference (for example, here's the query to get a club, but it doesn't tell you what fields are returned, what types they are, if they have sub-fields etc.)
When I worked on customer sites at IPS I spent a lot of effort trying to query stuff in Pages blocks using raw PHP blocks and the IPS framework. Being able to write a GraphQL query to fetch everything I needed would have been great.

Unless it has changed since I worked on this, I think one really important thing to call out is the GraphQL API respects permissions. The REST API treats requests as admin requests (unless you specifically use the OAuth flow to get a token). The GraphQL API uses the logged in member. So you can query a list of topics and it'll be accurate for that member, which is really handy.

This is really well executed. I especially like the implementation of online events, and the month selector. Really well done.
P.S:
The "Search Events" panel has too much padding The date display in the top-left corner of the larger event block also has too much padding. Although I see why you did it this way (so it's inline with the content in it), it looks wrong compared to the smaller blocks below it where it is actually in the corner. It's also not inline with its content in the smaller block. You should push it to the corner but make it bigger in the larger block. The filters on the map view need some tidying: "Back" / "Sort By" buttons butt up against the controls above, which are unevenly spaced, and the top of the "Search" button is misaligned with the top of the labels. Visiting the Calendar probably shouldn't prompt the user to provide their geolocation until they interact with something. Sorry, I couldn't help myself.

This I think will be really useful, putting further limelight on a feature that is central to why members visits - or not - a Q&A-oriented community.
Something to consider about the statistics offered could be to complement with a basic way to show the spread of time to solution (e.g. the standard deviation). This would show if the time to solution in a forum is similar for most questions (like the fictive forum being red in the picture), or if some come members get answers with the speed of light and some have to wait painfully long (blue).
A measure of spread could indicate if there is an imbalance between the answers needed by members and the answers provided within specific knowledge areas. Combined with a way to identify the posts in the statistics shown (maybe the search function will do the trick) this could trigger rewarding actions to close this gap, increasing member satisfaction and strengthening the community brand. 
Posts never being marked as solved could be treated similarly, being able to identify and analyze so that appropriate action may be taken.
I'll add this idea to the Feature Suggestions forum when we have used the solution for a while.
 
 

Figure: Same mean value to solution but different spread.

Deja Vu.
Come into blog entry, see this in the comments:

Leave again.
 

As my own forum was created in 1999 and has been in IP for the vast majority of that it has been a great journey. 

To be honest I only need to return here these days when things go wrong and then I realise I have lapsed..... 

So $150 on its way, despite the fact that I only use the forums and can't not renew the other elements. I am not even sure if I could swap it to one of my fifteen unused licences!! 

Just one question @Matt - where is cleancut? 🤣  

We have helped dozens of new and existing communities in the past few years. Not to mention all the hundreds or thousands who use us but don't work with us directly.
You need to offer value to users, and you need to market the community to present that value to them. Social media has a leg up on the second one because the users are already there, but there is no reason why an independent site (whether it's a 'forum based community' as you put it, or any other kind of community) cannot also be successful. There are many thousands of successful sites out there, so if a site doesn't succeed it cannot really be blamed on the tech giants. Either you didn't offer enough value, or you were unable to get it seen by the right people.
It's a bit weird to measure your success in terms of number of members vs. Facebook. Measure your success in something more meaningful to your site. Is it providing value to people, is it covering its own costs, is it growing? A small community site with 100 people can absolutely be counted as a success if it has achieved its goals.

We have helped dozens of new and existing communities in the past few years. Not to mention all the hundreds or thousands who use us but don't work with us directly.
You need to offer value to users, and you need to market the community to present that value to them. Social media has a leg up on the second one because the users are already there, but there is no reason why an independent site (whether it's a 'forum based community' as you put it, or any other kind of community) cannot also be successful. There are many thousands of successful sites out there, so if a site doesn't succeed it cannot really be blamed on the tech giants. Either you didn't offer enough value, or you were unable to get it seen by the right people.
It's a bit weird to measure your success in terms of number of members vs. Facebook. Measure your success in something more meaningful to your site. Is it providing value to people, is it covering its own costs, is it growing? A small community site with 100 people can absolutely be counted as a success if it has achieved its goals.

We have helped dozens of new and existing communities in the past few years. Not to mention all the hundreds or thousands who use us but don't work with us directly.
You need to offer value to users, and you need to market the community to present that value to them. Social media has a leg up on the second one because the users are already there, but there is no reason why an independent site (whether it's a 'forum based community' as you put it, or any other kind of community) cannot also be successful. There are many thousands of successful sites out there, so if a site doesn't succeed it cannot really be blamed on the tech giants. Either you didn't offer enough value, or you were unable to get it seen by the right people.
It's a bit weird to measure your success in terms of number of members vs. Facebook. Measure your success in something more meaningful to your site. Is it providing value to people, is it covering its own costs, is it growing? A small community site with 100 people can absolutely be counted as a success if it has achieved its goals.

We have helped dozens of new and existing communities in the past few years. Not to mention all the hundreds or thousands who use us but don't work with us directly.
You need to offer value to users, and you need to market the community to present that value to them. Social media has a leg up on the second one because the users are already there, but there is no reason why an independent site (whether it's a 'forum based community' as you put it, or any other kind of community) cannot also be successful. There are many thousands of successful sites out there, so if a site doesn't succeed it cannot really be blamed on the tech giants. Either you didn't offer enough value, or you were unable to get it seen by the right people.
It's a bit weird to measure your success in terms of number of members vs. Facebook. Measure your success in something more meaningful to your site. Is it providing value to people, is it covering its own costs, is it growing? A small community site with 100 people can absolutely be counted as a success if it has achieved its goals.

I think I bought Invision Board (Wasn't it called Invision Power Board)? in that first year.
I intended to create the number one websites and communities about the Republic of Turkey. And I didn't want to go with one of the free boards. I wanted The Cadillac of forums. Even in that first year I could see that Invision Power Board was the best. So I bought it and installed it and have been using it ever since.
It didn't have the capacity for articles. Or for a directory like Yahoo. So I created them myself. They didn't talk to Invision Board. My site was kind of a mess. Then Invision added Content. Which solved my problem. I bought that and transferred all of my articles into Invision Content.
Then Facebook came along. It was killing me.
But Facebook has a profound weakness. It doesn't handle complex content. Invision Community does. So instead of Facebook ruining my life, I now exploit it. Often there are questions on Facebook requiring a complex answer. I reply, but then link to my Invision Community article which explains everything.
I now have a separate site about Turkish residence permits. Lots of articles and a forum, among other things.
Looking back I think buying and installing Invision Board was one of the best decisions I've made.
Your support is fantastic. Very polite and professional. Even if I have what I later find was a dumb question, your support staff helps me, even walks me through things.
I was with you from the beginning and I will be with you to the end.
Thanks to all of you at Invision Community. You are still the "Cadillac" of communities.
Ken Grubb
TurkeyCentral.com
TurkeyPermit.com