666454 - Select a topic for the September Dev Derby and get description copy

Status: VERIFIED FIXED

(developer.mozilla.org Graveyard :: Wiki pages, defect)

Description

[John Karahalis [:openjck]]

Decide a topic for the September Derby so that it can be listed below a trophy in the "Upcoming Challenges" section.

Comment 1

[Jay Patel [:jay]]

To make things as simple as possible, here is what I propose when we have the topic, tagline and short description ready:

1. Move July to the center trophy
2. Replace left trophy with new September content

No need to rearrange all 3 trophies.

Janet: Once we have a topic, could you help get the copy together for it?  Basically a tagline and short decription (like we show along with the tophies on the Dev Derby page: https://developer.mozilla.org/en-US/demos/devderby).

Comment 2

[Jay Patel [:jay]]

We're going with History API for September!  

Here is a short description we can use for the hover on trophy copy:

"The History API in modern browsers enables live changes to the document without breaking the back button and allows apps to be bookmarked."

For the tagline below the trophy, how about:

"Play with browser memory."  cheesy, I know... so if anyone else has ideas, throw them out there.

Comment 3

[Luke Crouch [:groovecoder]]

"A browser never forgets."

Comment 4

[John Karahalis [:openjck]]

How about "Change history with HTML5!"

Comment 5

[Jay Patel [:jay]]

(In reply to comment #3)
> "A browser never forgets."

I like it!  Let's go with Luke's version of the tagline.

John:  Yours was good, but we're not really changing history, so it doesn't work. :-(

Comment 6

[John Karahalis [:openjck]]

(In reply to comment #5)
> (In reply to comment #3)
> > "A browser never forgets."
> 
> I like it!  Let's go with Luke's version of the tagline.
> 
> John:  Yours was good, but we're not really changing history, so it doesn't
> work. :-(

Yeah, I figured that might be a drawback of the tagline. :-)

Good work, Luke! I like it.

Comment 7

[Jay Patel [:jay]]

assigning to les since he was working on these pages before.  please reassign if needed.

Comment 8

[Les Orchard [:lorchard]]

This bug's gotten a bit confusing. In the future, it'd be better to file a bug to make the page changes, with a copy bug like this and bug 666453 as blockers.

Just to confirm, this is the final copy, right?

History API
A browser never forgets.

Comment 9

[Jay Patel [:jay]]

(In reply to comment #8)
> This bug's gotten a bit confusing. In the future, it'd be better to file a
> bug to make the page changes, with a copy bug like this and bug 666453 as
> blockers.

Sorry, we'll break up the bug into 2 next time.


> Just to confirm, this is the final copy, right?
> 
> History API
> A browser never forgets.

Yes, that's the final copy.

Comment 10

[Les Orchard [:lorchard]]

(In reply to comment #9)
> Sorry, we'll break up the bug into 2 next time.

Not breaking up the bug, so much as wrangling all the individual tasks / dependencies into a tracker like bug 668242. 

That way whomever implements the changes (eg. me) and whomever does QA on the changes can more easily see what needs doing overall. Lots of moving parts here and things decided in comment threads.

Marking this bug closed, because the topic has been decided and copy finalized

Comment 11

[John Karahalis [:openjck]]

(In reply to comment #8)
> This bug's gotten a bit confusing. In the future, it'd be better to file a
> bug to make the page changes, with a copy bug like this and bug 666453 as
> blockers.
> 
> Just to confirm, this is the final copy, right?
> 
> History API
> A browser never forgets.

That makes sense. Thanks, Les!

Comment 12

[raymond [:retornam] (inactive)]

verified fixed https://developer.mozilla.org/en-US/demos/devderby