MozillaFoundation / plan

What the MoFo production teams are working on
https://build.mozillafoundation.org
18 stars 4 forks source link

WordPress workflow? Alternatives? #188

Closed mmmavis closed 8 years ago

mmmavis commented 9 years ago

Excuse me for my loooooooooong post :cold_sweat:

Currently many MoFo sites are built in WordPress: eg. Hive Learning Networks, Advocacy, MozFest, Fundraising... and more

Current Workflow (definitely not optimal)

  1. Fresh WordPress install
  2. Create a theme and build everything in the theme code. (ie., minimal or zero widget usage). Almost everything is built as part of Theme. This means site content is coded as HTML within the template files. (ie, we are not pulling content from the database)
  3. Create a Github repo to store the Theme code
  4. Push Theme code to Github
  5. ssh to server(staging/production) and do git pull there.
  6. Push subsequent commits and repeat Step 5.

Pros

Cons

Thoughts?

mmmavis commented 9 years ago

@simonwex

thisandagain commented 9 years ago

cc @hannahkane

davidascher commented 9 years ago

For a bunch of these sites, I expect a static site generator with embedded disqus comments is likely just fine. e.g. Jekyll, Octopress, … Combined with a travis hook to publish on github commit, it means that simply making a push of a markdown file can update the site. It's also easy to setup prose.io to make it possible for people to edit those files in a web browser without having to learn git. I'd be happy to show you next time we're both in the office if you want @mmmavis

cassiemc commented 9 years ago

<3 that you're tackling this @mmmavis. Besides also addressing your pain, which is important, I would love to see how the solution to this problem can help streamline ux & design across mozilla properties. One mozilla ftw!

toolness commented 9 years ago

I personally really like using WordPress Admin as a backend for CMSes because it's both easy to use, fully-featured, and tons of non-devs are already quite familiar with it. What frustrates me more is WP front-end/theme work, since like Mavis and others I'm extremely rusty on my PHP.

For a pro-bono site I worked on, lifeofthelaw.org, I wrote a node-based front-end that talked to a WordPress back-end using the excellent WordPress JSON-API Plugin.

There were some pitfalls to this approach, but one particular advantage was that it allowed the site's content creators to continue using the same WP admin backend without needing to migrate data or learn how to use a new user interface.

jbuck commented 9 years ago

If we just need a way to edit content, https://prismic.io/ and then we can do whatever we want with the front-end?

gesa commented 9 years ago

+100 @davidascher's comment on Jekyll, Prose.io, and Travis. I've done this several times for clients and family members, it p much always ends with happy users.

alicoding commented 9 years ago

I would suggest https://ghost.org/ since they are open source and it's written in JavaScript. The benefit here is that it's really easy to use and it also supports multi-user. Writing a plugin or adding anything is just like using any other node npm's module, so nothing new to learn here.

mmmavis commented 9 years ago

Hey guys, thanks for the great feedback. I'll have to do lots of research before I can start asking questions again. If we can settle an improved system it will benefit our future projects a lot!!! Fingers crossed!

For our existing WordPress sites, since we are kinda late to the game and have no resources to port everything to the new system... I'm gonna see how I can make use of this popular WP plugin ACF to make both site admins and my lives easier. :pray:

mmmavis commented 9 years ago

@davidascher cool I will find you when I go to the office next week.