The question “Would you put your credit card info on a website that doesn’t have the love green padlock?” should elicit the same vehemently negative response as “Would you wade through a pool of piranhas without wearing chainmail?” Admittedly an SSL certificate isn’t the be all end all of safe browsing, but it’s a rather visible baseline indicator of how seriously the site owner takes security. It’s like what a friend told me about OSHA inspectors: they look for bad housekeeping and a sloppy work area, as they’re indicative of much bigger problems.
I’d first heard of Mautic on the first day of my internship with InboundRx (and truth be told that’s the first time I’d heard of marketing automation – I’ve worked with web analytics and email marketing campaigns, but the idea of setting stages and points for your participants and having software facilitate the process flow was something that lay outside my loop until then). The idea was to use this as an alternative to Hubspot which is regarded as the proverbial Cadillac of such services (with features and price tag to go with that), and we were tasked with customizing this open source tool with modified branding and launching an instance of it on the cloud.
Continue reading “Marketing Automation and a Cluster of Cloud Services”
And I have myself a custom WordPress theme, created almost from scratch. Well, almost a complete custom WP theme. I’m still working on it. Yeah, yeah, WordPress, blah, blah, it’s everywhere, it’s stupid simple, it’s not what the cool kids do… or so they say! I’d spent the closing months of 2016 learning how to customize Drupal, which by consensus is the more sophisticated sibling of WordPress in the CMS family, yet I kept thinking to myself, “I gotta spend time with WordPress!” Continue reading “Eight Days and Thirty-Seven Commits Later”
I’d been wresting with SASS over the last couple of days while working on a WordPress custom theme, and while my brain feels like it’s been kneaded a bit, I gotta say I’m pretty chuffed with what I’m able to figure out. Continue reading “Less WET, More DRY, Whole Lotta SASS Be Goin’ on Here”
As a simple exercise in site-building, I’d decided to recreate an existing corporate website (originally made with Drupal 7) in WordPress. No, I won’t tell you which website, but as far as getting the baseline platform up and running went, WP is truly hard to beat in terms of ease and speed. Continue reading “Site Building for Fun and (Eventual) Profit with WordPress”
For the past couple of weeks, I’ve been working with Mautic, the open-source inbound marketing automation tool. Thus far I’ve set up Mautic on:
- Cloud 9 development environment
- Heroku (unsuccessfully – see below)
- Digital Ocean Droplet
- GoDaddy Virtual Private Server
With the current version, Mautic dropped support for Postgres, which seems to be the database of choice for Heroku (I set up one of our Epicodus group projects there and had to migrate the database from MySQL to Postgres), and trying to get the app to work with CloudDB and Google SQL weren’t terribly successful. So, no Heroku for you. Or for me. Continue reading “Setting Mautic Afloat in the Cloud”
I finally did it. After how many false and less-than-true starts, I’m publishing content related to me! A number of these previous iterations had been either standalone HTML/CSS/JS creations or a handful of Drupal 7/8 installs that stalled out. Turns out that good old WordPress seemed to be the fastest way to get posting. Customizations, Material Design revamps, groovy plugins are somewhere down the road, but first things first, content.
These are little notes to myself, filed under “TILT” (Things I Learned Today). I intend to keep ’em coming.
The following links were invaluable in prepping the deployment environment and getting this site up and running in very short order:
The Composer and phpMyAdmin links aren’t as germane to this particular deployment, but they’re great references for other applications, namely Mautic.
Addendum: in order for pretty paths to work, not only does the .htaccess file have the proper permissions to be written by the server, the Apache .config has to specify AllowOverride All (n00b error of not having the correct path resulted in /headdesk for a goodly while).