* These are so good we should create a Webmaker-branded version
* Maybe Aki can do this next sprint, since she made them
Assignee: nobody → aki
Whiteboard: [resources] [july11]
Created attachment 8446064 [details] m3dgh.png Any thoughts on what we should do with this design-wise? Should I make the text block full-width? Should we put a replacement image in that space instead?
These are likely always going to be for partners, so we can just leave it as a space where they can add their logos. See bug #1032794
Well in that case these are basically ready. They're already templatized, just need content. What we really need, and I can't provide I don't think, is a strategy for slugs. Do you want me to throw these in a new repo similar to the landing pages? That way we don't have to try to fight with existing webmaker.org URLs every time we're doing a new campaign, but rather can have a specific `https://[static-subdomain].webmaker.org/[variable-slug]/` URL format to rely on any time we have a new campaign. Also it means we could spin them up super quickly, and possibly even on the fly without the help of a developer, as needed.
(In reply to Brett Gaylor [:brett] from comment #3) > These are likely always going to be for partners, so we can just leave it as > a space where they can add their logos. See bug #1032794 An unbranded generic webmaker page could be a useful catch-all for smaller partners to use. So long as they use their own RID to promote it, they can all share the same content and we can focus design/content resource on the custom partnership landing pages which will get the most traffic.
Adam (In reply to Adam Lofting (:adamlofting) from comment #5) > (In reply to Brett Gaylor [:brett] from comment #3) > > These are likely always going to be for partners, so we can just leave it as > > a space where they can add their logos. See bug #1032794 > > An unbranded generic webmaker page could be a useful catch-all for smaller > partners to use. So long as they use their own RID to promote it, they can > all share the same content and we can focus design/content resource on the > custom partnership landing pages which will get the most traffic. Great point! Perhaps then we should just put in the maker party logo, so at least that is consistent?
If we're going to include the Maker Party logo, we should reference it in the copy (and creating generic copy for this page seems to me the main blocker on closing this bug), and also be sure to link the graphic to the maker party site. Otherwise, removing the logo section and making the paragraph block full-width sounds like a dandy solution.
Flags: needinfo?(cassie) → needinfo?(matt)
For posterity's sake, I want to note that we decided in a meeting on Thursday (July 3) that we would move these pages over to https://welcome.webmaker.org/ (though we may still want to talk about a standard or base slug)
+ 1 to just removing the logo. Less work, + more evergreen. If Cassie's ok with that design-wise, so am I.
* Aki: that slug sounds find to me.
Matt: we still need a default to come after the base URL though, so https://welcome.webmaker.org/[something-clever-here]
Whiteboard: [resources] [july11] → [landingpages] [july11]
Created attachment 8453273 [details] 2014-07-09-Welcome to Webmaker-1024x1274.png A templatized version, all on github, save copy. Cassie—is it too white without the nav bar?
* Aki: do you still needinfo from me? can we do URLs like: https://welcome.webmaker.org/teachers https://welcome.webmaker.org/techies https://welcome.webmaker.org/parents etc?
Aki I can answer your question once I have a better idea of the user flows. Matt, do we want to be so explicit with the URLs? Might be better to keep the personas internal, and have the URLs more based on what the users can DO as opposed to how we are internally funneling people.
I was under the impression we were going to have one that was a default/catchall, was still waiting on a slug (which I realised I never explained, that's the actual page name, after the last slash) and copy for that.
(by the way I'm realizing now my impression may have been wrong but is still worth thinking about)
For this group of 'self guided making activities' how about: /firstwebpage /makeameme /etc or if you wanted to group them for production reasons: /getstarted/firstwebpage /getstarted/makeameme /getstarted/etc
Component: Teaching Kits / Curriculum → webmaker.org
Attachment #8452808 - Flags: review?(kate)
+1 Adam's first set of URLs. Although, we don't know what the makes will be until we have settled on the content (still in progress). This generic template will be useful for production purposes, though I don't think we will be sending users directly to it. If you need this to live somewhere on webmaker.org though, the slug could just be 'template' or something like that. Aki, the revised flow for this exercise is (from Brett/Andrea): a) Snippet b) Landing page that includes short survey and segments users (note: this is a remix from sending user survey by email - trying to tighten loop) c) Based on segmentation, users are emailed appropriate CTA d) Users that click through will be on the landing page You can follow other tickets related to the sprint here: http://bugzilla-sprinter.herokuapp.com/#/sprint/121 but I'll also update the ones assigned to you as soon as I have a better idea of designs.
Comment on attachment 8452808 [details] [review] https://github.com/mozilla/webmaker-landing-pages/pull/11 I marked a couple of nits, but this is ready to go
Attachment #8452808 - Flags: review?(kate) → review+
Commits pushed to master at https://github.com/mozilla/webmaker-landing-pages https://github.com/mozilla/webmaker-landing-pages/commit/a1e3f55e87f106d00c4e6c54924510e8b3081aec Fixes Bug 1027252 - Create generic, Webmaker-branded versions of "Made w. Code" pages https://github.com/mozilla/webmaker-landing-pages/commit/4eccac1495b123ac951b2fc4898ddb767c6616e5 Merge pull request #11 from gesa/1027252/mwc-style Bug 1027252 - Create generic, Webmaker-branded versions of "Made w. Code" pages
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Since the rudimentary template is built to the best of my ability with changing requirements, I'm closing this and we'll handle any further changes in upcoming tickets.
You need to log in before you can comment on or make changes to this bug.