i want to contribute here please assign me

Hi @SusheelThapa, Please assign this issue to me.

hi @SusheelThapa Please assign this issue to me

Hi @SusheelThapa assign me to this issue please.

I want to contribute please assign the issue to me

Is this in progress? any ETA?

Is this in progress? any ETA?

I don't think @rajatsingh23 is working on it anymore. Feel free to take over.

@sumn2u Thanks for the assignment, can you provide details about the assignment? or if there are any identical completed example PRs I can reference from?

Thanks in advance!

@sumn2u Thanks for the assignment, can you provide details about the assignment? or if there are any identical completed example PRs I can reference from?

Thanks in advance!

This PR (#226) outlines the process for adding an interpreter. The goal is to provide environments where users can execute code and view the results directly within their browsers. Feel free to add it where you think an exercise will help to understand the concept.

Feel free to add it where you think an exercise will help to understand the concept.

Okay that explains why this issue is kept open all this time because nobody wants to go ahead and read all the content to decide if an interpreter is needed or not... a lot of bottlenecks in the process.

How about streamlining the procedure by adding a JS interpreter Icon at the level of the navbar (plenty of space available) that can toggle the interpreter's visibility and auto scroll to it's viewpoint? (the interpreter will be page agnostic)

LMK @sumn2u

@kenshanta Thanks for the suggestions and for pointing out the bottlenecks. For now, I think it makes sense to start with these chapters: Strings, Conditional Logic, and Arrays. We can move on to the others later.

Regarding the JS interpreter icon, I think it makes more sense to place it inside the right sidebar, within the chapter section, rather than in the navbar, but this is a lower priority for now.