Jetpack is Wow

Thanks for the feedback!

too much module. some can be separated to different plugin.

I assume you know that already, but anything that’s deactivated under Jetpack > Settings won’t actually load on your site, so never hesitate to deactivate what you don’t need!

too much script loaded separately. what’s the point of having it as one plugin? (a minify module could be useful?)

We’ve actually worked on concatenating all CSS into a single file, but we haven’t done so for JS files yet. That’s on our radar, though!

contact form do not support template files.

Could you give me more details about this, or create a GitHub issue with your ideas?

Thanks!

awesome support
– several features/modules is must have (essential) for every site.

Well thank you ??

yes I understand the settings. and some modules actually depend on each other (and wp com api). it’s still too “monstrous”.
but i totally understand the “concept”. I probably going to do it the same way if I was the dev ??

about scripts:
that’s a great news. I’ll look forward to see how you’ll implemented it ??

about contact form:
I think the implementation relying in post meta is a weird and awkward.
the large (not so short)code need to be added in content, shortcode inside shortcode, unable to manually block email address/spammy text string, the CF pop up unusable in mobile device, etc.
here’s an issue about what I mean (do shortcode in template/not template friendly): https://github.com/Automattic/jetpack/issues/102
I can’t suggest anything to CF module, except a complete (or if not complete than it’s a lot of) rewrite ??
(but that’s just my personal opinion)

but, CF module works well if used as basic CF (which is what it is),
submitted entries logged in admin, akismet integration, etc.

but overall. jetpack still an awesome plugin. and knowing that it’s maintained by automattic, give a piece of mind. (in the end it’s about trust)

thank you so much for your great work!

Thanks for the extra details!

There are indeed a lot of things we could change about the Contact Form. ??

Since you mentioned a few examples, I linked to the related GitHub issues below:

the implementation relying in post meta is a weird and awkward.

https://github.com/Automattic/jetpack/issues/3118

unable to manually block email address/spammy text string

https://github.com/Automattic/jetpack/issues/430

CF pop up unusable in mobile device

https://github.com/Automattic/jetpack/issues/1055

If there are other things you’d like to change, feel free to open new issues! A complete rewrite would indeed be a solution to some of these issues, but it’s not a small amount of work, especially considering the myriad of options and filters that should remain functional after the rewrite. Jetpack’s Contact Form might be a “basic CF”, but its options and filters make it quite flexible ??

thank you for the issue links.
good to know that you and others are aware of these issue.
I do understand that it is not easy. It is a complex plugin.