Here at SiteFarm, we're proud to offer a service with a whole host of valuable features, functions, and options to help you build a quality site that truly represents your department online. Chief amongst these features is security.
The Bay Area Drupal Camp (BADCamp), hosted this year by UC Berkeley from October 18-21, is an annual gathering of members of the Drupal community to engage in all-day summits, training sessions, presentations, work sprints, and networking with social activities in the evenings.
We interviewed Alex Russell, one of SiteFarm's earliest adopters, to find out more about his journey in exploring the service and expanding beyond its framework to discover unique solutions to his web site needs.
One of the key reasons that Drupal has been successful is because we always made big, forward-looking changes. As a result, Drupal is one of very few CMSes that has stayed relevant for 15+ years. The downside is that with every major release of Drupal, we've gone through a lot of pain adjusting to these changes. The learning curve and difficult upgrade path from one major version of Drupal to the next (e.g. from Drupal 7 to Drupal 8) has also held back Drupal's momentum. In an ideal world, we'd be able to innovate fast yet provide a smooth learning curve and upgrade path from Drupal 8 to Drupal 9. We believe we've found a way to do both!
You may have noticed on our home page we've added a list of events that include mentions of the upcoming Stanford Camp, DrupalCon, and Bay Area Drupal Camp (BADCamp). If you're wondering, who is this for? It's for you. If you're not sure if you should go, let's talk about how you might evaluate that question.
In a recent status update from Drupal founder, Dries Buytaert, we’ve learned that the already released Drupal 8.2, and the upcoming release of Drupal 8.3 in April 2017, provide significant inroads to high-value features requested by content editors in the Drupal community’s latest 2016 survey, in particular, workflows.
Updates to content workflow will appear in two different ways; content save states and workflow permissions prior to content being published.