Closed Bug 683008 Opened 13 years ago Closed 13 years ago

[User Engagement Content Project] Push Theme to Production

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: christine.brodigan, Unassigned)

References

()

Details

This is a blog project similar to Bug 680148. 

But, this should not involve a new instance of wordpress. Rather this should be much more minor like the solution for Gary's blog.

Carmen is product owner with Jane.
Assignee: malexis → nobody
Component: www.mozilla.org/firefox → other.mozilla.org
QA Contact: www-mozilla-com → other-mozilla-org
Hey Mike,

We'll have the final design and PSD for a Wordpress theme locked down by eod.

Can you help us proceed to work with Craig or another flux team resource to build a new category into blog.mozilla.org and launch the User Engagement blog in the coming 2 weeks (if possible).

This is identical to the Gary blog project we just completed, so not too much heavy lifting or configuration. I can meet with you to discuss anytime. LMK. I will attach the final design asset eod or first thing in the morning.
Assignee: nobody → malexis
Added Bug 695080 to cover the WebTrends part of this project.
Assignee: malexis → craigcook.bugz
Hey Craig,

As a part of this Wordpress implementation, we'd like to add a Post type called, User Engagement to the blog, where all of this team's posts will be captured and organized. Ideally, this would be visible to the main admin and then User Engagement would have rights to edit as well.

Ultimately, building out this as Mozilla's main Wordpress instance and home for future team and individual blog efforts (under one roof, sharing a single taxonomy).

Let me know how much detail you need, and if you want to jump on a call to sort anything out.

Final PSDs: http://mozilla.tyflanagan.com/artwork/TheDen/Moz_TheDen_Final.psd.zip
Assigning over to Steven.
Assignee: craigcook.bugz → steven
Steven, updating to 4.3, please ping me with any questions you have about the design and nuances.

I'd like to configure Wordpress in comment 3 and can talk you guys through that structural change if needed.
Target Milestone: 3.9 → 4.3
We'll get started on the blog theme right away. Might be worth getting another Bug started for the setup of the wordpress blog that our theme will live on (or using this bug for that setup and breaking out a new theme design bug for us).
Blocks: 695395
(In reply to Steven Garrity from comment #6)
> We'll get started on the blog theme right away. Might be worth getting
> another Bug started for the setup of the wordpress blog that our theme will
> live on (or using this bug for that setup and breaking out a new theme
> design bug for us).

done! bug 695395
No longer blocks: 695395
I've made a copy of the theme for Gary Kovac's blog and modified the header according to the photoshop mockup (r96572 in trunk).

CC'ing jakem to push to production. The theme is called "The Den" and will be selectable in the WP admin. I did not setup the Twitter/Facebook counts on each post, nor did I set up all of the right sidebar content as I'm not sure how much of that should live in the theme vs. being set up in the Admin.
Is there a url on stage somewhere that we can use to check if Webtrends is working?
(In reply to mcbmoz from comment #9)
> Is there a url on stage somewhere that we can use to check if Webtrends is
> working?

As far as I know, there is no staging environment for the blogs.
(In reply to Steven Garrity from comment #10)
> (In reply to mcbmoz from comment #9)
> > Is there a url on stage somewhere that we can use to check if Webtrends is
> > working?
> 
> As far as I know, there is no staging environment for the blogs.

Jake just did something to fake it a bit for Gary's blog, maybe he can do the same here?
For Gary's blog, I just created a new temp blog and assigned it that theme (without opening the theme up for use on other blogs). This is just a workaround until we have a proper staging environment, which is on the way.

When this theme is ready for infrasec approval, we can do the same for it.

As far as Webtrends, I know nothing about that. The Metrics team handles all aspects of Webtrends (apart from sometimes telling us what to do sometimes). I'm not sure what exactly is required to have that working, or if it just naturally works for everything on blog.mozilla.com...

Anyway, your best bet on Webtrends will be to talk to Metrics and find out what (if anything) is required to have that working.
Target Milestone: 4.3 → 4.4
Summary: Add User Engagement Category to Blog (similar to Gary's blog) → [User Engagement Content Project] Add User Engagement Category to blog.mozilla.com
(In reply to Jake Maul [:jakem] from comment #12)
> For Gary's blog, I just created a new temp blog and assigned it that theme
> (without opening the theme up for use on other blogs). This is just a
> workaround until we have a proper staging environment, which is on the way.
> 
> When this theme is ready for infrasec approval, we can do the same for it.
> 
> As far as Webtrends, I know nothing about that. The Metrics team handles all
> aspects of Webtrends (apart from sometimes telling us what to do sometimes).
> I'm not sure what exactly is required to have that working, or if it just
> naturally works for everything on blog.mozilla.com...
> 
> Anyway, your best bet on Webtrends will be to talk to Metrics and find out
> what (if anything) is required to have that working.

Jake,

What you did with Gary's blog would be perfect for Carmen's User Engagement blog. Many thanks. Please update once it's pushed.
Summary: [User Engagement Content Project] Add User Engagement Category to blog.mozilla.com → [User Engagement Content Project] Push Theme to Production
Jake - I asked a question of you in the wrong bug - apologies. 

Is pushing the blog the way you did with Gary's something that's fairly easy to do? Is it something we can do today, or do we have to wait for a bundle to be pushed? If not today, can you tell me when we can get on your schedule to push the theme?

Thanks!
Hi Carmen,

As per Bug 696956, this was not set up as a separate blog like Gary's blog. Instead it is a *category* under the main blog.mozilla.com blog. That bug has the details, but the short answer is you cannot set a theme on a category.

If you want a custom theme, it has to be a separate blog. This is how Gary (and mrz, and Mozilla IT, and dozens of others) are set up- they are independent blogs, and (from a content perspective) do not tie into the main blog. They share all the same infrastructure, so it's very easy for us to manage... but WP knows they are separate blogs and don't share content. Thus, they can have different themes, categories, authors, etc.

Specifically, comments 10, 18, 19, and 38 in that bug speak directly to this decision and the ramifications of it.

The benefit of using categories instead of separate blogs is that a post can be tagged in multiple categories... thus increasing it's audience. For example, a post in mrz's blog cannot be viewed from Gary's blog, because they're totally different blogs. If they were set up as categories instead (as "User Engagement" was), they would share the same space- posts could be tagged in either category.


If we must have a custom theme for "User Engagement" posts, then it needs to be its own blog instance, like Gary's blog is. We can do that, if that's what you want. I recommend talking to mcbmoz about this though, as this would conflict with some of Engagement's goals. This theme is already approved and pushed, so if we want to do it this way I can have that done in a matter of minutes.


Hopefully this clears up the confusion. I'm going to mark this bug as RESOLVED and take ownership of it. If we decide this should be a separate blog instead of a category, please re-open and I'll get it done.
Assignee: steven → server-ops
Status: NEW → RESOLVED
Closed: 13 years ago
Component: other.mozilla.org → Server Operations: Web Operations
OS: Mac OS X → All
Product: Websites → mozilla.org
QA Contact: other-mozilla-org → cshields
Hardware: x86 → All
Resolution: --- → FIXED
Target Milestone: 4.4 → ---
Version: unspecified → other
Amendment... instead of re-opening *this* bug, please re-open Bug 695395, which I am about to close. That's a much better place to discuss the actual blog setup, whereas this bug was supposed to be about the theme. :)
(In reply to mcbmoz from comment #13)
> What you did with Gary's blog would be perfect for Carmen's User Engagement
> blog. Many thanks. Please update once it's pushed.

Gary's blog is a new blog - separate blog..  You said you didn't want a new blog under blog.mozilla.com  (it would be a lot easier for us if you did)

Maybe we should hold off making any more requests or changes until you can meet with Jake.  I think you might be confusing some of wordpress's abilities in our current installation.
(In reply to Corey Shields [:cshields] from comment #17)
> (In reply to mcbmoz from comment #13)
> > What you did with Gary's blog would be perfect for Carmen's User Engagement
> > blog. Many thanks. Please update once it's pushed.
> 
> Gary's blog is a new blog - separate blog..  You said you didn't want a new
> blog under blog.mozilla.com  (it would be a lot easier for us if you did)
> 
> Maybe we should hold off making any more requests or changes until you can
> meet with Jake.  I think you might be confusing some of wordpress's
> abilities in our current installation.

Cory, Jake has clarified here. At this point, the request is do for Carmen what was done for Gary.
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.