Skip to content

Api Days Singapore Blog #2397

Open
Akshat111111 wants to merge 8 commits intographql:sourcefrom
Akshat111111:source
Open

Api Days Singapore Blog #2397
Akshat111111 wants to merge 8 commits intographql:sourcefrom
Akshat111111:source

Conversation

@Akshat111111
Copy link
Copy Markdown

Added my experience of API Days Singapore as a blog.

@linux-foundation-easycla
Copy link
Copy Markdown

linux-foundation-easycla Bot commented May 4, 2026

CLA Signed

The committers listed above are authorized under a signed CLA.

@vercel
Copy link
Copy Markdown

vercel Bot commented May 4, 2026

@Akshat111111 is attempting to deploy a commit to the The GraphQL Foundation Team on Vercel.

A member of the Team first needs to authorize it.

@martinbonnin
Copy link
Copy Markdown
Contributor

Thanks for writing this Akshat.

I'll let others comment but my thoughts are that posts on graphql.org should be voiced as a "We", not "I". It'd be OK if this were a testimony but since this is more of a feedback from a community organized event, I'd like it better if it were written from the point of view of the team.

I don't think we have any guidelines around this though so it might be a personal thing. Whatever we decide, we should document in CONTRIBUTING.md

@Akshat111111
Copy link
Copy Markdown
Author

Thanks for writing this Akshat.

I'll let others comment but my thoughts are that posts on graphql.org should be voiced as a "We", not "I". It'd be OK if this were a testimony but since this is more of a feedback from a community organized event, I'd like it better if it were written from the point of view of the team.

I don't think we have any guidelines around this though so it might be a personal thing. Whatever we decide, we should document in CONTRIBUTING.md

Sure! Make sense.

@jemgillam
Copy link
Copy Markdown
Contributor

jemgillam commented May 5, 2026

@martinbonnin Martin, I would like to start taking articles written from Ambassadors in their own voice. I want to tag this as an Ambassador story and eventually we would have a number of them we can then spotlight in the Ambassador pages perhaps.

Comment thread 2026-05-04-learning-graphql-to-representing-it-at-api-days-singapore.mdx Outdated
Comment thread 2026-05-04-learning-graphql-to-representing-it-at-api-days-singapore.mdx Outdated
Comment thread 2026-05-04-learning-graphql-to-representing-it-at-api-days-singapore.mdx Outdated
@martinbonnin
Copy link
Copy Markdown
Contributor

martinbonnin commented May 5, 2026

@jemgillam sounds good to me. Suggestion to rename the tag to ambassador stories instead of just ambassadors.

As a reader, I want to be able to filter on content. Just as I wouldn't do a tsc or board tag. Whether the author is a TSC, board member or ambassador is useful context but not the most important one.

@jemgillam
Copy link
Copy Markdown
Contributor

I have no idea if the tag can be two words, if so then that is definitely preferred!

I noticed a lint error on the first sub heading, looking back I can see many blog posts don't have a H1 and instead start on using H2 headings. Is this lint rule new? I don't think it's needed for blog content.

@martinbonnin
Copy link
Copy Markdown
Contributor

I have no idea if the tag can be two words

We have IN THE NEWS so I'm guessing that'll work.

Is this lint rule new? I don't think it's needed for blog content.

Not sure if it's new but agreed we probably don't need it.

Comment thread 2026-05-04-learning-graphql-to-representing-it-at-api-days-singapore.mdx Outdated
Akshat111111 and others added 4 commits May 8, 2026 11:58
…gapore.mdx

Co-authored-by: Jem <6413628+jemgillam@users.noreply.github.com>
…gapore.mdx

Co-authored-by: Jem <6413628+jemgillam@users.noreply.github.com>
…gapore.mdx

Co-authored-by: Jem <6413628+jemgillam@users.noreply.github.com>
…gapore.mdx

Co-authored-by: Jem <6413628+jemgillam@users.noreply.github.com>
@Akshat111111
Copy link
Copy Markdown
Author

Hello @jemgillam
Can this be merged now??

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants