673540 - Implement 2-3 content templates

Status: RESOLVED WONTFIX

(www.mozilla.org :: General, defect)

Description

[Carmen]

Until we determine an infrastructure for where content will live, we'd like to have 2-3 content templates to use in Q3 as we put together some content features. 

More info to come on what the templates should contain. We're still working out the details.

Comment 1

[Laura Forrest]

Hey Carmen - Thanks for the bug. Is this to implement what's being created in Bug 673537? If so, feel free to change the bug description. Also, any additional information around live date, where this content will live, etc, would be greatly appreciated.

Comment 2

[Carmen]

Hi Laura,
Thanks for the guidance. I updated the description.

As soon as I have live date, etc., I will enter. Jane instructed me to open this bug as a placeholder for a Q3 project that we're still hammering out as we define my role a bit better.

Comment 3

[Laura Forrest]

Sounds good!

Carmen - also feel free to ping Chrissie about this as she has a lot of experience with content heavy sites, UI, and UX. She can also help Shepard you through this release process. 

Moving to a "future" release for now.

Comment 4

[Jane Finette]

Hey there -- this is actually on our schedule still for Q3. wanted to make sure that's still OK. Tara, this was on our list that I emailed over, but I'll be darned if I can recall the next steps on this one.

Comment 5

[mcbmoz]

(In reply to Jane Finette from comment #4)
> Hey there -- this is actually on our schedule still for Q3. wanted to make
> sure that's still OK. Tara, this was on our list that I emailed over, but
> I'll be darned if I can recall the next steps on this one.

Adding Tara, but Jane a few questions:

*How regularly will content be published in these templates (once weekly, twice bi-monthly, etc.)

*Will this content need to have a taxonomy to associate other similar content (through tagging)

*How frequently will these templates need to be updated with design/layout or will they be fixed (magazine-style) and in the future new templates added v. updating existing layouts?

*How often will changes need to be applied to the content post-publish date

*How will these templates and publishing differ from a blog publishing workflow, which can happen outside of a release schedule and without a developer?

Comment 6

[Tara (musingt)]

Hi there.  Thanks for cc-ing me Chrissie.  I was actually looking at the design bug today and wondering when I'd hear more.  As of now, I'm not entirely clear what the scope and scale of this project is.  I haven't allocated (or held) any design resources for this because I've been waiting for an update from Carmen.  The design bug has no details for me.  So, until I hear more... I can't comment :)

Comment 7

[Jane Finette]

Okay ladies. Let me sync up with Carmen and look out for more news in this bug and bug 673537 tomorrow.

Comment 8

[mcbmoz]

(In reply to Jane Finette from comment #7)
> Okay ladies. Let me sync up with Carmen and look out for more news in this
> bug and bug 673537 tomorrow.

Sounds excellent, Jane, I'll also be in MV tomorrow if you want to sync up in person.

Comment 9

[Tara (musingt)]

I iz in MV too!

Comment 10

[Carmen]

Hi folks,
Sorry I haven't had any new updates to the content templates project. I'm still flushing out the strategy, which is nearing the end stages. 

So I don't know how regularly content would be published in the templates, because we don't have a strategy in place yet. We have a long-term look, but we're going to have to think short-term as well. 

I was thinking that the templates would have a fixed design, with text fields for headlines. That we could figure out a way to update the text only. a CMS or HTML-driven WYSIWYG editor would be most awesome so as not to involve a developer. But this was just my thinking - not communicated to a bigger team yet.

The more the strategy comes together, the less I think it will work within a traditional blog framework, but there may be blog technologies that I'm just not aware of. We're still working it out.

I will touch base with Jane and make sure I'm on the right track here. I think she just wanted to make sure we were still on the radar as we're ironing out the details.

Thanks for your patience.

Comment 11

[mcbmoz]

(In reply to Carmen from comment #10)
> Hi folks,
> Sorry I haven't had any new updates to the content templates project. I'm
> still flushing out the strategy, which is nearing the end stages. 
> 
> So I don't know how regularly content would be published in the templates,
> because we don't have a strategy in place yet. We have a long-term look, but
> we're going to have to think short-term as well. 
> 
> I was thinking that the templates would have a fixed design, with text
> fields for headlines. That we could figure out a way to update the text
> only. a CMS or HTML-driven WYSIWYG editor would be most awesome so as not to
> involve a developer. But this was just my thinking - not communicated to a
> bigger team yet.
> 
> The more the strategy comes together, the less I think it will work within a
> traditional blog framework, but there may be blog technologies that I'm just
> not aware of. We're still working it out.
> 
> I will touch base with Jane and make sure I'm on the right track here. I
> think she just wanted to make sure we were still on the radar as we're
> ironing out the details.
> 
> Thanks for your patience.

Hey Carmen,

Let's simplify a bit and don't worry about the technology solution (the web team will take care of that and make a proposal based on your needs).

Identify needs around those five questions I posed in comment 5 and the rest will be pretty easy for us to determine together.

It's a little like doctor/patient. Describe your symptoms and I'll help find a solution.

:)CB

Comment 12

[Tara (musingt)]

Thanks Carmen, sorry if I've missed something here... but I'm feeling a bit in the dark as to what these "templates" actually are.  If you can give me some background / context so I can understand what is coming up in terms of a design request, that would be great.  And please be sure to update the design but with the appropriate information when you are ready.

Thanks.

Comment 13

[Jane Finette]

Carmen - lets sync tomorrow.

Comment 14

[mcbmoz]

Attachment: Round 1 for Phase 1 of Carmen's content project

Carmen currently reviewing and will lock content down for Matej to review and final layout  options tomorrow.

Comment 15

[Tara (musingt)]

Hey guys. The bugs are getting a little messy here.  This is a website bug, but I don't have a design bug on this.  Can we please keep our conversation threads in the right bugs please :)  Do we have a design bug or are we treating this as the design bug?  I don't have any designers on this bug...

Comment 16

[Carmen]

Hi Tara - messy indeed. :)

Okay, so the design bug that matched this website bug was Bug #673537 - I think you pinged me on that one to ask about how it related to Bug #682987. I marked the first bug (Bug #673537) resolved, because I thought that the second bug (Bug #682987) took care of the design for it. Here's why:

I originally opened this website bug and the design Bug #673537 for 2-3 content templates. As I got into developing requirements, Chrissie proposed that we use blog.mozilla.com for the content piece. So she created the design for that piece in Bug 682987, and the implementation for that piece in Bug #683008 

Also, Chrissie's proposal included 1 landing page (like a mini online magazine) that would point folks into the blog content. She's described it in attachment 55528 [details] above. 

I propose that to make things neater/easier, we close this bug, since the scope has changed. I can enter a new design bug for the landing page, and a new website bug for the landing page.

Plus, if it helps, I'm more than willing to get on a call and talk through it, to make sure I'm not confused, either. :)

Comment 17

[Tara (musingt)]

Ah ! okay.  I am reminded of the design bug now.  Thank you.

So, can we please be sure to post wireframes and anything related to design on that bug please? But #682987 vs. this one?  Once design is done, we can move the assets into this bug for implementation.  Tracking everything any other way is just going to be a big head ache :) 

Chrissie, could you please post the wireframe content on the design bug so Ty is also in the loop? 

Thanks so much.

Comment 18

[mcbmoz]

(In reply to Tara from comment #17)
> Ah ! okay.  I am reminded of the design bug now.  Thank you.
> 
> So, can we please be sure to post wireframes and anything related to design
> on that bug please? But #682987 vs. this one?  Once design is done, we can
> move the assets into this bug for implementation.  Tracking everything any
> other way is just going to be a big head ache :) 
> 
> Chrissie, could you please post the wireframe content on the design bug so
> Ty is also in the loop? 
> 
> Thanks so much.

Hey Ladies,

What I'd like to do is close this bug as "WILL NOT FIX" and take this discussion over to email with Shappy, because this landing page is likely part of the bigger content consolidation and innovation project I'm going to head up in Q4. 

Is that cool with you all? I like a tidy bugzilla garden myself!

~cb

Comment 19

[Tara (musingt)]

I'm only concerned with Design bug(s) :)  as long as the appropriate bits are in the design bug, I'll let you handle the implementation bug as you see fit.

Comment 20

[mcbmoz]

(In reply to Tara from comment #19)
> I'm only concerned with Design bug(s) :)  as long as the appropriate bits
> are in the design bug, I'll let you handle the implementation bug as you see
> fit.

Tara, wireframes were attached on 08.23.2011

Carmen, are you OK with us closing this bug, since the project continues to be evolving?

Comment 21

[Carmen]

Fine with me - however is easiest

Comment 22

[mcbmoz]

We'll revisit shortly with the PR team and work this into blog.mozilla.com