Closed Bug 1013858 Opened 12 years ago Closed 9 years ago

Create instructions on how to properly 'whitelist' Webmaker Tools on filtered networks

Categories

(Webmaker Graveyard :: webmaker.org, defect)

x86_64
Other
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: doug, Assigned: doug)

Details

(Whiteboard: [tech-debt])

See this from Webmaker Training: http://discourse.webmakerprototypes.org/t/whitelisting-webmaker/343/8 Educators are getting stuck with whitelisting as they need to do so for several domains (and this isn't documented on webmaker.org AFAIK)
Doug, want to take a stab at creating a SUMO article on this? Then it will be more discoverable when a user clicks on the help section within thimble.
Assignee: nobody → doug
Yep, have suggested in Discourse thread. Will co-create with community (as I'm not in a position to test)
I started an etherpad for community sourced instructions on how to overcome this challenge.
There are also a few things we could do dynamically from Thimble to direct users to the SUMO article. For instance, if mozillathimblelivepreview.net doesn't load within a reasonable amount of time, we could show an error message that directs the user to the SUMO article. It seems like this would be particularly useful, since mozillathimblelivepreview.net is both critical to Thimble's functionality and never appears in the address bar (and is therefore completely non-obvious to whitelisters).
Unless someone has the knowledge/expertise for this, I'm going to have to close it. I'm not on a filtered network so can't test.
Whiteboard: [tech-debt]
Status: NEW → ASSIGNED
Added to Kat's teaching kits spreadsheet: http://goo.gl/pyISnZ
The webmaker.org site is no longer developed. https://learning.mozilla.org/blog/whats-next-for-webmaker-tools
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.