-
Notifications
You must be signed in to change notification settings - Fork 805
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add new connect splash screen content. #9138
Conversation
Chat with us: https://jetpack.com/contact-support/ |
Just some quick feedback!
@joanrho The only goal of this page is to get people to connect. Do you think the "chat with us" or "search our support site" buttons are necessary? |
@jeffgolenski Thanks for the review and feedback! I'll get on the styling once we have the scrolling worked out. As for the "chat with us" and "search our support" site buttons, that section already exists in the current longer disconnection full-screen banner, so my version updates that as a way for uncertain users to reach out for help before deciding. Here's what the current (old) one looks like: I don't think we should nix this just yet, but we may decide to later on if we see that few users click through to those support options. |
Thanks for the review @joanrho and @jeffgolenski ! @jeffgolenski about this:
I'd argue here that one more request doesn't hurt that much, while we have the benefit to make changes to the logo in one place if needed. This PR also makes the settings masthead include that logo as a file. |
This is ready for review again, @jeffgolenski . Thanks for the feedback! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this, @zinigor! I added some minor styling to the "not now" dismiss text and increased the bottom padding.
Did the font style issues get resolved? I know @zinigor is on a linux machine, but we're seeing both system fonts and helvetica in his screenshots. |
@@ -14,6 +14,7 @@ import analytics from 'lib/analytics'; | |||
*/ | |||
import { getSiteConnectionStatus } from 'state/connection'; | |||
import { getCurrentVersion, userCanEditPosts } from 'state/initial-state'; | |||
import { imagePath } from 'constants/urls'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not defined when we're building the static.html file for the loading screen, so the console is always giving me a 404 for this path, even though the logo is showing after it loads.
Some things I noticed:
|
Let's merge this as is and address the choppy logo and other to-dos in another PR, is that alright @dereksmart? @jeffgolenski can you take a look at the logo svg and the other checkboxed items I posted? |
I'm not seeing this @rickybanister. Can you test again and see if you are? |
I've updated the styling so it better matches the hierarchies in my original mockups and removed the word "fascinating" from our TOS line in Ready for review and to pass on to whoever for next steps (disconnected dashboard?). |
That looks much better. Let's get this merged! @zinigor @dereksmart, what's the best way to copy this to the dashboard, should we rewrite it and duplicate it? Are there any other viable solutions with less duplication? Can we use some interpretive thing for the links that get 'pre-processed' by the php and react code so we can reuse some meta template for the content and copy? |
@rickybanister -- the good news is that @oskosk is currently working on a solution so we can reuse components in html/templates, so we only have the write them once. The bad new is that to take advantage of that, this whole PR would have to be re-written in React. |
@zinigor This seems to be in great shape to be closed—want to go ahead and merge it? Thanks! |
* Set boilerplate for 6.3 in readme.txt * Add changelog for 6.2.1 to changelog.txt * Set boilerplate for 6.3 in to-test.md * Sync Stable tag to 6.2.1 * Add #5647 to changelog * Add #7956 to changelog * Add #9138 to changelog * Add #9573 to changelog * Add #9728 to changelog * Add #9732 to changelog * Add #9752 to changelog * Add some testing instructions * Add #9823 to changelog * Add #9780 to changelog * Add testing instructions for #9780 * Add #9525 to changelog * Add #9782 to changelog * Add #9828 to changelog
Fixes #8900 and #8617
This still needs some work:
I was hoping I could get some help with this from the design team.
Changes proposed in this Pull Request:
Testing instructions:
Proposed changelog entry for your changes: