Popular posts

I know a lot of WordPress developers who use Vue and love it. It’s different from the other options in that it scales down as well as it scales up. You can drop it in and start coding like jQuery, or use it to build a complex single-page applications or server-side rendered apps.

That seems very much in the WordPress philosophy to me. You can start a WordPress site without having to do much coding, then you can add in plugins, then configure those plugins, then build your own plugins and templates, etc. WordPress scales with their skills and Vue offers a similar learning path.

That said, no one knows the needs of WordPress like the WordPress team - there are always considerations outsiders like me aren’t aware of. So no matter what happens, I trust that they’ll have weighed all the options and made the best decision for their community.

I know you asked for other opinions from other members. I will add that i think all the core team are on the same page, and will support the Wordpress team as much as we can.

We hope all the best for the team, and support any of there decisions they will make now and in the future. At the moment it is still early days, and it is unclear on the move they will commit too. If however they do switch to Vue as a default, we will find ways to embrace the Wordpress community and the team to ensure they get the best results.

As a WordPress developer/user myself, I'd be more than happy to see Vue integrated with WP at some level – project Guttenberg is definitely a good start. Whatever WP team's decision may be though, including possibly coming with an entirely framework-agnostic solution, we'll for sure be supporting it and offer help wherever we can.