Closed Bug 498421 Opened 15 years ago Closed 15 years ago

Create FF 3.5 party page

Categories

(Websites Graveyard :: spreadfirefox.com, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: abuchanan, Unassigned)

References

()

Details

Hey,

We've started mocking up a page here for FF 3.5 launch parties.

This is bug for tracking that task.  Also, I'll be moving this page to a static page, so we don't have to manage it through Drupal.
Do we need to link to the event form and the party list?

Here is an example link to the party list,
http://www.spreadfirefox.com/event/2009/06/12/list/all/808
Group: mozilla-confidential
(In reply to comment #1)
> Do we need to link to the event form and the party list?
> 
Oh, I'm blind and didn't see the "Create a party" button.  Maybe we should still include it in the content somewhere?
Target Milestone: --- → 3.0.2
somehow I made this confidential accidentally, reverting that
Group: mozilla-confidential
r27887 checks in the party page 

Mary and/or Sarah, could you find a place on this page to link to the party list, and the create event form (from within the content) please?

Thanks
Hey there - I think I need to update the text for the party list and then "create party" should link to the new form.
(In reply to comment #5)
> Hey there - I think I need to update the text for the party list and then
> "create party" should link to the new form.

sounds good.  post the updates here and i'll update the page.

I can link "posting your event on Spread Firefox" to the event form
Actually - no need to update the page!  Here is where you should link...in brackets.

There should be Firefox parties all over the world. If you’re looking for one to attend, you can find and RSVP to gatherings in your area via [our calendar].
r27895

https://spreadfirefox.authstage.mozilla.com/lets-party

node/4201 and blocks 46 & 47 will need to be removed from production before this launches
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
It's a bad user experience that logged-out users are going to see "Access Denied: You are not authorized to access this page" when clicking on "Create a Party"; we don't mention anywhere on https://spreadfirefox.authstage.mozilla.com/lets-party that you have to have an account AND be logged in.
Ok - I can add that!
Updated.  Let me know what you think!
(In reply to comment #11)
> Updated.  Let me know what you think!

I don't see anything about accounts or logging in; is the old page just cached, or something?
Hey there:  It's here...

# Create an “invite” on Spread Firefox and/or a social network. You can start by posting your event on Spread Firefox (click the create party button on the right -- you'll need to have a SFx account & be logged in!)
r27974 adds the note to stage.
Hi there:  A few other changes:

* Can we change the url to /party?
* Under when to party we need to change this to July:

Celebrations should be planned for July—don’t worry we’re not limited to any specific dates.

We should be good to go.
[1] I still think a lot of users are going to skim the text and just "Create a Party", but the "Access Denied" error message is a limitation of our current implementation, so I'm not going to harp on that.

[2] Staging is also missing the pink background for the "Let's Party" block.
Any suggestions other than bolding?
(In reply to comment #17)
> Any suggestions other than bolding?

Me?  No; the text you added is fine -- not much else we can do other than to fix our error-message page to point to creating a user account and/or logging in -- that's something for a future release.
per our meeting, the URL for this page has moved to /party r28025
Still missing the July change per Comment #15...
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
r28088 updates the text from comment #15
Status: REOPENED → RESOLVED
Closed: 15 years ago15 years ago
Resolution: --- → FIXED
Verified FIXED.
Status: RESOLVED → VERIFIED
Product: Websites → Websites Graveyard
You need to log in before you can comment on or make changes to this bug.