Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Firefox Devtools Instructions #24

Open
arky opened this issue Oct 30, 2013 · 5 comments
Open

Firefox Devtools Instructions #24

arky opened this issue Oct 30, 2013 · 5 comments
Assignees

Comments

@arky
Copy link
Collaborator

arky commented Oct 30, 2013

Would love to use this to introduce JavaScript programming. However the tutorial only mentions Chrome but not Firefox Devtools.

Thanks @xMartin for pointing me to this resource.

@xMartin
Copy link
Member

xMartin commented Oct 30, 2013

A bit more background:

Arky works for Mozilla and cares for local communities and as part of this education.

The question is, if we can/want to integrate mentioning and explanation of Firefox and the Devtools in addition to Chrome. On the one hand I don't like the focus on that one product (Google Chrome), on the other hand we did this to keep it simple. I always tell people that there are other great tools around, this is just an example. I would be open for proposals how to add Firefox and make the explanations more open and vendor-independant.

Same issue maybe with the editor (Sublime Text) for day 2.

Maybe this is a sign of growth, that we have to take more care now about those kind of issues as our user base gets more diverse.

@theophani
Copy link
Member

I agree with everything you’ve said, @xMartin. I kept it to Chrome and Sublime Text 2 for the first event to simply things in that first workshop. Now is a good time to remove those specifics.

@gnunicorn
Copy link
Member

Totally agree. Though removing the reference of tools kinda makes it hard and artificial.

So, I was wondering if it was feasible to have each block that is tool-specific available for each tool. At the beginning the learner selects the tools they use or want to see the stuff in (like chrome+sublime or firefox+vim) and then the parts using other tools are hidden throughout the material. I don't know if that is feasible and doesn't add too much confusion, but maybe it is a solution worth trying ...

Extra Plus: if you could click to select the same paragraph for a different tool to allow learners to get some idea, how it might be done in other tools... Diversity and stuff, yo know.

( @arky welcome in the discussion. Not sure if you remember, but we have met over two years ago at the Mozilla Breakfast Meetup at St. Oberholz, when you were in Berlin. Really happy to see you on board.)

@arky
Copy link
Collaborator Author

arky commented Oct 31, 2013

Thanks for the feedback. Yes, I remember you @ligthyear. Still wear that cool unhosted t-shirt you gave me in Berlin.

@gabeno
Copy link

gabeno commented Oct 31, 2013

Hello everyone, this is an important concern. I concur with @ligthyear's suggestion that for the same content a learner may be pointed to how they could do it using other tools to accomodate the potentially diverse user base. This also encourages learners to realize that there are other tools to use do the achieve the same purpose and it depends on a matter of preferences.

Ideally, a learner starts their journey with a given set of tools and they may change them over time as they advance their skills.

@arky arky self-assigned this Oct 4, 2017
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

No branches or pull requests

5 participants