SendGrid, a MailChimp competitor, pushes forward with new marketing campaign enhancements
While I may be an old dog with decades of experience utilizing websites for marketing purposes, I'm more like a newborn puppy when it comes to email marketing. Until a couple years ago, I never utilized email campaigns or email newsletters in hopes to get more visits to my websites. My current email marketing service provider is MailChimp, but there is another customer communication platform that is on my radar, Colorado-based SendGrid.
This week, SendGrid announced a new editing experience for SendGrid Marketing Campaigns. The new email marketing editor addresses familiar pain points for marketers who previously had to choose between the convenience of visual design and efficient editing of code.
“Savvy, time-starved marketers crave elegant visual design tools that also allow them to quickly and safely edit HTML,” said Steve Sloan, Chief Product Officer at SendGrid. “With the enhancements made to the SendGrid Marketing Campaigns editor, marketers no longer have to choose one or the other. They are now equipped with the tools to choose their own path when editing for flexibility and efficiency, empowering them to drive high engagement from their campaigns.”
New flexible editing options give marketers the ability to edit in code, design view, or a mix of both, minimizes the risk of unwanted changes to custom HTML and delivers time savings and efficiencies. The improved editing experience benefits SendGrid customers whether they send campaigns via Marketing Campaigns or create API triggered templates through SendGrid’s delivery platform.
A few weeks ago during my visit to the local Home Depot, I came across the Ryobi RM480E, an all-battery powered electric riding lawn mower. Ryobi claims that you'll get up to 2 hours of run time or cut up to 2 acres on a single charge. This quiet, smooth battery powered riding mower houses three high-torque brushless motors to support the mower's blades and drivetrain. The RM480E's uses four 12V lead acid batteries instead of lithium-ion which given the choice and given the size of the mower so they're not lithium).
The mower itself has a 38 in. cutting width with a 12-position deck height adjustment. Cutting height ranges from a minimum measured at 1.5 inches to a maximum of 4.5 inches. The mower is capable of cutting in three modes: side-discharge, mulching, and bagging.
I have not reviewed the Ryobi RM480E myself, but overall the mower has received favorable reviews. However, most reviewers recommend that if you have around 2 acres or more you should stick with a gas mower. After 2 acres of mowing, the RM480E will likely require an overnight charge before you can continue cutting the rest of your acreage. The best Ryobi RM480E reviews I've read so far are written by Pro Tool Reviews as well as Paul Sikkema over at Today's Mowers. For the best video review, check out the review by Tools In Actions (embedded below).
Article first appeared at Powered by Battery.
WordPress 4.8 is named "Evans" in honor of jazz pianist and composer William John “Bill” Evans.
WordPress 4.8 is now available and introduces users to new content management tools including three media widgets covering images, audio and video. The "Evans" release also includes link improvements, an updated text widget that supports visual editing, and an upgraded news and events section in your dashboard.
When Matt Mullenweg announced the release of WordPress 4.8 he mentioned that this new version was built with you in mind. While the updates seem minor, he indicated that users will find that the improvements intuitive enough that "you’ll welcome [the changes] like an old friend".
New Widgets for WordPress
As mentioned, Wordpress includes three new media widgets and one rich text widget. Below is a description of all four widgets:
1. Image Widget
Adding an image to a widget is now a simple task that is achievable for any WordPress user without needing to know code. You simply insert your image right within the widget settings and see it appear automatically.
2. Video Widget
You can now add any video from the Media Library to a sidebar on your site with the new Video widget. WordPress gives examples of how this widget could be used including "to showcase a welcome video to introduce visitors to your site or promote your latest and greatest content".
3. Audio Widget
Despite the increased popularity of video in content, interest in podcast creation is making its own comeback. WordPress sees their new audio widget being welcomed by podcasters, musicians, and avid bloggers. Users just need to upload their audio file to the Media Library, go to the widget settings, select your file, and the page is ready for listeners.
Sometimes I get too nostalgic over computers or software that I once used in my daily life. I remember my first computer (the Commodore Vic-20), I remember my first programming language (BASIC), and I remember my first spam filtering software for user generated content (Akismet). But nine years ago, a new spam filtering service originally intended for Drupal called Mollom emerged and I quickly forgot about the other spam blocking software.
I was first introduced to Mollom by Dries Buytaert via an invitation to beta test the service on my websites. After installing Mollom, the amount of time I spent moderating anonymous comments for potential spam was significantly reduced. In less than three years, Mollom had blocked more than 100,000 pieces of spam on one of my websites. Along the way, Mollom was acquired by Acquia and would record blocking over 13.5 billion spam comments worldwide since its inception.
It was a good run for Mollom but unfortunately the end is near. An end-of-life announcement has been placed on the Mollom website notifying users that Acquia will no longer be supporting the service after April 2, 2018.
As of 2 April 2018, Acquia will no longer actively support or maintain Mollom. After that point in time, the Mollom service will no longer be available. If you still have the Mollom module enabled on your site at that point, either all comments will be approved or all comments will be denied depending on how you have the Mollom module configured . We suggest disabling the Mollom module in advance of the end-of-life date.
Although I retired last year from writing stories solely focused on content management systems, I still have a few of my favorites that I like to keep an eye on. One of those favorites is DNN which back in the day we once called DotNetNuke. Less than a year ago, DNN brought to market Evoq 8 which addressed modern day marketing needs for better customer engagement. Last week, DNN showed the industry the ongoing evolution of its product line through Evoq 9. The new release continue's DNN's journey to be more than CMS company as it reaches beyond websites to apps, devices, and other Internet of Things.
Evoq 9's goal is to deliver omnichannel publishing via a microservices architecture. To make this happen, Evoq 9 includes Liquid Content, a new Content as a Service platform that is delivered as a service via DNN’s cloud platform, Liquid Content Cloud. Features included in Liquid Content:
Niels Hartvig recently posted that Umbraco 7.4 has been released. With much focus on improving the user experience, this new version of Umbraco is being subtitled as the "Content type editor update".
Features and improvements highlighted in this update includes:
- New content type editor
- Some UX polish + documentation
- Media library improvements
- Grid polish
- Password for user panel (no dashboard)
- Models Builder
A few days ago, the Agility CMS Team released an update that includes new features and bug fixes. This is the first update since the "big upgrade" threee months ago when Agility introduced a significant rebuild and redesign of its content management system's interface.
Among the bug fixes, probably the most annoying one to me was a bug hat prevented users from being able to delete a linked content item from within grid view. Previously, a user was required to click on the "Edit Content" button in order to remove an item. Before the fix, the work-around was sufficient but annoying due to the changes involved in the expected workflow. Overall though, as a user of the Agility CMS, I've been pretty impressed how much Agility got right in the redesign that the waiting time for the fix was acceptable to me.
As was mentioned earlier this week, today is the day Drupal 8 becomes official and is released for public consumption. The last time CMS Report was given the opportunity to talk about a major Drupal release was in January 2011 with the release of Drupal 7. If you thought the three year waiting period from Drupal 6 to Drupal 7 was long, waiting nearly half a decade for Drupal 8 certainly feels like a lifetime in the world of content management. During this cycle of development, Drupal's own open source community has evolved and its developers have introduced hundreds of changes into the Drupal content management platform.
Since the release of Drupal 7, the Drupal community considered not only how they could influence the content management industry, but has also looked outward to consider how the best practices of developers, designers, and publishers could influence Drupal's own to build a better Drupal. Dries Buytaert, founder and project lead of Drupal, in a blog post remarked that "Drupal 8 has been a big transformation" for the open source community.
The pace of change in the digital world has become dizzying. If we were to ignore these market forces, Drupal would be caught flat-footed and quickly become irrelevant.
I admit it. When looking at the calendar my eyes have been focused on November 19, 2015. This is the date that Drupal 8, under development since 2011, is expected to be released. But for Drupal 6 users, the beginning of Drupal 8 also marks the beginning of the end for Drupal 6 support. Announced on Drupal.org, Michael Hess writes that Drupal 6 will reach end-of-life on February 24 2016.
As announced in the Drupal 6 extended support policy, 3 months after Drupal 8 comes out, Drupal 6 will be end-of-life (EOL).
On February 24th 2016, Drupal 6 will reach end of life and no longer be supported.
What this means for you:
- Drupal 6 will no longer be supported by the community at large. The community at large will no longer be creating new projects, fixing bugs in existing projects, writing documentation, etc. around Drupal 6.
- There will be no more core commits on Drupal 6.x to the official tree. (see What if I have a Drupal 6 site still)
- The security team will no longer provide support or Security Advisories for Drupal 6
All Drupal 6 releases on project pages will be flagged as not supported.
- At some point in the future update status may stop working for Drupal 6 sites.
The policy of the Drupal community is to support only the current and previous stable versions. (When Drupal 8 is released, Drupal 7 will continue to be maintained but Drupal 6 be marked unsupported.) This policy was created to prevent Drupal's core and module maintainers from having to maintain more than two active major versions of Drupal.
Three years ago, CMS Report made the jump from Drupal to the Agility CMS featuring its Magazine Publishing Suite. Since then, I've had the opportunity to see Agility's software evolve including improved delivery in the mobile space through responsive web design. While gradual improvements were made in the CMS, probably the biggest change for Agility Inc. was in late 2013 with the appointment of their new CEO, Jonathan Voigt. When Jon was appointed CEO he promised a refocused vision for Agility that would provide better products and improved services for Agility's paying customers. This autumn, Agility fulfills that promise as it rolls out a significant rebuild and redesign of the content management system's interface.
Agility has announced that they have started pushing out the new version of its popular web content management solution. Besides the interface improvements, the new version of Agility CMS also introduces a new Dashboard feature as well as significant improvements in software performance and task workflow.
"This a huge step forward for Agility CMS. The legacy content manager was built out 8 years ago, and it served us and our customers well. This new, upgraded version provides the same user-friendly experience – but it’s sleeker, faster and provides more value to all that login to the platform,” Jon Voigt, CEO of Agility CMS, said.