Hey @AkashRajpurohit could you please take a look at the new content portion?

I decided to use alternativeAnswers for question #40. The original question 'I am getting underpaid for what my role has evolved into?' sounds similar, but let me know if you'd like to split them? Also, questions #17and#46` could be grouped on the "micromanaging" subject.

Regards, Eugene

I recommend (for performance reasons) to optimize fonts and serve modern format.

I wrote a little bit on th subject here: https://pavelloz.com/blog/google-fonts-optimization/

Is your feature request related to a problem? Please describe. Expanding question is currently reliant on JavaScript. With JavaScript disabled, there is no way to read the answers. (Besides sifting through source code.)

Describe the solution you'd like Page should be served as accessible static HTML document with both question and answers accessible straight away. Only the "filter" feature should be client-side progressive enhancement not present in the static payload. The "reveal" feature could be done either using native <details><summary>Question</summary>Answer</details>[...] HTML structure with no need of client-side scripting, or with static description list (<dl><div><dt>Question</dt><dd>Answer</dd></div>[...]</dl>) progressively enhanced to interactive button toggle ("accordion") structures similar to current one.

Describe alternatives you've considered "Robust" alternative with true answer reveal without client-side JavaScript would require either server-side scripting, presumably stateful (what seems a bit over-engineered, but perhaps Vercel could do that in meaningful manner?), or CSS label&checkbox hack (what is not optimal from accessibility perspective and has similar issues to JavaScript-only approach).

Additional context Must praise otherwise quite accessible approach; current version works well with keyboard. Haven't tested screen readers but seeing reasonable aria attributes gives hope it was thought-out. Inline SVGs should be hidden from the tree, though.

"As per my prediction, this outcome does not come as a surprise."

As a native English speaker, this sentence sounds very unnatural. It is a "dangling modifier" (or similar); it sounds like the prediction you made was that the outcome would not be a surprise. But in fact you're trying to say that you predicted the outcome.

Better alternatives include:

• "This outcome does not come as a surprise."
• "This outcome agrees with my earlier prediction."
• "Seeing as it agrees with my earlier prediction, this outcome is not a surprise."

Life got in a way, but here it is :)

I didnt remove the old fonts, just because you might want to create a different subset in the future - good to have source file.

Below you have the ls to compare sizes. Im pretty happy with the results. 309 KB -> 15 KB should be visible on non-fiber connections.

Inter font

 51K Inter-Bold-subset.ttf
 15K Inter-Bold-subset.woff2
309K Inter-Bold.ttf

 51K Inter-Medium-subset.ttf
 15K Inter-Medium-subset.woff2
307K Inter-Medium.ttf

 50K Inter-Regular-subset.ttf
 14K Inter-Regular-subset.woff2
303K Inter-Regular.ttf

DancingScript font

45K DancingScript-Medium-subset.ttf
22K DancingScript-Medium-subset.woff2
79K DancingScript-Medium.ttf

Enjoy :)

As we are seeing that the data source is increasing, this feature will allow users to add their own favorites and toggle selectively toggle to view the favorites only.

The data for favorites would be stored in the user's localStorage hence the favorites won't be accessible on different browser.

Hello @AkashRajpurohit

a new portion of q & a from Laura. Starting from the ~q#53~ q#52 there are q&a from the "interview edition", not sure what's your view on it, should we put them with the rest? Regards ,Eugene

Previously, when the flow was "answer->question" and the user edited the search field, the list was re-filtered correctly but was also reverted to "question->answer" flow.

This was because the logic for swapping the question and answer only ran when the flow was toggled. When the user edited the search value, the list of questions to display was recomputed from scratch and the swap was lost.

Fix this by also running the swap logic when the search value changes.

DISCLAIMER: Completely untested. Not sure if this is the best approach.

This was by far the most requested feature on the comments for hackernews feed, so with this PR, users can switch the flow of data representation

Closes #2

Hi 👋🏻

I just wanted to thank you for doing this project. I am someone who is sorely lacking in tackles, and discovering a project like this will help me a lot in my daily life.

This is not an issue, just encouragement from me and thanks.

Thank you!

The word "yourself" is supposed to be spelt without a space between "your" and "self". Remove such a space in qna.ts in one of the questions.

Is your feature request related to a problem? Please describe. Hi, I’m currently looking for some ideas on what I could implement as a Raycast extension and I remembered this project. Would it be possible to (ideally) provide a simple JSON API or (worse but also appreciated) an NPM package with the raw data?

Describe the solution you'd like Ideally, a simple JSON API (or json file hosted on a predictable URL) would be great

Describe alternatives you've considered An NPM package that contains the JSON would also help, but it would mean that downstream projects need to always update it manually.

Additional context N/A

Is your feature request related to a problem? Please describe. If you're not english you have to translate everything

Describe the solution you'd like Multi-lang support

Describe alternatives you've considered nothing

Additional context no