Lean Data Practices Landing page + 4 supporint Pages:
Project Board
Master Project Doc
Current Page
Resources from Client
Copy doc
Success Criteria
I'm curious about the Wordpress requirement. Do they expect to be updating it frequently? From the mockups it looks like a good candidate for a static site.
I'll ask Mika.
@stephaniehobson - Mika said Legal is good with a static website. I'll change the requirement.
@rraue - Mozilla owns leandatapractices.com and it currently redirects to https://www.mozilla.org/en-US/about/policy/lean-data/
The desire is to have the new Lean Data Practices content (nearly done) live on its own website and we're wondering, w. regard to SEO, if it is best that is live on leandatapractices.com - or - if live as a subdomain to mozilla.org (perhaps as 'leandata.mozilla.org).
Please provide your recommendation for a URL for the site.
There is basically no Seo-traffic on this page so I would redirect this question back to a Brand question. I would say, that core-content of what Mozilla does, do we want it external or on the website?
A subdomain I wouldnt use for this, as the volume around this keywords is too small and tehre will be not much content either. So the url right now is good and the domain mentioned by @ejregithub is good as well, if Brand doesnt want it nearer to Mozilla.
But another question: what is the success metric of this page? There is in the new mockup a download button for the toolkit, but pretty much hidden in the footer and if usage of the toolkit is the success metric, I am pretty sure the current page will perform better.
@ejregithub can you please provide some context as to the reasons why this update is in the form of a microsite, and not just a series of updates to the existing pages on www.mozilla.org. If there are some good reasons to spin up a separate site for this then that's fine, but there is a long term cost of keeping microsites up and running, as well as ongoing maintenance required (asking for our SRE's).
Perhaps the horses are already out of the barn on this particular project, but this is exactly the kind of thing Protocol is supposed to solve. We could pretty quickly build this set of pages without fully polished designs from an (expensive) agency.
I don't know that this site needs a unique brand and interface, unless it's purposely meant to stand apart from the Mozilla brand. If we need to match these designs it'll mean building from scratch, which takes longer and incurs more technical debt. Overall we should be striving for fewer microsites and more consistent design, not the opposite.
If it's not too late to rethink the requirements I'd recommend building this on mozorg using Protocol and treating the designs as a wireframe guide. If there's a compelling reason for it to be a standalone website I'd still recommend using Protocol for it if possible.
@alexgibson - I pinged Mika, who inherited the project. She's okay with this going on mozorg at /about/policy/lean-data/ with the requirement that the leandatapractices.com domain redirect there remains.
@rraue - this is an old design from The Brigade, we can largely ignore old bits, building it with our new toolkit. And the branding, while also out of date in the mockups, is intended to reflect the mozilla global brand.
Thanks all for winnowing this down. I'll update the Success Criteria
Most helpful comment
Perhaps the horses are already out of the barn on this particular project, but this is exactly the kind of thing Protocol is supposed to solve. We could pretty quickly build this set of pages without fully polished designs from an (expensive) agency.
I don't know that this site needs a unique brand and interface, unless it's purposely meant to stand apart from the Mozilla brand. If we need to match these designs it'll mean building from scratch, which takes longer and incurs more technical debt. Overall we should be striving for fewer microsites and more consistent design, not the opposite.
If it's not too late to rethink the requirements I'd recommend building this on mozorg using Protocol and treating the designs as a wireframe guide. If there's a compelling reason for it to be a standalone website I'd still recommend using Protocol for it if possible.