Discussion: Project Name

[SachaG]

I've heard from some people that "GraphQL Rules" as a name can feel a bit too strict and rigid, and I fear some people might be unwilling to contribute because they feel GraphQL shouldn't have "rules" beyond what's in the spec.

Maybe renaming the project to "GraphQL Patterns" would make it clearer that those patterns are suggestions and best practices more than absolute rules?

There is already a podcast called GraphQL Patterns by @Nader3 but maybe he wouldn't mind letting us share the same name?

[RIP21]

Feel the same. @nodkz what do you think on that and other suggestions? :)

[nodkz]

We chose among the following names:

• graphql-rules.org (Suggested by Makar Stetsenko)
• graphql-patterns.org
• graphql-standard.org
• graphql-style-guide.org (Suggested by Mikhail Novikov. BTW he declined rules and standard as rigid and not polite too)

I very like graphql-patterns.

[SachaG]

I know we haven't settled on a name yet, but I was playing around with an idea I had for "GraphQL Patterns":

[nodkz]

Logo: 🤔
FontFamily: 👍
For example, if we get just the logo for stickers it will be lost.

Maybe we keep GraphQL logo with borders? Something like:

PS. For other issues, I need to take more time to answer. Cannot find a quiet place where no one will bother me ;)

[SachaG]

I think stickers would work as long as we have a white background. But yeah I can try different things.

[SachaG]

I asked Nader directly and he said he didn't mind sharing the name. Personally I think it could be cool to link to the podcast from the site if both have the same name, since both cover the same topics. Maybe build a big "GraphQL Patterns" family of resources :) But I'll leave it to you guys to figure this part out.

[nodkz]

@SachaG so good news. 👍

When backend with authorization and like/dislike mechanics will be ready for rules I'll start migrating to the new name. I think it'll take couple of weeks.