Skip to content
This repository has been archived by the owner on Apr 1, 2021. It is now read-only.

Implement the basic landing page in Mezzanine #68

Closed
8 tasks
Pomax opened this issue Mar 9, 2017 · 5 comments
Closed
8 tasks

Implement the basic landing page in Mezzanine #68

Pomax opened this issue Mar 9, 2017 · 5 comments

Comments

@Pomax
Copy link

Pomax commented Mar 9, 2017

Based on the work done in #98, implement the landing page as shown on https://redpen.io/gsccb3006ea4b5ee5a in Mezzanine:

Implementation status

  • page header model

  • clubs blolck model

  • testimonial block

  • signup block

  • aggregated landing page model

  • landing page template

  • page header template fragment

  • page footer template fragment

@Pomax Pomax self-assigned this Mar 9, 2017
@Pomax Pomax changed the title Implement a basic CMS page in Mezzanine Implement the basic landing page in Mezzanine Apr 3, 2017
@Pomax
Copy link
Author

Pomax commented Apr 3, 2017

Basic implementation doc: the page itself can be separated into several functional blocks, some of which are base schema data for a "landing page" type, some of which are ForeignKeys into separate models for capturing the information that needs to be presented on the page but is more specific instances of independent models.

thingakajigger 2

@Pomax
Copy link
Author

Pomax commented Apr 3, 2017

required building blocks based on implementation design:

header

This can be a written as a template fragment without a model backing

  • logo image
  • nav bar - built by tapping into mezzanine
  • user block - this has to wait until we have a viable login system

page header block

Backed by a "page heading" model:

  • title heading
  • description
  • in-page navigation link to sign-up block

clubs block

For now, backed by a "clubs highlight" model:

  • title heading
  • one to three "club summary" blocks based on club data, using:
    • the club's image
    • the club's name
    • the club's description
    • a (relative) link to that club's site URL

testimonial block

Backed by a "testimonial" model:

  • personal photo
  • personal quote
  • "who said it" name
  • "who said it" location, but only country name

signup block

Backed by a "signup" model:

  • heading

  • description

  • "engagement action" block, backed by an "egagement-action" model:

  • input field placeholder

  • "do it" button label

  • "where to submit this field's data" URL (true submit unless JS loads on top to turn it into dynamic JS)

  • consent checkbox

  • consent description

footer

This can be a written as a template fragment without a model backing

  • a whole bunch of engagement links
  • mozilla logo
  • moz description

@comzeradd
Copy link
Contributor

@kristinashu @Pomax do we have the Zilla font in woff/woff2 format, so I could use it for the headers? Otherwise I'll use Open Sans for now.

@kristinashu
Copy link

@comzeradd Zilla still isn't available yet (should be available any day now) so yes, please just use Open Sans or Fira for now.

@Pomax Pomax removed their assignment Jun 6, 2017
@comzeradd
Copy link
Contributor

This is no longer in scope. Landing page has been implemented in Wagtail.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants