Foundation.mozilla.org: Add advocacy/campaign info on the foundation site

[gideonthomas]

tldr; we need a general info page about our campaign work (possibly /campaigns)

The /initiatives page has a good overview of the different channels through which we work.

The fellowships section has a button to "learn more" that links to the fellowships mini-site on the foundation site and this site has some good high-level content about the fellowships.

Ticket #2285 deals with moving specific campaign content into the foundation site. It would be super useful to have a more general page (like we have for fellowships) for campaigns that can link to these specific campaigns on the advocacy site (and later the foundation site once all the campaigns have been ported over). This will give us the agency to link to this page when we're emailed and asked about what kind of work we do (true story).

cc @Sydette

[alanmoo]

Jesse and I talked about this last week when discussing how to shut down advocacy.mozilla.org (we'll redirect that domain to /campaigns)

Let's create a Pulse entry for each of our campaigns thus far using a tag, and then make /campaigns an opportunity page with a Pulse component that shows all those campaigns. That way we have _something_ to reference.

Gideon, can you facilitate making those Pulse entries, since it requires digging into the CMS to get the links? (It may end up the easiest way to do it is for you to simply submit the entries yourself)

[gideonthomas]

@alanmoo should we also include past campaigns that weren't on the foundation site? i.e. stuff on adv.moz.org?

[alanmoo]

No. We're likely going to take them down and redirect them to this page.

[gideonthomas]

One concern I do have is about the user journey for the campaigns (or it might be because I don't fully understand the solution). We're linking from the foundation site to pulse entries about campaigns that link back to the foundation site? Doesn't that seem a bit redundant?

[alanmoo]

Great point. @xmatthewx or @jessevondoom thoughts?

[Sydette]

I agree with Gideon. I want to look at user journey with somebody and talk
about what looks best. Fellows are asking how to add their things and
reference our reports and add their own. I think it's redundant but I'm
unsure. I think Tais has the most recent IA structure.

On Tue, Jan 29, 2019 at 8:21 PM Alan Mooiman [e-mail]
wrote:

Great point. @xmatthewx https://github.com/xmatthewx or @jessevondoom
https://github.com/jessevondoom thoughts?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mozilla/foundation.mozilla.org/issues/2397#issuecomment-458671686,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMwA2Y57zlSms3ka8axt_yM4DCTx4dRvks5vIJ80gaJpZM4ZnQRX
.

--
Sydette Harry
Editor - Web Properties Mozilla
[email protected]

[xmatthewx]

The old advocacy site is killing our SEO and likely confusing a bucket full of good people. It’s been disconnected for far too long.

I think we can simplify. I think we _must_ simplify to move forward, fix the bad situation, and then after that, pursue the right long term solution.

I propose:

• create page with a simple paragraph or two on our advocacy.
• publish page and redirect top level advocacy urls
• add a simple list to new page with highlights of active and past campaigns
• post campaigns to pulse
• extend wagtail pulse component with checkbox to allow authors to use direct link that skips pulse view
• replace static list with pulse feed
• archive advocacy site
• iterate on campaigns landing page if needed

No item on this list is more than a days worth of work. It solves a major weak spot of ours. A comprehensive plan will take weeks or months with debate among many stakeholders.

[kristinashu]

~I still don't see why we need to go through pulse, especially since we'll be linking to internal pages. Why not use cards we already have? They allow for some intro text to give provide context and unique cta link copy.~ Feel free to ignore.

[gideonthomas]

@alanmoo pulse entries created. For now, I updated https://foundation.mozilla.org/cms/pages/233/edit/ which is an opportunity page that already existed under /initiatives.

Next steps (in order):

• [ ] Transform /campaigns into a CMS editable page. @alanmoo can you advise on how to do this?
• [ ] Port over content from the page I updated above to /campaigns and @Sydette to add content about our advocacy/campaign work.
• [ ] Setup redirects from advocacy.mozilla.org to /campaigns.
• [ ] implement @xmatthewx's suggestion of allowing authors to use direct links that skips the pulse view and then update the /campaigns page with that component.

Let me know if this requires engineering and I can file a project brief.

[gideonthomas]

@Sydette would you be able to come up with some content about the advocacy/campaign work we do and post it here?

[alanmoo]

I think a few of us need to have a conversation about page templates, as this opens up a bit of a rabbit hole. With a minor code change, I can make "Campaign" and "Opportunity" pages children of "Primary" pages, and make this new page a "Primary" page. However, the top level pages of mini-sites then show up in the horizontal nav of the primary page

There's a few ways we can go to solve this, but before we slap another band-aid on it, I think it's time to step back for a moment and evaulate where our templates are at holistically.

[mmmavis]

This visual IA chart would be useful for the convo: https://redpen.io/hx70e9eb24e0534b72

[gideonthomas]

can we file a new ticket with the dev work for this if it's not a simple change (and mark this as blocked)?

[alanmoo]

Yeah, this is on me right now to schedule another meeting and talk about proposed solutions. Probably not going to happen till after reviews though.

[alanmoo]

I've spun up https://foundation.mozilla.org/advocacy and filed this ticket

[kristinashu]

Also opened https://github.com/mozilla/foundation.mozilla.org/issues/2688