Api Days Singapore Blog #2397
Conversation
|
@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. |
|
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. |
|
@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. |
|
@jemgillam sounds good to me. Suggestion to rename the tag to As a reader, I want to be able to filter on content. Just as I wouldn't do a |
|
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. |
We have
Not sure if it's new but agreed we probably don't need it. |
…gapore.mdx Co-authored-by: Jem <[email protected]>
…gapore.mdx Co-authored-by: Jem <[email protected]>
…gapore.mdx Co-authored-by: Jem <[email protected]>
…gapore.mdx Co-authored-by: Jem <[email protected]>
|
Hello @jemgillam |
|
@Akshat111111 It is still failing on a lint rule, but don't make any changes @benjie any insight into why suddenly articles can't skip an H1 title? Many many other articles have been written skipping straight to using H2. What do we need to change? |
| date: 2026-05-04 | ||
| byline: "Akshat" | ||
| --- | ||
| > The following report was written by Ambassador |
There was a problem hiding this comment.
I think ESLint is demanding this maybe:
| > The following report was written by Ambassador | |
| # From Learning GraphQL to Representing it at API Days Singapore | |
| > The following report was written by Ambassador |
But also, this file is in the root of the repository which is the wrong location for it. Try moving it first and if that doesn't solve it you might need to add the H1.
There was a problem hiding this comment.
Ah, no doubt moving the files to their correct location will fix the lint issue, I didn't spot they were just in the root!
Added my experience of API Days Singapore as a blog.