Home of the Stanford Web Services Blog
Posted by Greg Garvey on Tuesday, November 17, 2015 - 8:05am
The development team was recently given the opportunity to stand up a Drupal 8 REST server with the intent of improving on our D7 content server, learning what's new with the framework and seeing how our content types would fit into the revised architecture. Having just attended BADcamp at UC Berkeley, we were excited to use Drupal 8 and its new special sauce (yml, composer, console, bigpipe, twig, etc).
Over four days in October, I found myself once again, wandering the campus of UC Berkeley and attending BADCamp. I've lost count of how many times I've attended BADCamp. I think I attended the first camp and have just kept coming.
Our team created the Stanford Sites Jumpstart service to help website owners focus their energy on what matters most: their content. To do this, Jumpstart includes a dashboard for simple content maintenance. This "Manage Content" feature offers an overview of all pages in the site and supports updating individual or multiple pages at one time.
While Stanford Web Services can be seen as a service provider, often involved with custom projects and closely working with clients, one of our core offerings is also our Jumpstart product. With any product offering company, as adoption and usage of the products grow, more and more customers give feedback and express interest in the future direction of the product. Lately, our group has been contemplating increasing transparency in our product development roadmap, and to what extent.
Posted by Johan Baath on Friday, October 16, 2015 - 11:54am
If you're writing CSS Injector styles to adjust the look of your Drupal site, it's easy to accidentally get what I call "CSS bleed" into the administrative experience, which can make things look pretty funky on edit screens. In this tutorial, I'll quickly explain how to avoid overriding the styles of your administration theme.