Closed Bug 695395 Opened 8 years ago Closed 8 years ago

[User Engagement Blog] Implement Blog

Categories

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

task
Not set

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: christine.brodigan, Unassigned)

References

()

Details

As a part of this Wordpress instance, 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.
No longer depends on: 683008
I think you should be able to do all/most of this as an admin to the blog in question. If you aren't an admin on that blog, feel free to file an IT bug to get those rights.
(In reply to Fred Wenzel [:wenzel] from comment #1)
> I think you should be able to do all/most of this as an admin to the blog in
> question. If you aren't an admin on that blog, feel free to file an IT bug
> to get those rights.

Hey Fred,

I think I might need some webdev help, but it's pretty easy to create the custom post type: http://codex.wordpress.org/Post_Types#Custom_Types

Thoughts?
Yup, that would need a little plugin. Not completely sure I understand yet why different post types are needed over just categories, but I am sure we'll sort this out :)
(In reply to Fred Wenzel [:wenzel] from comment #3)
> Yup, that would need a little plugin. Not completely sure I understand yet
> why different post types are needed over just categories, but I am sure
> we'll sort this out :)

High-level answer is that this will allow us to start consolidating all the blogs (more than 150) across teams. Teams can use the post type and not run into other teams' work product. It's a good way to silo.

Categories then can be used across all post types, so we can more easily create related-content structures, so if User Engagement blogs about Security, it could go out in multiple places if the teams wanted it to, or just go into the single silo.

Would you be able to add the post type for User Engagement, so we can experiment a little bit as we think through how we can make more effective use of the single wordpress instance with the goal of reeling in team blogs over the coming quarters and reducing the number of unique wordpress sites out there for IT to wrangle.
Checking in on this, will the user engagement blog be ready to go to production tomorrow?
(In reply to mcbmoz from comment #5)
> Checking in on this, will the user engagement blog be ready to go to
> production tomorrow?

The theme is ready, but I'm not sure about the rest of the setup - it's out of my level of access.
Fred/Jake, could you chime in with next steps?
Steven: Did you take care of the post types? I think those go into the template code.

Chrissie: As far as categories are concerned, that's what comment 1 was about.

Hope this helps.
(In reply to Fred Wenzel [:wenzel] from comment #8)
> Steven: Did you take care of the post types? I think those go into the
> template code.

I did not - WordPress development is a bit out of my area of expertise. We can look into it, but we were pulled in quickly to help with the theme as Craig wasn't able to start right away. It may be faster by now to have him help with this?
Assigning to Mike Alexis to answer comment 9
Assignee: nobody → malexis
(In reply to Fred Wenzel [:wenzel] from comment #8)
> Steven: Did you take care of the post types? I think those go into the
> template code.

They do. Let's see what Mike A. says.

> 
> Chrissie: As far as categories are concerned, that's what comment 1 was
> about.

Apologies, I meant to change the title here to Implement. I've taken care of the category

> 
> Hope this helps.

Is it still possible to launch what we have and then make these tweaks in the next week or so when Craig has more bandwidth?
Summary: [User Engagement Blog] Set up category and post type in wordpress → [User Engagement Blog] Implement Blog
Hey Steven, while we figure out setup, Brad was wondering if he could take a look at the HTML to add unique webtrends tracking.
(In reply to mcbmoz from comment #12)
> Hey Steven, while we figure out setup, Brad was wondering if he could take a
> look at the HTML to add unique webtrends tracking.

Chrissie, can you file a separate bug for webtrends?

(In reply to mcbmoz from comment #11)
> (In reply to Fred Wenzel [:wenzel] from comment #8)
> Is it still possible to launch what we have and then make these tweaks in
> the next week or so when Craig has more bandwidth?

I think that makes sense. Let's push the blog to production and Craig can work on the post types feature when he has the bandwidth (we'll need a new bug for that too).

I'm a bit unclear what the workflow is for blogs and what the next steps are here. Do we need IT to SVN up the WP theme to prod? Has QA looked at it?
(In reply to Mike Alexis [:malexis] from comment #13)
> (In reply to mcbmoz from comment #12)
> > Hey Steven, while we figure out setup, Brad was wondering if he could take a
> > look at the HTML to add unique webtrends tracking.
> 
> Chrissie, can you file a separate bug for webtrends?

Already done: Bug 695080

> 
> (In reply to mcbmoz from comment #11)
> > (In reply to Fred Wenzel [:wenzel] from comment #8)
> > Is it still possible to launch what we have and then make these tweaks in
> > the next week or so when Craig has more bandwidth?
> 
> I think that makes sense. Let's push the blog to production and Craig can
> work on the post types feature when he has the bandwidth (we'll need a new
> bug for that too).
> 

I will file this today.

> I'm a bit unclear what the workflow is for blogs and what the next steps are
> here. Do we need IT to SVN up the WP theme to prod? Has QA looked at it?

Fred can you answer, I'm not sure of the process for blog.mozilla.com stuff. We'll document after we figure it out here.
(In reply to Mike Alexis [:malexis] from comment #13)
> I'm a bit unclear what the workflow is for blogs and what the next steps are
> here. Do we need IT to SVN up the WP theme to prod? Has QA looked at it?

AFAIK there's no staging instance for blogs, though if it's a new blog with no traffic, there's nothing keeping us from deploying it, then have QA look at what will later be the production instance.

And yes, the way the themes make it into production is for IT to SVN up the checkout. FTR, all our themes are here:
https://svn.mozilla.org/projects/blog.mozilla.com/trunk/wp-content/themes/
(In reply to Fred Wenzel [:wenzel] from comment #15)
> (In reply to Mike Alexis [:malexis] from comment #13)
> > I'm a bit unclear what the workflow is for blogs and what the next steps are
> > here. Do we need IT to SVN up the WP theme to prod? Has QA looked at it?
> 
> AFAIK there's no staging instance for blogs, though if it's a new blog with
> no traffic, there's nothing keeping us from deploying it, then have QA look
> at what will later be the production instance.
> 
> And yes, the way the themes make it into production is for IT to SVN up the
> checkout. FTR, all our themes are here:
> https://svn.mozilla.org/projects/blog.mozilla.com/trunk/wp-content/themes/

Jeremy, cc'ing you to help route this to the right person in IT who can help deploy a new blog for us (hopefully tomorrow). Can you point me to the right person?
OK, assigning back to Steven to put the theme in https://svn.mozilla.org/projects/blog.mozilla.com/trunk/wp-content/themes/

Opening up an IT bug for pushing to production.
Assignee: malexis → steven
Blocks: 696956
Target Milestone: 4.3 → 4.4
(In reply to mcbmoz from comment #17)
> OK, assigning back to Steven to put the theme in
> https://svn.mozilla.org/projects/blog.mozilla.com/trunk/wp-content/themes/

This has been in trunk since the 19th (r96572).
(In reply to mcbmoz from comment #4)
> (In reply to Fred Wenzel [:wenzel] from comment #3)
> > Yup, that would need a little plugin. Not completely sure I understand yet
> > why different post types are needed over just categories, but I am sure
> > we'll sort this out :)
> 
> High-level answer is that this will allow us to start consolidating all the
> blogs (more than 150) across teams. Teams can use the post type and not run
> into other teams' work product. It's a good way to silo.
> 
> Categories then can be used across all post types, so we can more easily
> create related-content structures, so if User Engagement blogs about
> Security, it could go out in multiple places if the teams wanted it to, or
> just go into the single silo.
> 
> Would you be able to add the post type for User Engagement, so we can
> experiment a little bit as we think through how we can make more effective
> use of the single wordpress instance with the goal of reeling in team blogs
> over the coming quarters and reducing the number of unique wordpress sites
> out there for IT to wrangle.

I would like to have a meeting to discuss this. There are a lot of negatives to this plan as written that I would like to discuss before we move forward. This project seems to have happened with minimal IT and webdev consultation, and that needs to be fixed before we can have any hope of a sane implementation.

I will email you outside of Bugzilla to set up a meeting.
(In reply to Jake Maul [:jakem] from comment #19)
> (In reply to mcbmoz from comment #4)
> > (In reply to Fred Wenzel [:wenzel] from comment #3)
> > > Yup, that would need a little plugin. Not completely sure I understand yet
> > > why different post types are needed over just categories, but I am sure
> > > we'll sort this out :)
> > 
> > High-level answer is that this will allow us to start consolidating all the
> > blogs (more than 150) across teams. Teams can use the post type and not run
> > into other teams' work product. It's a good way to silo.
> > 
> > Categories then can be used across all post types, so we can more easily
> > create related-content structures, so if User Engagement blogs about
> > Security, it could go out in multiple places if the teams wanted it to, or
> > just go into the single silo.
> > 
> > Would you be able to add the post type for User Engagement, so we can
> > experiment a little bit as we think through how we can make more effective
> > use of the single wordpress instance with the goal of reeling in team blogs
> > over the coming quarters and reducing the number of unique wordpress sites
> > out there for IT to wrangle.
> 
> I would like to have a meeting to discuss this. There are a lot of negatives
> to this plan as written that I would like to discuss before we move forward.
> This project seems to have happened with minimal IT and webdev consultation,
> and that needs to be fixed before we can have any hope of a sane
> implementation.
> 
> I will email you outside of Bugzilla to set up a meeting.

Thanks so much Jake, looking forward to talking outside of Bugzilla.
Trying to keep up in Bugzilla and ask questions as we go so I can learn.

Does this mean we need to set up a meeting BEFORE we launch? Can we launch and then CHANGE this if we need to? (Bringing our old posts with us?)

Chrissie/Jake - depending on a response about launch, would you like me to set up a meeting for tomorrow? Happy to set it up, but would like to move quickly as I feel like we're "almost there!" and I don't want to spin on this too long.
Carmen, I think if you go to blog.mozilla.com/wp-admin and enter your ldap credentials, you should be able to see things working. Please confirm. 

I'm new to how blog launches work here too, so Jake - you probably have better advice.
Chrissie - I can log in, and post to the category, but when I preview, I don't see the Den theme (I'm not sure if that's because it's preview mode or not)

Jake - since I was planning on this launching this week and have some content hinging on this, please let me know about comment 23 ASAP. Appreciate it!
Jake/Fred,

However, Gary and others have released their Wordpress themes, let's just keep the staus quo here and do the exact same thing for Carmen.

Apologies for any complexity, I was trying to reduce the need for an entirely new blog instance.
Hi team,
So the security review was completed and the theme approved. How do we get it pushed live, and when can we do that? Can someone provide a date?

I went to http://blog.mozilla.com/blog/category/user-engagement/ this morning and did not see the theme for "The Den"

Thanks!
(In reply to Carmen from comment #25)
> So the security review was completed and the theme approved. How do we get
> it pushed live, and when can we do that? Can someone provide a date?

Need jakem to push the theme from trunk into production.
Steven/Jakem - is that 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!
(In reply to Carmen from comment #27)
> Steven/Jakem - is that 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!

Carmen, I'm sure this has gotten a little confusing, please see Bug 683008 for progress on getting your theme pushed to production.
Apologies :) I'll take it to the other bug. It's a bug swarm!
Per Bug 696956, this was implemented as a category instead of a separate blog.

If this was in error, please re-open this bug.
Assignee: steven → server-ops
Status: NEW → RESOLVED
Closed: 8 years ago
Component: blog.mozilla.org → Server Operations: Web Operations
OS: Mac OS X → All
Product: Websites → mozilla.org
QA Contact: blog-mozilla-org → cshields
Hardware: x86 → All
Resolution: --- → FIXED
Target Milestone: 4.4 → ---
Version: unspecified → other
Hi Jake -

Pardon my confusion - this is my first Mozilla project, and it seems to have gotten all confused, despite mcbmoz's efforts to help me through this.

Unless I'm misunderstanding something from the other bug 68308 in order to have a custom theme, we need a separate blog instance. Correct?

And that's how you created Gary's blog - yes?

I think that's What Chrissie is saying in comment 24 - whatever the status quo for Gary's blog was, let's follow that lead. And she just clarified in bug 68308

The user engagement blog needs to have a separate theme. I'm okay if we can't link to other categories, we can link to other blog urls if we need to. 

In the words of Captain Picard - Engage! I believe you said that creating this new blog instance is something you can do today? Minutes even?

Would the url then be able to be: blog.mozilla.com/theden ? (Does the new blog instance mean that we can have this name?)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Hi Carmen -

No problem, glad to get on the same page with this. :)

It can be named whatever you'd like it to be... I believe thus far these 2 names have been proposed:

blog.mozilla.com/theden
blog.mozilla.com/userengagement

Also available is this, if you like the latter but want something shorter:
blog.mozilla.com/engagement

Let me know what you prefer.

Also let me know if you'd like me to set up any other users for you, or just yourself for now. I can make you an admin if you like, in which case you'd be able to add/remove other people later on. Whatever works for you. :)
Thanks Jake - now we're cookin' with oil!

Let's go with:
blog.mozilla.com/theden

For admins, here's the list
Me (Carmen Collins)
Jane Finette
Matej Novak
William Reynolds
Jessilyn Davis 
Winston Bowden
Chelsea Novak

That will cover the user engagement team for now. If you want to make me the admin, I can add others as needed. 

Can you just ping me in the bug when it's launched? I'm crossing my fingers for today :)
This is completed.

http://blog.mozilla.com/theden/

The admin page is here:

https://blog.mozilla.com/theden/wp-admin/

You should be able to log in with your LDAP credentials. I've set you (Carmen) up as an admin, and all the others as Editors... this gives anyone the ability to put up or take down posts, correct typos, etc. It's basically full control except for blog settings, like the theme and user management.


I have also removed the "User Engagement" category from the main blog, since with this in place it would only serve to confuse people.

Please let me know if you have any trouble with this. Thanks!
Status: REOPENED → RESOLVED
Closed: 8 years ago8 years ago
Resolution: --- → FIXED
Gold stars. :) thank you!
verified fixed http://blog.mozilla.com/theden/
Status: RESOLVED → VERIFIED
Jake - can I ask a quick question? 

The subhead under "The Den" title on the blog was supposed to read "Content curated by us and delivered to you." It now reads "Just another Blog.mozilla.com site"

I'm not sure if I posted it in one bug and not another, if we somehow posted an old version of the design, or what. I went back through them and can't piece the puzzle together.

Is that something that would be a quick fix? Or is that something that would require a complete over-haul? 

Technically, the way it stands, it's incorrect, due to the .com/.org merge. At the least, I'm hoping we can updated it to say Blog.mozilla.org.

You tell me next steps. I'll try to work with you, seeing as you earned gold stars today. :)
You can change that easily yourself: Go to the admin panel, click "Settings", and edit the tagline.

Technically blog.mozilla.com *is* correct right now... .org redirects to .com. That's a whole separate project, and not at all trivial. However, you can easily change the tagline to be what you originally wanted and don't have to reference it either way. :)
Thanks so much!
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.