Views module has long been the killer feature of Drupal, making it easy for a site builder or skilled administrator to essentially create complex SQL queries through a web interface, without knowing SQL.
As we onboard a slew of new clients due to our joining
Seattle, Washington, March 31, 2020. For immediate release.
Seems like every day this month I've answered the same question: Why should I use Drupal instead of WordPress? And this is the answer I've come up with. They are entirely different applications, about as different as Microsoft Word is from Microsoft Excel.
To our clients using our email hosting:
I hope you had a great Thanksgiving!
Yesterday we turned on a shiny brand new mail server.
If you’re making improvements to your sites, even as simple as pushing updates, you’re going to be changing things around. Inevitably, you’ll break something. Wouldn’t you like to find that out before the production site goes down from the “improvements”?
In short, choosing a particular technology allows us to:
Make a decision once and leverage the results over and over
Increase profitability
Increase developer satisfaction
When you build a new website, going live is relatively easy. You get ahold of a domain name, point it at a webhost, put the website code there, and you're up and running!
After a site is live, it gets a lot more complicated.
Glitzy websites are all the rage these days. Everybody seems to be looking for easy ways to create multimedia-rich pages with ease.
Just ran across a sad story where Digital Ocean is accused of killing a startup:
