Closed japick closed 8 years ago
I don't work with Wordpress other than to fix things on my wife's site. I was leaning towards a static site as I don't think I'm ready to dive fully into WP.
With something static it opens up the opportunity for more developers to contribute now and in the future.
I've been using Nunjucks from Mozilla (although not totally a static-site, it templates well) and am certainly not opposed to Jekyll. This also makes the site extremely portable!
I'm more than happy to be swayed towards Wordpress or a sort of CMS, though. :smile:
Happy to roll with Jekyll (not used Nunjucks). Although, using an open-source CMS like WordPress would, in my opinion, open more doors re future developers, as I'd hedge my bets that more devs use WordPress than a flat file alternative like Jekyll, for example. But then again, going down the 'static' root would be quicker and require less maintenance...
I'm leaning more towards static now!
I'm totally fine spinning up a droplet for WP or maybe even seeing if we can get VisualPeople to sponsor a WP instance but I suppose if we can avoid a DB I'd be pretty happy about that. You're right, though–there are a lot of WP devs out there. I am a fan of starting out static, though.
Static for now? Decision time. :smile:
Yeah lets just go with static for now then!
If considering a CMS, I recommend ProcessWire. Very refreshing for anyone used to some legacy tentacle-monster-CMSes :) Good intro article: http://code.tutsplus.com/articles/4-reasons-to-choose-processwire-as-your-next-cms--cms-25062
For now let's just do static. 👍
Hosting with GitHub is amazing.
I was thinking WordPress would be most suitable for the site's back-end - unless you had a preference already? I work with WP on a daily basis, so I'm more than comfortable using it.
What were your thoughts on this?