PM / Business

“Back in the day” web development was all about Projects. Project Managers met with clients to gather requirements and then worked with designers and developers to meet those requirements within a set amount of time. 

In today’s world, more people are working on web “Product” or “Platform” teams where they are serving the needs of both site editors and site visitors while running continuous integration and continuous delivery/deployment processes.

A couple of years ago, the H&S Web team split its time between running new projects and responding to support requests on live sites. Today, the support work has shifted.  From a reactive place, we've moved to a more proactive model. 

One of the cornerstone practices has been our maintenance reports, which we are now calling our continuous care reports.  Three times a year, we reach out to our units and share a report containing what feels most relevant to their ability to keep up the health of their sites. 

The marketing department at Stanford Health Care is responsible for the content in an extensive and dynamic web ecosystem, including 10 websites containing about 25,000 pages of content. This session will explore the tools and processes involved in the creation, publication, and maintenance of web content within a consensus-driven organization.  

“We need to think about accessibility before we start any of our work, before we write any line of code, at every step of our development lifecycle. Shifting left means thinking about accessibility at the start of every step we take when we deploy new software or services.”

Learn how Higher Ed leverages power of Backdrop CMS for various use cases - from building new sites to upgrades from Drupal 7 before EOL. Topics include business case, selecting hosting platform, authentication, training for users and many other challenges.

The presentation will transition into open discussion about using Backdrop in Higher ed and non-profit space.

Failure happens. We’ve all experienced failure, and it's not fun. But, it does give us the opportunity to learn and, ideally, to plan better for the next time disaster strikes.

The web technology stack is ripe for failure because there are often so many pieces at play. Web servers, database servers, content management systems, third-party plugins, caching layers, networks, DNS… not to mention all the people who can bring a website down with the touch of a finger.

Drupal is the swiss-army-knife of content management systems. It provides the flexibility to build pretty much any site you want. This is why so many of us choose Drupal for our backend technology.

Jamstack vs Static

You can find tons of resources on Drupal with React, Gatsby, Next, Vue and Nuxt, yet not so much static-focused non-Jamstack content beyond using the Drupal Tome module (which is a great tool!). Why are JavaScript frameworks such a hot Drupal topic yet simple static frontends not so much? I think static Drupal has a marketing problem!

Join us for a quick welcome session and get an overview of WebCamp.