mozilla / fxoss Goto Github PK

In the admin when editing a page if you click "view on site" in the upper left you get a url that looks like:

http://fxoss-dev1

Followup to #4

The mini title font is looking big. Suggest bumping down to 16px to see if it can get closer to PSD.

Left is PSD Right is site

Currently the styling appears to be broken

Tighten up the margin/padding under the intro paragraph to be closer to PSD. Left is site, right is PSD note the space between the bottom of the paragraph and the start of the grey area is slimmer.

@bensternthal requested a doc be provided for know snippets:

Refs #67 & #49. Once all default snippets are defined, we should dump a set of fixtures as well.

Trying to test the form content type the following occurs upon multiple refreshes:

1. Page displays error
2. Page displays form but no css
3. Page displays lessc not found error.

Screenshot of #2
https://www.evernote.com/shard/s24/sh/53e0d09c-fe1c-40a0-b315-42820391f186/d4585e986331a7534148964a45d3eb06

Screenshot for #3
https://www.evernote.com/shard/s24/sh/938e2047-9864-4cfc-9096-e76e57731252/927ba9da3c9cdde6448f481b65669bb1

My test form is called 'testing form'

#40 exposed an issue with the profile update form. We override the profile form to capture Salesforce data on registration. When performing a Profile Update, the only fields expressed should be the baseline user fields that the Django User model is storing.

Top text flows off screen in mobile layout.

Even after #3 the project layout from mezzanine is a little messy. We should move the settings and urls into a project module like the Playdoh layout https://github.com/mozilla/playdoh/tree/master/project. All of the name parsing and sys.path hacks should be removed from the settings and manage.py.

Add .zip as an allowed file extension.

Increase download size to 100mb (if possible, if less than 100 go as high as we can)

Testing the click through we noticed that once the download kicks off, you are left on the click through page.

See https://mobilepartners.mozilla.org/firefox-os-brand-toolkit/ for an example.

The use case looks like there will be multiple downloads on that one page. So if possible we would like:

1. User clicks download link
2. User presented with click through
3. Download kicked off
4. User redirected to previous page

The user can then proceed to download more files.

It feels weird to leave them on the agreement.

The left-most td in mini-table will get squished if the content in the right td is long.

The main Page content model should have the following text based fields. We need to extend either via Mezzanine's field injection or via subclassing the Page model.

• Title: Text Field
• Subtitle: Text Field
• Intro Paragraph: Text Area
• Content: Rich Text Editor
• Closing Paragraph: Text Area

Details in this bug:

https://bugzilla.mozilla.org/show_bug.cgi?id=964917

There are some additional fields we need to capture during user registration:

https://app.box.com/files/0/f/1508496125/1/f_13618024035

Some of these fields will be stored in the database, some will be routed to Salesforce and stored there. Need to delineate which fields belong where.

If i try to upload media I receive an HTTP error. The file does not get uploaded

Brand was renamed to market!

Holy cow so once this change is made I will go through and edit all the slugs on dev and prod.

Left is site, right is PSD. Note the bars in the PSD are patterned.

Please increase the upload file size from 10mb to 100mb. I want an adequate buffer just in case.

Non-superusers Content Authors need a group with perms to Add/Change/Delete:

• Forms
• Pages
• Media

may be other perms needed, but those are the bare minimum for the initial phase

The grey divider that appears above H2s is considerably larger and more pronounced than designed. See screenshot, top is rendered on the site, below is the PSD.

The messages framework needs to be reincorporated into the frontend (or uninstalled if not desired as it causes cruft for logged in users in admin.).

https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/core/templates/base.html#L71

Possible point of implementation: https://github.com/mozilla/fxoss/blob/fxoss-theme/sandstone/templates/base.html#L50

• Needs styling/layout
• Needs JS for closing of messages

Please add a class for " »" so the space and arrows can be added to links without hardcoding.

Hard to give you clear guidance on this.... but the left nav I think can be improved.
Right now the hover and click to open behavior is (to me) a bit unpolished. I know you made some changes here due to mobile nav but I am hoping we can get this feeling nicer.

Can we change the opening / closing to be the slide up/down or make it smoother?

I am open to suggestions on this one.

I am getting the basic http authentication prompt on dev now (good) but when I try to view the site as just a viewer I get redirected to the admin login.

The registration branch has the user panel (login/logout) embedded in the left nav. Final designs indicate these should be in the top nav

• Signin >>
• Hi, [email protected] | Signout >>
  • Email clickable (change password form)

Login on dev goes to mezzanine login not the nice blue login for the site. Works OK locally.

Need to style the form presented to the user prior to downloading the protected content assets.

See screenshot. Note h2 heading "Firefox Marketplace" does not appear when site is viewed. It is contained in the source.

The link tool currently only allows images to be linked to as downloads.

Note in screenshot how the zip file is greyed out.

Please enable for all uploads.

https://www.evernote.com/shard/s24/sh/57c56cbe-4cd9-43c2-97e4-12ec3283f876/eb48f90e26f9ad9181e3b894d246968d

We will need to customize the text in the welcome email and forgot password email. I did not see these as templates in the code base.

Can instruct on how we would customize this text?

https://mobilepartners.mozilla.org/brand/contact-mozilla-form/

The form should just have the red asterik, no need to also display the "required text

"

If you click the image insert tool in the wysiwyg edtior a blank window appears with no content.

See Screenshot:
https://www.evernote.com/shard/s24/sh/c24dfc77-2b59-483a-980e-5400dfc7f659/c6b3036f8f5eb68fc311480b15615105

We will need to moderately tweak the organization and layout that Mezzanine provides to conform to Mozilla Deployment SOP.

Ref: https://github.com/mozilla/playdoh/tree/master/project/settings

Subtitle should not be a required field.

Now that we have the design and copy samples in hand, the custom Page fields need refactoring:

• SubTitle becomes Call To Action Title (text field, optional)
• Closing Paragraph becomes Call to Action Body (Rich Text, optional)
• Inherit from root parent (checkbox, Root Parent Title and Intro Para used on render)

Utilize the samples from #49

We have a known node in the tree of RichTextPages that needs to render content for authenticated users or static content for unauthenticated users.

• Create a custom brand.html template

TinyMCE On Prod Has Different Editing Options see screenshot

See: https://mobilepartners.mozilla.org/learn/

We will need a left nav to support linking to the items under the 3 main sections.
The design is being flushed out here

https://bugzilla.mozilla.org/show_bug.cgi?id=966318

Marking as not ready to code pending design.

Typo on login button.

https://mobilepartners.mozilla.org/accounts/login/?next=/accounts/login/

Lower parts of letters with h2 style are cut off. See "g"s in screenshot

The title tag is not being rendered in the content area of the template.

See screenshot, note title Learn entered into mez but not rendered.

https://www.evernote.com/shard/s24/sh/93e009f4-f212-4338-8a82-3dac2518a951/ee45225e979b9f2d4a691dc8cf636975

Based on the current workflow diagrams, logged in users which have accepted the download agreement should have access to the restricted downloads. Need a couple pieces here:

• A way to manage which downloads should be restricted
• The enforcement of signing the download agreement

Using the test form, i do not receive an email to my entered address when the form is submitted.

I am able to login and view the submissions.

There are two issues here:

• Procedurally, content authors should know to always place items in the Top Nav (if they are Left Navigable)
• Adjust Top Nav dropdown.html template to only render child nodes when responsive kicks in and the top nav collapses

If we do not do the above, left nav nodes will have no navigability when the site hits non-Desktop breakpoints.

Running Firefox Aurora on Linux