You can view the slides here or download them via the links below.
Drupal 8.7 will be released on May 1, 2019. As Drupal 8 continues to evolve, the content authoring experience has become amazing, especially when compared to past versions of Drupal.
The data is there. Somewhere. Can you find what you’re looking for? Can you find it again later? Can you share it with others?
Tools like Google Analytics are powerful, but unwieldy and inscrutable to the uninitiated. The interface offers a ton of information, but how do you know where to quickly find what you need? How do you share a snapshot of a certain metric with stakeholders? And, how do you make sure that everyone’s looking at the same data – particularly when that data is actively changing?
DevOps, CI, Build, Test, Deploy! There are so many different components flying around this buzzword-compliant practice, it's hard to know where to start. (Spoiler: always start with low-hanging fruit!) But the promises are very attractive: Fewer bugs, faster deployment, greater confidence in your changes.
Learn practical tools and workflows from those of us already in the trenches. We will cover:
Decoupling with Drupal has been a topic of much discussion in recent years. With the shift towards more projects being built for multi-channel experiences including mobile apps, wearable devices, digital signage and others, Drupal’s powerful capabilities of flexibility around structured data and editorial experience have worked hard to adapt.
If it is true that the meaning of all communication is the response it elicits; then what should we do to get the results we need? By reducing communication into the simplest parts, it is easier to see their interactions and there-by understand the complex results. We will tour the communication process to understand where it happens, show how it functions, and why it breaks.
We are developing our Drupal 8 contribution module, Cloud by practicing Scrum for Agile software development. I'll introduce the background story of the reason why we could successfully achieve our super-fast paced development with higher productivity.
The Agenda:
Backdrop CMS is the Drupal fork. It is a faster and less-complex version of Drupal 7 with more features you want, and fewer you don't.
This session will highlight the Backdrop Mission, it's intended audience, and it's guiding principles.
We'll explain the decision making process, introduce the Project Management Committee, and expand on how the project's direction is set by the needs of the whole community.
We'll cover topics like how we handle Security and Stability, and talk about how we're trying to decrease the cost of long-term website ownership.
You're in charge of a website. Or two. Or a dozen. Or several thousand.
In any case, you're "responsible for the health of the service".
What does that mean? How can you, your team, your leadership, or your stakeholders quantify that?
(Spoiler alert: I don't know the answer)
Nevertheless, I can discuss how we at Stanford Web Services track metrics across the following dimensions to try to keep a grasp on the "health of the service":
Views allows people to choose a list of nodes or other entities and present them as pages, blocks, RSS feeds, or other formats.
In this presentation we'll explore Views functionality to display a first list of articles, then create an inline menu for navigating the list.
Don't you wish there was a way to write content faster without having to log into your WordPress site? Turns out there is and it is called Markdown, which can be written in any text editor you choose. Based on the basics of HTML and with a goal of making marked up content as readable as possible, Markdown takes only minutes to learn and is the most transportable way you can write your content. Sites like GitHub, Bitbucket and Reddit already expect it and now WordPress does too.
