Skip to content

Contact Form Gutenblock#27996

Merged
enejb merged 71 commits intomasterfrom
add/gutenblocks/contact-form
Nov 10, 2018
Merged

Contact Form Gutenblock#27996
enejb merged 71 commits intomasterfrom
add/gutenblocks/contact-form

Conversation

@georgestephanis
Copy link
Copy Markdown
Contributor

Syncing stuff from Automattic/jetpack#10256

This PR supersedes the prior PR, #27688

Most discussion has been on the Jetpack PR, where the bulk of active development has taken place.

@matticbot
Copy link
Copy Markdown
Contributor

@ghost
Copy link
Copy Markdown

ghost commented Oct 22, 2018

Warnings
⚠️ "Testing instructions" are missing for this PR. Please add some.

This is an automated check which relies on PULL_REQUEST_TEMPLATE. We encourage you to follow that template as it helps Calypso maintainers do their job. If you think 'Testing instructions' are not needed for your PR - please explain why you think so. Thanks for cooperation 🤖

Generated by 🚫 dangerJS

Comment thread client/gutenberg/extensions/contact-form/components/JetpackFieldMultiple.jsx Outdated
@simison simison requested a review from a team October 30, 2018 15:14
@simison simison added the [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. label Oct 30, 2018
@simison simison requested a review from a team October 30, 2018 15:16
@simison
Copy link
Copy Markdown
Member

simison commented Oct 30, 2018

We recently removed jetpack textdomain from Jetpack blocks, so this PR will need some changes to work with that setup.
See PR #28088 for background + example.

Copy link
Copy Markdown
Contributor Author

@georgestephanis georgestephanis Nov 9, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
'If left black, feedback will be sent to the author of the post and the subject will be the name of this post.'
'If left blank, feedback will be sent to the author of the post and the subject will be the name of this post.'

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I fixed these. Good catch!

@georgestephanis
Copy link
Copy Markdown
Contributor Author

There's a number of inconsistencies as to whether or not the jetpack textdomain is used in the __ calls

Copy link
Copy Markdown
Member

@simison simison Nov 9, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just noting that eventually we'll need to look into moving hardcoded colours into variables, especially since some of these are Gutenberg-core colours. Won't need to happen in this PR though.

https://github.com/WordPress/gutenberg/blob/4dcf338ba603f47bf6027a764ab0b0d389e81700/assets/stylesheets/_colors.scss#L15

See e.g. related posts block:

// @TODO: Replace with Gutenberg variables
$dark-gray-300: #6c7781;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same with a lot of the other CSS properties and values as well. It's also always a good idea to start early.

Comment thread client/gutenberg/extensions/presets/jetpack/index.json Outdated
Comment thread npm-shrinkwrap.json Outdated
Copy link
Copy Markdown
Contributor

@roccotripaldi roccotripaldi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Panama people!

@simison
Copy link
Copy Markdown
Member

simison commented Nov 9, 2018

Not a blocker for anything but just wanted to flag this. Wonder if we can improve on user expectations how the button will look like at the site:

I'm using the latest master of Twentynineteen theme.

In the editor—
screenshot 2018-11-09 at 22 50 08

At the site—
screenshot 2018-11-09 at 22 51 02

When I create a button block, I see a similar button like at the frontend:

screenshot 2018-11-09 at 23 05 46

Perhaps using button component would work visually better?

@roccotripaldi roccotripaldi force-pushed the add/gutenblocks/contact-form branch from 218adff to 6a5338c Compare November 9, 2018 21:15
@enejb enejb assigned enejb and unassigned georgestephanis Nov 9, 2018
Copy link
Copy Markdown
Contributor

@lezama lezama left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great work everyone, 🚢 IT !

Let's keep iterating on following PRs

@enejb enejb merged commit 418de14 into master Nov 10, 2018
@matticbot matticbot removed [Status] In Progress [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. labels Nov 10, 2018
@sirreal sirreal deleted the add/gutenblocks/contact-form branch November 12, 2018 10:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Goal] Gutenberg Working towards full integration with Gutenberg

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants