Hello, everybody. Welcome to part four of the Sophia Code. I am having so much fun with this book. This book has already become such a life-changing book for me. And based on the feedback that I'm getting from you, you are also enjoying this work as well. Today, we're going to be finishing up the first section of the Sophia Code next week. We'll start into section two, which goes along with all the activation with the Sophia Dragon tribe key code mentors. But before we get started, I am being led by Magdalene to smudge my system because attacks are vicious right now because we know we're at the very end and the devil doesn't go away peacefully. So right now, I'm just going to call on Michael and Gabriel and all of my guides that are here for my highest good. If the person that's watching right now would like to consent, then they can consent to the same thing for their own system, but that's only if you consent. I'm asking that any beings that are here negatively that are not here for my highest good or the viewer's highest good or humanity's highest good to please leave my space, to please leave the space now. I send you back to Source Creator. And again, I ask that all guides, all beings that are here for our highest good be allowed in during this here now moment. I'm also going to ask Magdalene to please be present and to please help me say what needs to be said so that your message is clear. Alright, so this starts us on Chapter 5 of Modern Mystery School. The Way of Self-Initiation. This next golden age is an invitation for you to reveal the unlimited depths and heights of your sovereign creative power. Rather than seek for the world to change for you, you are the change. You are here to embody the reality of heaven on earth that so many within your species seek to discover outside of themselves. The golden age of miracles. The High Council speaks. A golden age is a cycle of time in which quantum evolutionary leaps become accessible to a large population of humanity seeking to embody Sophia Christ consciousness. Sophia Dragon Drive serves all ancient and future golden ages at certain evolutionary junctures. The return is highly visible guiding light council for catalyzing golden ages on earth. As many of you are already aware, humanity is now being prepared to participate in a new golden age cycle here on earth. The dawning of this next golden age cycle is unlike any other. This revolutionary age begins with an unusually high volume of incarnated master souls that are ready to serve this quantum wave with you. You are now walking to earth with many advanced souls that have traveled great distance across the cosmos to be by your side for initiating this global awakening. And this very much was saying the same thing that the law one is saying. We are in a very, very special time in our planetary history, in our collective consciousness, and also in the cosmos. And most of us are what the law one calls wonderers where we are actually have already been harvested. We've already ascended multiple times, but we came back to earth into a third density body and order to hold the vibration to be able to push earth into fourth density positive versus fourth density negative. Now, as I've said, because this is a battle, the dark forces also sit down beings that are highly evolved in the dark arts to wage this war. But for everyone watching right now, you are very, very special indeed. Remember that your practice as a living master is to recognize, behold, and bless the masters that walk beside you in this great endeavor, both seen and unseen, regardless of all outward appearances. Keep your eyes open to see beyond the surface of any mundane role that your star seed brother or sister may be playing as part of their mission here on earth. Great ancient masters may dress up or down or play their chosen role in the riveting chapter now unfolding as a foundational precursor to this next golden age. Sophia has ordained this next cycle to be known as the Golden Age of Miracles. This title points to the unusually high amount of incarnated souls amassing to embody the full divine potential for their higher selves in a single lifetime. The Golden Age of Miracles is also a seated name for telling the countless miracles that will come to pass from this many master's souls consciously converging and unifying as a global community for humanity's ascension. One of the many miracles of this dawning age is that embodying the sovereign power of your higher self liberates the Akashic record vaults of humanity's collective suffering without the need for you to suffer for anyone's relief. That is to say, the lives of billions of people are directly transformed by your personal willingness to embody the Sophia Christ light of your higher self. The authentic embodiment of your sovereign divinity broadcasts a transmission of freedom from the activated crystalline chromosomes of the Sophia code within you to the dormant DNA of countless souls. The long one talks about this. They talk about how when you get into fourth density from third density, all of a sudden, you have what's called a collective memory bank. For example, if you want to understand and feel the lessons that I learned being the target of a coven, you could just tap into it because my experience becomes part of the collective experience. You can literally tap into what I went through or anyone else for that matter to receive what I learned from that without having to go through it yourself. I know that's such a weird concept because in third density, it's not like that. But that's one of the things that's going to be coming in fourth density. And that's kind of feels like what she's saying here, through the living transmission of your higher self embodiment, people who are suffering beyond their understanding will experience the freedom of your life through a holographic transference of upgrades for their consciousness. For as you embody the golden radiance of your higher self, the seeds of humanity's collective consciousness will part for millions to follow your lead as you walk the way of your sacred heart. Yes, indeed, you are a way sure for this golden age of miracles. The next golden age is an invitation for you to reveal the unlimited depths and heights of your sovereign creative power. Rather than seek for the world to change you, you are the change. You are here to embody the reality of heaven on earth that so many within your species seek to discover outside of themselves. Your personal passion to radically serve humanity's ascension is mirrored in your own collective desire to wholly support you in this lifetime. With your invitation, we are here to mentor you in a modern mystery school curriculum for embodying the sovereignty of your higher self as an initiator for the next golden age of miracles. And so we kind of spoke about this last week regarding mystery schools. Mystery schools to me are very, very, very fascinating and they're not bad. They didn't start off as bad. They got inverted by the dark side, the dark ones, the controllers. And as I've said almost every episode, the darkness can't create anything. The darkness can only take from the light and invert it. So everything you see was a one point created for the light including mystery schools. And we're taking those suckers back. Your modern mystery school seek not the ancient mystery schools for another age. Daily life is now your modern mystery school activating your highest potential in every present moment. With your conscious daily choice to mentor with our ascended master high council, we prepare and activate your awareness to become a wayshower for others in birthing this next golden age of miracles. So in this lifetime, class is in session every day. In order to live in alignment with reality of miracles, you are now being guided to access your soul's initiation and personal training for embodying your higher self from masters abiding in the highest light realms of creation. Accessing our daily guidance beyond your physical reality creates a direct path for recognizing the master that already lives within you. As ascended master mentors, we provide the same mystery school initiations that you once physically received in other lifetimes for activating the spiritual technology of your human body from the higher dimensional realities. Receiving these same initiations in this new way activates the power of your faith to download direct revelations which is a precursor for commanding miracles. Your faith reveals the master who already lives within you when you believe that you can directly commune with us to receive our blessings. Divine intervention, soul initiations, DNA activation, emotional support, or personal coaching across multiple planes of reality. Cultivating your ability to receive our direct revelation occurs one self-loving step at a time in the modern mystery school of your daily life choices. We invite your consciousness to consider that the extraordinary opportunity of this next golden age is to become the embodied miracle of your own faith as well as living embodiment of the direct revelations that you can download from your higher self. This is your lifetime for the master within you to be revealed and witnessed in the presence of other masters both seen and unseen. As you reach for us in our moment by moment support, you build a bridge from our dimensional reality to yours. This results in your physical reality resonating with the high frequency vibration of our steadfast presence guiding your awareness. Your willingness to reach for our frequency raises the vibration of your entire being to regularly receive quantum solutions for your life. As we reach for you in our daily communion, we create bridges that ground our heavenly frequency within your dimensional reality on earth. Our intention is to create new neurological pathways for multi-dimensional relating through personal mentor relationships that radically support your willingness to consciously live your life in absolute sovereignty. Over an arc of time, our daily communion eventually aligns you an ever-increasing measure with your role as an initiator and wayshower for all of humanity. We are co-creating this radical modern-day mystery school with you and our evolution is mutual in this heroic journey of awakening all beings to their divine inheritance of the Sophia Code. So we encourage you to celebrate your daily life as a ceremony of ascension, surrendering to an age of grace. The seeds of all miracles is faith and the space in which those miracles blossom is called grace. The underlying momentum that is preparing humanity for this forthcoming golden age of miracles is your collective desire to surrender into grace. Grace is an invincible present that cannot be bought, sold, or traded for. Grace cannot be earned for it is freely available regardless of all circumstances. Grace is never withheld yet her presence is most often recognized during divinely appointed hours of individual and collective awakening from suffering. Grace is the space that your soul was birthed in free of any conditions placed upon you for the gift of your eternal life. Grace is the space where what is ready to return to the natural balance may spontaneously return to that balance without apology, explanation, or delay. Grace is the space in which you may experience and even enjoy your sovereign divine nature. Humanity is ready for the spaciousness of grace. Grace knows how to end wars that humanity does not know how to end. Grace knows how to be at peace when humanity does not know how to be at peace with itself. Grace knows how to forgive what feels unforgivable. Grace also knows how to love what feels unlovable. Grace is the sanctuary of space from which quantum solutions arise that end the need for all suffering. Grace allows for the seemingly impossible to miraculously appear without effort as a direct revelation of divine love. Other than your willingness to receive her mighty works, Grace does not need human participation to work a perfect divine will for all to be boundlessly blessed. When you surrender to grace, you are surrendering to the Holy Spirit within all that is orchestrated every day miracles for you beyond your understanding and beyond your ability to control a desired outcome. Humanity's faith in itself and in a benevolent universe will only be restored by receiving the grace that humanity believes it has lost. Grace is the invincible divine feminine Christ consciousness that has never left you and who lives within you. As you surrender to her mighty works and miraculous solutions, your faith will be reconciled. There is no greater motivating force in this universe than the primordial space of mother. Our divine feminine Christ blueprint is designed to awaken humanity from its addiction to suffering which is rooted in an agonizing belief that humanity is irreconcilably separate from its original mother. Therefore, humanity's collective prayer for the next golden age is to surrender and reconcile with the unconditional love of Sophia whose presence has never left you. Sophia is the one self and there is no greater teacher for reconciliation than she. Every complementary force of nature that humanity has polarized through duality exists harmoniously within Sophia's whole self. Therefore, Sophia's grace is a fluid dialogue that includes both divine feminine and divine masculine rays of consciousness speaking as both a unified voice as well as individuated polarities that can only exist within the empty space of the oneself. As an immaculate quality of Sophia, Grace is a perfectly balanced divine feminine presence whose great works are supported by divine masculine qualities that harmoniously complete her miracles. The divine feminine Christ revelations of Sophia are beyond humanity's gender identifications of God or goddess figures. These revelations exist beyond hierarchical concepts of right or wrong and point to inevitable mysteries and a state of grace that can only be explored by surrendering to your own innocent nature. To explore the unknowable, bow to the universe within you and confess that you know nothing. Surrender your need to control what you understand about Sophia as a primordial holy mother of grace. Lay down your need to feel safe through limited earthbound logic and linear thinking. Open to her inevitable mysteries and quietly await your humble prayer to receive the grace of these revelations as they are not as you would have them fit into your current paradigm of right or wrong. When you discover that the presence of Sophia exists within you and within all an equal measure, this great movement to surrender to the grace of unconditional love may unfold for all of humanity. Therefore, we invite the causes of all internal and external wars to now rest their heads in her primordial lap of divine love forever. Returning to the fluidity of divine feminine Christ consciousness can be as graceful or as hard as you want it to be. Our creation story is a powerful invitation to explore the grace of your soul sovereignty from within the holy of holies of Sophia. The power of that invitation requires grace to accept it. As the oracle order of the devotee Shikina, the Sophia Dragon tribe proclaims all form as holy. We pronounce that Sophia is the Christ within all incarnated bodies and the vessel of every form that carries her holy spirit is the christened form. Therefore, we are each the body of Christ returning again and again to the world of light and form to proclaim her holy grace and sovereignty that exists within all according to the Sophia code given to all an equal measure. Humanity is one key code species that makes up this universal body of Christ. As humanity takes up its mantle of divinity, there will be a great shift to embody a noble humanity as surrendering to grace in which humanity will be welcomed back into the interstellar diplomatic dialogue regarding the earth's evolution as stewards and guardians of this beloved planet. Embracing the divine feminine Christ consciousness begins with embracing the primordial aspects of Sophia that exist within you as the grace that you are here to offer yourself and others. You may discover these divine revelations of grace already calling you to go within as you read this invitation to discover these inevitable mysteries of the universe within you. As such, this introductory volume of the Sophia code cosmology introduces the first eight of thirteen essential divine feminine ascended master teachers of our modern day mystery school for humanity's collective awakening and return to the divine feminine Christ blueprint for this planet's ascension through grace. Every key code mentor was responsible for birthing new paradigms of heavenly consciousness on earth including the reclamation of the form as holy. These feature key codes are exceptional mentors for your own embodiment of grace as a birther of this next golden age of miracles through the immaculate conception of your Sophia Christ consciousness. Five ways our mystery school teaches you. We use five non-linear interdependent operating systems of quantum communion that initiates a divine feminine awakening for your awareness to interface with your higher self and activate the Sophia code within you. The architecture of our high council is designed to offer advanced metaphysical teachings that directly download into your soul and awareness without effort. Our divine feminine teaching model intentionally bypasses the limitations of your logical localized mind and initiates you into the oracle art of divine knowing. These five operating systems also activate your body supporting neurological pathways that allow for direct communion with your higher self and are as follows. One we use the mirror of relating with you. Every ascended master key code offers intimate details of her challenges and successes in the world of form as inspirational fuel for your own human journey. This transparency creates accessible heroic examples that mirror your own potential legacy for this lifetime. Divine feminine vehicles for awakening create a feeling response of equanimity and accessibility and accessibility that softens inspires and empowers you. Two we speak the language of your soul. Our divine feminine key codes share ancient knowledge and raise of wisdom that already exists within you. As you experience the many aha moments that may arise as you read this codex these full body soul recognitions liberate the master within you to confidently awaken. Divine feminine vehicle for awakening creates spontaneous self recognition responses that invoke your acceptance and celebration of the master within you. Three the mastery of yourself initiation. This codex presents transcendental key code initiations written in the first person perspective so that you may read them aloud. As you speak the key code initiation with the resonance of your own voice you are consciously using the sovereign power of your higher self divinity to command your own empowerment for spiritual activation. Our initiations are designed for you to easily recognize honor and embody the master that already lives in you. Divide feminine vehicle for awakening create a self-initiatory response that builds confidence to command miracles and trust in your own divine knowing. Four the communion of our mentorship. We offer mentor relationships designed to stimulate your own self empowerment.  These extraordinary mentor relationships build confidence for clearly seeing yourself as one who deserves to receive the best support for embodying your highest potential. Divide feminine vehicle for awakening create a safe container for your self empowerment through the experience and support of our multi-dimensional communion. Five visions awaken the oracle within you. The ascended masters of the Sophia dragon tribe are known throughout the history for their auricular abilities to prophesize and reveal their direct visions and teaching revelations of Sophia. Visionary states of consciousness are direct revelations that provide full downloads of multi-dimensional blocks of information.  Therefore we offer a visionary teaching transmission that awakens your own auricular facilities. This codex is a richly detailed vision of the Sophia code cosmology which has been directly downloaded for you by their very nature. Visions activate the same auricular facilities of those immersed within the shared multi-dimensional experience. Stepping inside the visions of this living transmission provides both an accessible interface and permission slip to explore your own auricular abilities for seeing and hearing your ascended master mentors. Divine feminine vehicle for awakening create a multi-dimensional container that activates visionary states of consciousness by sharing of direct revelations through visions.


maybe experiencing some symptoms of the pulmonite last night. It's one of the big reasons I wasn't there. It's a real pleasure to be here at Triple Camp London. I want to thank all of the organizers and the sponsors of this event. Let's give them all a big round of applause. So this is actually only my third time in the city of London. But I've been to the UK many other times. I actually, while at university, spent a good amount of time living in north Wales. Can anyone tell me what the name of London is in Welsh? Llynda. Llynda. That's exactly right. How about Manchester? Anyone? Can you make your hands in here? Yeah, got some people from Manchester. What about Manchester in Welsh? My opinion, back in the UK, because a lot of my studies were here. Actually, at university, I did my research in Welsh language policy. So all of the things that I've been hearing about in terms of Brexit have been very interesting in the Welsh society. That's for sure. So today, a bit of a zoomed-out perspective of true role. And I'm calling this section de-contextualizer content because there's a little bit of too much context in true role. And I want to talk a little bit about that in just a little bit. But first, let me just get a sense of the room here. How many people are new to true role? A few of us. How many people are copywriters or content strategists or content marketers in the room? Okay, got a few of us there. How many people have worked with de-contextualizer role? All right, great, perfect. Well, I hope this session has something for everybody. But please don't hesitate to give me feedback afterwards. And I'll be happy, of course, to answer questions. Just to introduce myself, my name is Preston. I have been involved in the true role community for about 11 years. And I was, until yesterday, the director of research and innovation at AQUI. Actually, though, briefly about my book. If you haven't looked at de-coupled Drupal before or if you're getting into de-coupled Drupal, I have a book out with a forward by Dries. It's called De-coupled Drupal in Practice. And I'm very happy to talk about that book with you afterwards if you'd like. There's a lot of really good information in there about de-coupled approaches, architectures, and builds. How many people have read the book or wrote the book? Okay, great. Thank you. Thank you for your support. As a commander, I just recently announced on Twitter that I'm moving to a company called Gatsby. For those of you who haven't heard of Gatsby, Gatsby is a static site generator that works really well with Drupal and is built in a react. I'm happy to talk more about that a little bit as well. It would be nice to put this up. I was actually in Cluj-Napalpa last year on the heels of Drupal Hack Camp in Bucharest. Wonderful place. I think it's gonna be a great event. I'm very excited for it. Also, I would be remiss if I didn't mention our conference that we've got in New York City. De-coupled days. We took Drupal out of the name this year. We've got a bunch of new tracks, including JavaScript and Jamstack, as well as different headless CMS approaches besides Drupal. It'll be held July 17th through 18th. We'd love to see all of you there. It's just a short talk across the pond. And one of the things that we have open right now is our call for papers. So if you'd like to submit a session, please feel free. We're gonna have that open until the end of DrupalCon in Seattle. Also, we have sponsorships still available. If you're interested in sponsoring the event and want to be noticed by decoupled practitioners, we've got a lot of interest from sponsors and we actually only have one of the diamond sponsorships remaining. So please, if you'd like to talk to me about that afterwards, please feel free. Okay, that's it for the ads. Had to put in all those blocks. Let me talk about, very briefly, what we're gonna cover today. And first, I wanna talk about what is, one of the things that I've been thinking a lot about in Drupal, which is what I call the complexity chain. And this is something that Jerry's recently posted about and his blog post about how to decouple Drupal in 2019. I also wanna talk about the Diffusions of Innovation Theory and how Drupal has played into this theory and how it's not over the last few years. I also wanna talk about how people have thought about and conceived about actually harmonizing the various experiences that we have, whether they're built in Alexa or in the reality, all of these different experiences that I've worked with on a daily basis. And then I wanna talk about what I mean by a decontextualized content strategy and what that means for Drupal itself. First, let's talk about the complexity chain and crossing the cast. And I think this is a little bit of a big picture perspective of Drupal, but I think it's very helpful for us to map out how exactly Drupal's history has been impacted by a lot of the trends that we've seen in web development over the last few decades. Drees by Tom Reese has been posted this blog post about how to decouple Drupal in 2019. There's a flow chart that's very helpful in there and it gives you a lot of information about how to decouple Drupal. But later in the blog post, there's a figure that looks like this. And this figure generated quite a bit of discussion at Acquia among our team because one of the things that we've noticed quite a bit over the last couple of years, especially over the last 12 months, is what I call motion along the complexity chain. If you consider the fact that on the left side, we have a build or a technology that's very easy to use for people who are not developers. On the right side, we have technologies that are more difficult to use and require more development experience. One of the things that we've noticed over the last 12 months is that many of the JavaScript developers who are using large scale frameworks like AngularNumber is that these frameworks have become extremely complex for more than just simple static sites. They become very complex and they should really only be used for highly interactive complex applications and they should really be used for static sites. So while this realm of technology has really moved up in terms of complexity, we also have a corresponding motion down where technologies like Gatsby and static site generators are now beginning to take the lead in adopting more of this middle ground for people of various scale levels. But I want to note here that what I'm talking about here is not actually real complexity, right? Because it's not necessarily true per se that these JavaScript frameworks are more difficult. Rather it's the perceived complexity. It's what we actually think about when we think about building an entire application and we act, or we think about building an entire application in Drupal. And we see this right now in Drupal today. Just this morning I was having conversations with a few of you and learning that many people in this room are already thinking about replacements or substituting different technologies for Drupal front end. So for us in Drupal, this is what this looks like to us, is that as Drupal theming and Ajax and all the things that we're used to in building interactive features into our Drupal sites, has those things become more complex for novice developers or those who don't write DHP or don't write Twig? At the same time, a lot of the new approaches that we're seeing in JavaScript are becoming less complex for us. And some very good examples of this are Vue and of course, Gatsby. Now one of the biggest issues with this whole trend is that we're losing the ability to hire Drupal talent very easily. Front end Drupal talent, especially nowadays, is very difficult to come by. It tends to be very expensive. Consider for example, these current trends that are occurring in decoupled rule. If you consider the fact that in JavaScript we're now seeing a motion towards the more novice developer where people are saying maybe we need to make things a little bit easier for people who are just entering into web development. If you consider the fact that there's now the Create React app projects, for example, in the React community, or also projects like Vue that have really taken on this idea of incremental adaptability and ease of use. We also know, as mentioned by Drees, that these static site generators like Gatsby are actually simpler limitations for a lot of people and have actually helped to offload a lot of these responsibilities that we formerly had to worry about off to different services such as Neverbot. And we also see, as I just mentioned, that Drupal front end developers are turning to these technologies because they do tend to be a little bit easier to use. Because Twig can be very complicated, as I think we all know for those of us who have worked with Twig. And as we said, one of the biggest challenges that people are finding is actually resourcing and staffing their teams. And this is not just a technological issue. This is now a resourcing and a human issue and a business issue that affects each and every one of us. As an example, many organizations are finding it difficult to find affordable front end Drupal developers experienced in Twig. And moving to a job from the front end can resolve some of these resourcing challenges. How many folks in here work at agencies that have had trouble hiring Drupal talent? A lot of us in the room. So today I wanna propose a different approach. And I wanna talk about this and couch this first and foremost in content strategy. So once again, we know why people want to use decoupling and decouple Drupal over Twig. It's because it's the perceived complexity. And it's the fact that we're not really seeing a whole lot of people excited about Twig these days. It is a PHP technology. It is something that's not necessarily something that is very enticing to people who are just entering the development today. And Drupal's complexity, perceived complexity, and this sea-coupled movement that we're seeing right now in the community is leading to these questions. Like, oh, why should we use Drupal at all in the first place? Why should we even bother if we're gonna be using these other technologies? But the thing we have to remember is that these same tendencies, these same trends, these same paradigm shifts, these same sea changes that we're seeing right now in decoupled Drupal are actually very similar to the trends that we saw throughout Drupal's history as well. Consider the other big complexity chain that we see in the CMS world. And I know that I'm using Drupal Type here. It's a very old example. I probably should have used some other CMSes, but this is just to illustrate very simply. The fact that in the early 2000s, we had this very large trend of dissemination of these blog publishing systems, right? These don't really exist anymore. They don't really exist anymore. They've been replaced by CMSes. And what happened is that people said, well, you know, I want to be able to use something that's more powerful. And I acknowledge that it's gonna be more complex. But in order for me to get to that functionality that I know that people want and that people are demanding among my customer base, I have to move up this chain and I have to move up to a more complex technology. And this first way to see a mass adoption that occurred in the early 2000s to mid 2000s and also late 2000s really shows that we actually had a big gap between what people wanted and what we as developers wanted and what was actually out there on the market. So the big question is, if we consider Moveable Type, a legacy CMS, how do we keep Drupal from falling into that same trap? There's a book by a gentleman called Jeffrey Moore. It's a very popular book that you find in business schools and it's called Crossing the Chasm. Has anyone read the book? Yes, it's a very good book. And it's actually held up remarkably well over the last 20 years. What this book states is it articulates this theory called the Diffusions of Innovation Theory by Everett Rogers. And this theory states that there's a big of this, not the one on the ground type gap, but a large gap between early adopters of the technology, people like us, people who are going to look at things like Gatsby, going to look at things like you and those who are the early majority, the pragmatists, the realists, those who are going to adopt the technology because it really makes sense and has penetrated the market to a larger extent. And more in this book states that marketers who want to actually pitch this technology and sell this technology should target one market at a time amassing just enough buy-in to move on to the next phase. But the most problematic chasm, the most problematic of this is between those two personas, those early adopters and the early majority. And what's interesting is that Drupal has actually already done this, really successful. If you look, for example, at the history of Acquia, you see this. In Acquia's early history, we were very focused on cloud solutions and developer support and all the things that many of us are doing today for our clients. And this was kind of the initial phase. We need to have a CMS that's for developers that works for developers who are building client sites. But we crossed into different personas and different markets that actually worked for a large number of people beyond just those technical developers like us. And those editors who came in and said, well, I need to have workflow, I need to have preview, I need to have all this stuff that we're used to in block publishing systems and in CMS. And then finally today, Acquia has really focused on the market of persona. And many Drupal companies as well have focused on the market of persona because now we want to have more visual control over what's going on and really have a very deep amount of authority over how content is placed on the page and how it appears to the user. But here's the question I want to pose today. Are we now facing a new cast? Are we now losing the developers that made Drupal so successful in the first place? And if so, is it a problem? What do we do about it? Or is it not a problem at all? That's the question I want to toy with a little bit today during the session. So the question I want to ask you all today and I want you all to think about is, is Drupal in trouble? Does Drupal need to win back developers or win new developers? And does Drupal need to cross that cast once again? Do we need to evolve once more into the future and leap into the future? Now let me move to a little bit of a different topic which focuses more on how agencies and how people in the Drupal landscape today have looked at harmonizing these discreet experiences that we see today that many agencies are building. Because the fundamental question we have to ask ourselves in conjunction with those questions I just posed is what will Drupal be for in 10 years? Will it be just for websites? Or is it going to be something that is truly for all digital experiences and what does that actually mean and entail? It all depends on whom you ask. One of the big questions that's happening right now at many large organizations across the world today is whether to centralize data or not. Should we put every single piece of data that we own and every single piece of content that we own into a single bucket that we can distribute out whenever we want to and hand out? There's this concept of right once published everywhere and a single source of truth. But recently we're seeing different trends emerge as well. If you look at Gatsby, for example, Gatsby adopts a strictly data-agnostic approach which means you can bring your own data sources, you can bring your own data, and Gatsby has no need to care about where that data is necessarily from. But one of the things that we're also seeing is that many large companies are saying, well, we're doing this because we see an institutional importance within our company to do this, to centralize all of our content, centralize all of our data in one place. So what I mean by this is that harmonizing with ecosystems, these ideas that organizations are needing to have a complete sense of harmony across all of these experiences and understand where they are and what they're doing is becoming a lot more common as a concern throughout some of the largest companies today. And some of you might have seen some of these figures before, but what I want to do with these illustrations is to demonstrate that we as developers have a great amount of control over what we can do in terms of these experiences that we build. We can build a JavaScript single page application, we can build a mobile app in Swift, we can build any other thing that we can conceive of. But the problem is that once we give this off to our clients, once we give this off to people who are actually going to be editing and working with this solution that we build, we actually have some problems begin to emerge. Editors, for example, can't necessarily preview unpublished content as easily on a mobile app or on an AR mobile app or on a JavaScript single page app, although there are solutions out there. They're heavily developer oriented. Then we think about the fact that marketers and those who really want to have visual control over the presentation of their content have absolutely no control over layout and over some of the things that they want to see happen on a mobile app or on a single page app. So if we want to serve all these experiences in a robust way, we have to think about how our choices that we make in Drupal and the choices that we make during the evolution of Drupal actually impact these other channels that we're building today. So I would like to venture a little bit into why Drupal is possibly in trouble today. And I don't want to be pessimistic about Drupal, but I do want to be realistic. And there's a fundamental problem in Drupal today. And for those of you who follow my talks, this upcoming graph is going to be very familiar to you. One of the things that we're seeing is that what's better for developers is not necessarily what's better for marketers and better for users. We're seeing a change where more custom work by developers is needed to actually make these editors and marketers happy. And we see this today in Decomple Drupal. If you build an application in JavaScript and you serve Drupal data to that application, that leads to a loss of critical functionality. You're losing, quick edit, you're losing contextual links, you're losing some of these contextual features that many of the people in our user base have considered very important for a long time, even if many of us in the community have thought that they're not as important. And so today, if you want to make preview happen, if you want to make in-place editing happen, if you want to make some of these things happen, layout management happen on a single page app, that's impossible without the help of a developer. So the biggest issue is that we have now crossed this chasm and we can't go back in some ways because the editors and marketers are now using Drupal and they expect to have the exacting functionality that they've had for it since day one. And for us, some of us who are architectural carriers, some of us who are really deeply involved in separation of concerns and software, we've always had a problem with the fact that there's this linkage and this coupling between structured data and the presentation of that data because this leads, as we all know, to Drupalisms and oftentimes a negative developer experience. I'm sure many of us have onboarded or worked with new developers who are used to other paradigms who have faced a lot of frustration when learning about how Drupal works and how it does things. So the hard truth is that Drupal itself has become far too coupled between three things. Number one, the presentation layer, the theme layer, the twin, the theme engine, the website itself, the idea of website, the idea that Drupal is for the website and only the website. And of course the underlying web content itself, the content that we all write on a daily basis, the content that we pump into Drupal that is written for a website but not necessarily written for anything else. And if you think about it, the vast majority of all the content we have right now in Drupal is web only content. It's not really meant to be used on other devices. It's not really meant to be something that we put elsewhere. And we know also that from our experiences helping people learn Drupal, helping people understand Drupal, especially people who are using JavaScript or people who are asked to do so by their employers, these Drupalisms can be very, very confusing. For example, one of the things that I've been seeing a lot on the Drupal Slack is a lot of questions about course configuration in decoupled Drupal which has become a little bit more difficult over the last few minor versions just because it's a little bit less successful to the novice developer. You have to go into your services.yaml file and understand Hamel and understand how that file works in order for you to be able to enable cores on the decoupled Drupal implementation. That's just one example. And we also see when we look at API responses in JSON API or GraphQL for those of you who work with decoupled Drupal that sometimes we see a lot of Drupal information leak through. We see stuff like field underscore blank leak through. We see all of these things leak through that are really unfavorable for those developers building these experiences. Everyone scratches their heads. Not only are new developers who are new Drupal who are really confused about some of these ideas but also clients because they're losing some of their functionality. I remember I once spoke to a customer who had been asked to work on a decoupled Drupal with React implementation. And this React app was wonderful. It was performance, it was great. It served content from Drupal effectively. But the client called back six months later and said, hang on, how do I get to my in-place editing feature? How do I get to the quick end? And the agency unfortunately had to tell them, yeah, sorry about that. Yeah, it's not available anymore. And the client was not available. So this is what I want to say when I say that we have a big problem, is that Drupal's biggest challenge today, biggest thing that we face right now at Drupal is that we have to decontextualize Drupal away from the website and from the Drupal website that is what Drupal traffic's in today. We have to get rid of this notion that Drupal is only about the website that it renders because it's not. We know this today. We know this from the presentations yesterday about Gatsby and React. We know this about today's community. We know this about today's evolution of Drupal. And we know also though that context matters. I love this image because it really illustrates some of the challenges that we face. If you think about each of these different screens as a different channel, like augmented reality or mobile apps or JavaScript, you can see that really one of the biggest challenges we face is the fact that only the person looking at the web context sees Drupal as an end-to-end system that works really beautifully for them. But we have to think about contextlessness and how many people have heard of the R.C. Wood message. So the R.C. Wood message is a message that is broadcast regularly by saying. That's the group of scientists who are working on extraterrestrial intelligence and want to tell extraterrestrials about Earth and tell them about humanity. And what this message actually contains is a lot of information about who we are as the human species without any context at all, without any need to understand the English language, without any need to understand, you know, necessarily the way that we use numbers and mathematics. And a lot is communicated here. A lot of this actually contains things like the population of Earth, things like number of days of the year, for example, so on and so forth. And it communicates a lot of information about Earth without necessarily requiring the context of our own understanding of language and mathematics. There's also a concept of contextualization and social linguistics, which is, linguistics is my background, by the way. And contextualization is really interesting because when you think about content and you think about the fact that we really communicate these ideas and the surroundings of our content through this idea of how we communicate and how we actually express ourselves. Consider, for example, how things evolve when you have a new scientific finding that's published in a scholarly journal versus popular science magazine or quantum, versus a Wikipedia article or a college textbook. These different contexts really give a lot of different meaning to the content itself and change the way that we envision how we want to write content and how we want to manage that content. The fact of the matter is that today all CMSs have fallen to this trap, every single one, including even the headless ones, have fallen to the trap of focusing on contextualizing themselves on the web. They assume that the context you wanna display all of your content in is the web and that is today the fundamental flaw of CMSs across the board. So what I talk about a de-contextualized content strategy, what I really mean is that we as content writers, we as content managers, we as content strategists really have to move away from the notion of the web as being the only place that our content will appear. Brett Hanwood is one of, he was a context strategist at Second Life, worked on Second Life again, and worked on marketing communications for Second Life. And he has this to say back in 2013, which is that it's not just a traditional editor role. It's not just a written word and it's not just the web. I have to consider how it might be repurposed and redistributed and actually reoriented on other channels of delivery. And in this article he talks primarily about Facebook, but you can also see in his head that he's thinking about things like the new channels that we're seeing emerge today. So the ideal piece of content that we can write today, and this is a really good exercise in copyright, maps neatly onto any context at all. Consider this brief paragraph, which is the first paragraph of the Wikipedia article about Islington, here at London. If we think about the fact that, okay, this paragraph makes a lot of sense, where can we see it end up? It could end up in a website with a heading and a read more link. This is something Drupal already does very well, for example. We don't necessarily need to add that read more link to every single content block. But it could also be something that appears in a voice assistant, like Alexa. It could be something that we ask Alexa for in terms of information. Is this paragraph something that is okay to listen to as a user of Alexa? These are all things that we have to think about. And of course, in the future, one of the things that we'll see more and more is situational interfaces and in-context interfaces like Avenger reality.  So here's an exercise I would encourage all of you to do with your website or your content. Today or tomorrow, take just one piece of content on the website. It could be a block of content that's reused across the site. It could be a single page of text that you've got when you're doing a site in a node. Consider these questions. If I were to display this piece of content as a card on a mobile app out of context of a website, would it still make sense to the user? If I were to take this piece of content and read it out to a voice assistant, would that make sense to the user? And if I was to situationally display it so that it was in context of it on the reality of the face, would it still make sense? Because the website is not enough anymore today and we can't think about content from the web perspective anymore at all. So, decontextualized content strategy involves from the very beginning enforcing a need, a lack of a need for context in your content. It means actually saying I'm gonna make my content so context less that it makes sense anywhere it goes, regardless of where it ends up. Now, why should we do this? Why is this so important? Well, there's a lot of reasons why. The first is that a lot of us have very small editorial teams. A lot of the organizations that we work with, a lot of our clients don't have large teams. They can't manage 15 different pieces of content based on each channel that that content is going to. Now, what we know of course that sometimes, a large paragraph, a lot of text is not something that's really favorable for certain channels. And that does lead to increased complexity, which is a flaw of this word approach. But if we think about content as a sweet object, as Drupal has trained us to do with its unique approach to structured content, one of the things that we can do is to really anticipate any particular channel that might emerge in the future, whether it exists today or not. So here's some things to think about when you're thinking about writing content and writing content for this kind of approach. The first is that, for example, headings might not make as much sense in a voice assistant. Or a sidebar block might not be something that really displays in a mobile app. And how does that change the way that your user experiences this content? Also calls to action are pretty much meaningless and useless in most other channels unless there's a capability in that interface to navigate to that link or navigate to that different state of your application or screen. And so overly contextualized content really in the future will become a maintenance burden. And we're already seeing this emerge more and more. And I'll talk about an example shortly that I've worked with in the recent past. So when you think about the fact that we have a focus on the web here, if you consider the fact, for example, that we want to be able to display this content anywhere, we have to think about how this content is going to change for each of these cases. And we know that if we can take this paragraph about just totally anywhere, that we can actually display that content really easily anywhere that we go, including on it on the reality of overlay. Once again as we're walking around with our iPad in front of that just totally implication. So this is a possible approach. And I think this is something that has worked for a lot of people, but it might not work for everybody because one of the key critiques of this approach is that there's very little variation between the content. And for those of us who have worked with voice assistants, for example, or chatbots, we know that the mode of conversation, the manner in which people like to interact with a chatbot is very informal. And how does that contrast with something like the government website of the United Kingdom, which has to portray a more formal approach? How do they write a chatbot? Is it the same? Is it written in a different tone? Those are the questions we have to answer as well. So the exceptions rule about, the exceptions where we have to think about, okay, well, this content's gonna be in a different scenario. We have to adjust it in a different way. And so this does leave, if you do write content that is particularly oriented to the channel, that does mean that it's channel optimized. But the problem with that is you have to trade off the maintainability. So that's what you have to consider as a content strategist, as a developer, as an architect, is what are the trade-offs between maintainability and between having that harmony across all of your content? Because our notions of content strategy up until now have primarily revolved around the web. Most of us have probably read content strategy articles that are focused on the web, by folks like, folks, excuse me, folks like, psychosis for example, and others are written on this topic. So we need a different model to conceive of our content. And if we think about content as discrete objects and not as pages and not as blocks and not as visual elements, they can help us to really re-task our approach to content. And as I mentioned earlier, Truthful already has this with structured content. But we have to move off of this web-first mindset. So there's one approach that I would recommend for all of you who are looking at content strategy and looking at how your content performs on different devices. And that is performing a content audit. I used to work on the Acquia Labs team and we built a project for the state of Georgia in the US called AskGeorgia, which was a Alexa skill for citizens of the state of Georgia to ask certain questions. One of the things we did during that project was a content audit, where we looked at every single piece of content that we wanted to adapt to be made conversational and experimented with what are some of the ways that we can fix this content so that it's actually completely context-less and decontextualized. AskGeorgia was a very interesting case study. It was actually a very early adopter of Alexa and Drupal. To this date, I actually believe AskGeorgia might be one of the only Alexa skills publicly available right now that engages in a search on a Drupal site as opposed to kind of written-in interactions that are actually custom. And so some of the things that we did for this project are to rewrite content so that there was less of the calls to action, less of those things that are impossible on a voice assistant. And we wanted to prepare the state of Georgia to be able to actually work with this content in a way that meant they could use it across any channel, including a mobile app, including a chat bot, including SMS messaging file, and a voice assistant. And as you can see, some of the things that we did were to reduce those calls to action and reduce the amount of links that will distract the user or make them confused if they're hearing learn more on a voice assistant, for example. This is a really good example of this. If you're on an Alexa device and you ask a question and you get more about this, that makes absolutely no sense to you as a user of that interface. And that's why we had to add a whole bunch of content here to give the user that ability to say, well, I don't need to go to another link on a website. I can just have the content right there. And this is one of the key problems that we have to resolve in all of our content because up until this point, all of us have written content or have managed content that's oriented solely for the web. So I talked a lot about what it means for content, this idea of decontextualization, this idea of taking away the need for context from our content. Now what does that mean for Drupal? About four months ago, I gave a talk at Drupal Camp Belgium called The Drupal Frontend in 2024. And this is a little bit of a, kind of a culmination of those ideas in a single place. I believe, and this is my opinion, by the way, I believe, I don't know if you agree with this. We'll see. I believe that our aspiration should be to create a CMS that isn't just for websites. I believe that our mission should be to create a CMS and foster an atmosphere for us to build a CMS that is truly for all digital experiences and ecosystems in every single sense of the phrase. And what does that exactly mean? It means that we have to move away from this web-based idea of what Drupal can be. Consider where Drupal is right now. And this is an extremely simplified diagram, but what I want to illustrate with this is to show two things.  If you consider the fact that we have things like JavaScript applications and static sites, which all have some operation of rendering taking place. And then we also have things like voice assistance and chat bots and push notifications, which we have much less control over in terms of presentation. Right now, we can see that Drupal is kind of this single backend. And this backend is coupled with a website, this Drupal frontend, which includes two things. Number one, the theme layer that we all know and love, PHP template or twig. And second, contextual features. As I just mentioned before, contextual features include things like in-place editing, they include things like contextual links, layout management, things that require an understanding from the perspective of the CMS of the presentation layer for. But I want to challenge this a little bit because one of the fundamental issues that I think we face today is how people conceive a Drupal when we say the word Drupal. When we say the word Drupal, people immediately think about websites and PHP. I don't necessarily think that that has to be the case. In fact, right now, we have something that looks a little bit more like this for many of us. If we are working with a large organization, chances are you have an architecture that looks somewhat like this. And yes, the website, the Drupal front, and it's still coupled to Drupal and it still has all these features, but we're also serving all of this data to other places like Angular, Gatsby, to an AR overlay potentially, and all of these things that we're building custom as developers today. In November, I proposed in an argument there that we actually should really redefine Drupal and that Drupal can be more than just a website. And Drupal can be more than just a web rendering layer and a web-based content management system. And an aspirational state for us to end up in is something like this, where we can conceive of Drupal as being the sum of all of its parts of the architecture. Drupal is also the front-end that Drupal itself is not actually rendering. And I'll talk about why in just a second. But first, I wanted to say that one of the things that has come about recently and a lot of conversations I've had with folks in the Drupal community is the notion that we have to move away from this idea of Drupal as a single piece of software. Drupal is much more than that. Drupal is an ecosystem, it's a community. It's actually more than just a single system of software. And we can move from this kind of approach and this kind of idealization of our architecture to something like this. And this is something that is an idea I've toyed with for many years and I've really tried to refine over the course of the times I've given talks about Drupal. But one of the things that is really interesting today that we're seeing is companies like Startups, like Simpla or Prismic, really trying to control a little bit more of the presentation that happens on those Drupal front-ends. Prismic, for example, allows you to actually inject edit buttons into whatever application framework you're using, whether it's React or Angular or Ember, jQuery, they actually allow you to put in edit buttons where every single piece of content controlled by Prismic is located on your single page application. Why can't we do that for Drupal? Why can't we do that for all of the things that we actually see in decoupled Drupal? There could be, for example, an in-place editing feature that we create or that Gatsby creates that integrates beautifully with Drupal. There could be a layout management tool that integrates beautifully with Angular or a contextual links widget that could operate even in an AR overlay as we are editing content on our iPad, walking around the Angular station. So if we think about this as Drupal, we completely reinvent how people think about Drupal. If we say that actually what's available on the Drupal front-end is in-place editing, but you can have that on Gatsby too and you can have that on Angular too and you can have that on Vue too and they all work in an engraving fashion with Drupal. Because that is what will ultimately lead to people understanding, especially those of us who have clients who want to go into these technologies, who want to go into this realm but don't have the ability to give up the features that their editors and their marketers use so on a daily basis. So it may seem counterintuitive because I've been talking a lot about reducing context and contextualization, rather than reintroducing contextual features. And I do agree. It is something that perhaps is a little bit hair-brained and a little bit unrealistic. But the key distinction here is that in a de-contextualized Drupal, all of these different channels that we're working with, whether it's Gatsby or Vue or Unreality or Mobile Apps, they own their contexts, they own their presentation, they own how they display themselves. And that's a totally different idea from what we have been used to in Drupal in the entirety of our history since Drupal's founding. So what does a de-contextual actually mean? The first thing that means is that channels own their presentation. It means that we leave all the issues of reverberating presentation and contextual features up to these channels themselves. This is an idea that we've already been dealing with over the course of the last few years. But also, crucially, as I mentioned last year in Lisbon, it means APIs for everything. It means that every single operation that we can conceive of in Drupal that we do today in the interface or that we do today programmatically has to be something that we can do through API or a remote procedural call. And finally, we have to refocus on developers. And this brings me back to discussing project accounting again. Because in order to attract these developers today who are not using PHP, who will not discover PHP, who are only turning to Drupal because their employers asked them to, we have to keep their interests as well in Drupal. Many people today have never even heard of Drupal. Many people today who are entering into the tech market and the web dev market have never even heard of PHP solutions or of Sydney. How do we bring them into the fold? So this might be an instrument of a task and it might be impossible. But I think we do have a shot of getting it right. And there are several things that we can do to get this going. One of which is working very closely with some of these other communities that are out there, like Gatsby, for instance. But we need to do three things. And the first is we have to recalibrate our priorities. We have to keep thinking about what it is that Drupal needs to focus on. We have to integrate more closely with other technologies. We have to work very closely with these other teams to actually be able to work with these new technologies that are emerging. And I believe that we need a new API-first initiative. Many people are saying that the API-first initiative is now complete because of JSON API and Drupal Core as of the upcoming release. But I actually think there's a lot more work to be done. And I would love to work on this with all of you as well. We have to retrain our customers as well. All of our customers, most of our customers who have gone their digital transformation journeys to borrow business parlance, are actually writing web-only content without realizing it in the first place. So we have to educate our clients on channel agnosticism, educate them on this idea of writing decontextualized content. And we have to educate them also on digital ecosystems and help them understand that they're not just dealing with one single facet of their organization. Third, we have to realign Drupal's mission. And what that means is we have to focus once again on the developer experience. I think we've done some amazing work on Layout Builder, amazing work as of late on some of the modules that have really gained a lot of steam in the editorial and marketer personas. But the problem with that is that we actually are losing those who are coming into the web dev landscape today. And most entrants to Drupal are today actually obligated to learn Drupal because of their jobs, not learning Drupal organically. And that is a big problem that we have to address. And finally, we need to cultivate a new generation of Drupalists. We have to bring those new learners, those people who are taking those coding boot camps by the horns, those people who are actually going into university saying, I wanna learn JavaScript and I wanna learn React. I don't know what this Drupal PHP business is. And we have to learn from them and attract them to work with Drupal in a new way that has never been done before in our community. So just to end with a few final words here and I'll take questions afterwards and open up for discussion. We have to traverse the new CASM. There is another CASM in front of us and it is the CASM that we have left behind a little bit because we wanted to focus on the personas that we focused on today. We have to win more developers and we have to win them with the right approach. Secondly, we have to decide once and for all whether or not we're going to make Drupal something that is optimized for more than just websites because I guarantee you in 10 years that will be the case of every single new CMS that comes on the content management market today in 10 years. And we have to decontextualize our content to prepare for this future in a channel-logistic way. We have to move content out of its context and move it into an idea of the sweet objects. And then finally, we need to decontextualize Drupal to win over those developers that we've lost and win developers that have never considered Drupal before in the first place. And that means that we have to redefine the what Drupal means and what Drupal actually does for all of these data. We need a new vision for Drupal that aims to harmonize across these experiences and really aims to focus on these ideas. So let's cross the catamac again. Let's focus on these other islands. Let's focus on these developers who are integrating with Drupal who want to have a content management solution that works for them and still enable our other personas because as we learn from our history in Drupal, it was developers who started out building the features that the editors and the marketers want. And here, it will happen again. I promise it and I guarantee it. Thank you very much. I have a really good question. I saw a new book, I thought this was a new book. And I think a small map is a small position. We do things in the last few weeks, the last few weeks, but it shouldn't change easily. And it all sorts out the way to defend against that. And in Drupal, one of the things we did was we seeded that ground. We just didn't bother writing WordPress. We said WordPress is a small site, so we lose a lot of sites. And those are crazy, but you know, we're good to go. And we're moving now to, this is to find a different area to gain that. But I think we still need to seed, we seeded to find a way of our action and make Drupal easy for people, like really easy. At least it's WordPress, because we always give our ground, if we don't. What are your thoughts in this, this completed role as an editor that you should take to undertake? Yes, it's a very good point. And you know, there is something to be excited about, I mentioned the other total experience and the market experience in terms of using the word being in and just getting people to feel that their features are still intact. And that was because of two things. The first is that when we look at how Drupal sits, we really started out. We look at, you know, the fact that really a lot of these people who started to do Drupal in the first place were people who were engineers or engineers or clients. If you look at, for example, like CZK and Muse, those were projects built for clients by those. And they weren't really so bad then. And some of them, some of those people are not silly with that as a whole day, as we would like. I believe that we should still look at some of those, some of those absolutely. And I think that for all the big lies that we have in Drupal, there's a lot of improvement that needs to happen. Nonetheless, I think that we have a finite in terms of ensuring that Drupal stays rather than practically in addition to editoriality and in the market in the States. It's a hard problem. I don't have the answer. And I think that, you know, one of the things that it has come about, for example, is I had a discussion with 10-12 years, one of the maintenance of the layout holder. You know, basically kind of playing with what's happening and saying, why are we doing the layout holder in the first place? It's only going to be relevant as a website. And I think it's true and I think it really illustrates the fact that we have two very different beasts that are trying to serve Drupal community and Drupal business landscape in particular, which are, number one, those clients who need the layout holder right now in yesterday. And then also those clients who are moving into this, and also ages and adults in the real community who are moving into a landscape where we're having a lot of trouble getting into the town. And we have to figure out how to harness both of these in a way that pushes us all the forward. I think really some of the jobs here focusing pretty much all of the attention of the Drupal acceleration team at Apguya on the layout holder and on the API acquisition. And so I think by pushing these two products forward, we can make products happen, product of the products. I do use all of the Drupal DCDs I do with that. But I think this is kind of in conjunction because what I'm probably hearing is not that we wash away back in Drupal, right? I'm not arguing that we should take away all the differences that we currently have in Drupal way. I'm really saying that we need to take that when the product that we have in Drupal and just think of one of a variety of different things that we provide to customers. Let's talk about this. I think there's a lot of discussion that we can have. Any other comments or questions? I'm going to say one more one. So how do you defend such, when that's planned, that's what that all happens, is when it's planned content, I argue that we need it early other way and my lots of contents or contents to be able to have a centralized core. So imagine the way that language is done. There's a core such that actually there's all shared artists with different languages. That's sort of appropriate but there's an intersection of content so that you can have long-form content which is planned and short-form content and have the same core part of it. So what does that do for the small, one of the newspaper that only has five years of that? Yeah, but they don't, they do long-form content. They don't do short content. They don't do flash parts. They're not ever going to move to a system where they're doing AR. That's so interesting. Just to repeat the point, sorry. I think most of it's written in one language, not in five. We can deal with five and deal with 20. But most languages, most of it's like get written in one language. I don't believe that actually. I don't think that's the same word. But you know, so let me just repeat the point because it's not right. The point was that, you know, people write, people should be able to write content for a variety of contexts, right? And have context with the content. And my argument in response to that was, well, what does that do for the small newspaper who only has five years of that? I can't manage 15 different, you know, contexts. I think that's a very important point. No one can possibly employ 50 different editors to write content for mobile, to write content for web, to write content for whatever else exists, voice assistant, whatever else. That's just not a possibility. And we see this with the state of Georgia. The state of Georgia told us, they said, we don't have a team that can manage more than one single piece of content at a time. So we need you to keep it unified. And I'd be curious actually, you know, how many people have had that experience with a client who said, you know, we're not gonna be able to do more than just one single piece of content at a time because we have a small team. Okay, a few people here and there. So yeah, you know, I agree. The second point we just raised was the fact that there's something that we only have written that's, you know, only one language is the right one, for instance. So I'd be curious to know if you're sure what you mean now. In one language, and you have to get it to have multiple languages for a website, but people, that's actually a fantastic thing. Oh, I see, you mean human languages, not programming languages. Oh, okay, I understand, I understand now, sorry. Okay, yes, okay, now I understand what you're saying, not programming languages. Yes, absolutely, I agree. But the points I need here have absolutely no bearing on the language. If you want to do multi-lingual, you can totally do that. And that should still be something that the Asian guys need to do. Now I'm using multi-lingual as a metaphor for what is both contextual and non-contextual. But if you have a, if you did multi-lingual in a non-contextual, what's on the way, which you'd have, what you'd have to do is have a translator ready between the two, an automatic translator. But what we do with multi-lingual is we have more than one, you know, we have English and Chinese. Right. And there's no real crossover between the two. I mean, there's crossover in terms of structure, but there's not crossover in terms of the actual language. And I think that, I think that this sort of thing with the non-contextual stuff, what you're trying to do is try to bring everything to one context, which destroys the, which destroys the, I don't know, the readability that the, the, I think its interest is of, of each. So just to be clear, I'm not arguing that every single piece of content should be in one language. That's definitely not what I'm arguing for. I'm arguing for, yes, but, but channels are different from languages. We can't have, we can't have any comparison between human languages and context in terms of channels.  Talking about removing the context, again, you don't explain the cost of that. It's just incredible that the, the focus, if you talk about a small newspaper with five content editors, well, they need to focus on the bits of the channel that are important for them, and then deliver them in the same way as if their market was in Chinese, it'll be right in Chinese, if the market is in English. You have one specific case of the Georgia State Council people, and they have, I would suggest a, an unusual case where they wanted to deliver a lecture, for example, as well as a lecture. But it comes with some incredible cost. Okay, so to repeat the point, the argument was that, you know, if you decontextualize content, and, you know, don't, and allow for a single piece of content to govern, and that content could be multi-lingual, just to clarify. But that single piece of content to govern across all channels, that comes at a huge cost. And I do agree, that's one of the things I stated up there was that there are weaknesses to that approach. But the issue is that as we work with larger and larger organizations that have more and more channels that they have to deliver to, that becomes a huge concern. Who's gonna manage all of that content? You can't have thousands of people managing 50 different, you know, ideas of content. We do have this already multi-lingual. I think that's absolutely something that's just the same place. I don't think there is any sort of issue with having, let's say, English, AR overlay versus Spanish AR overlay in the same exact concept of content. And I do agree that there are definitely people who are not as far along this journey who still need to, you know, have channels because of the content. And that's one of the things I raised there, which is that it does come at a huge cost in terms of complexity. And it's a trade-off between complexity and maintenance, I think, is what it comes down to. Yes, can you get a mic for us? We're running out of time. Yeah, last one. Off on one. Is the argument of who is Drupal 4? Is Drupal 4 the smaller sites where, you know, I started as a hobbyist. I started my own Drupal site, or is it for the larger organizations, the ambitious sites? And for most people, I would assume like probably 80% of the websites aren't going to do single-channel publishing. You know, that's what Drupal does, that's what Drupal does really well. And I think, I don't know, maybe I don't have a question here, but I think the trick is just predicting the future. You know, and I think Drupal is predicting that everything is going to go multi-channel, at least for the market that Drupal wants to be. You agree with that, or do you have any thoughts? Well, I think what we're seeing right now is an extreme proliferation in channels that are not necessarily non-webbing, right? So if you consider the fact that many of us today in this room are working with Gatsby, and are working with Vue, and are working with Weat, those are different channels. If you think about them from the perspective of how Drupal communicates with them, they are fundamentally different channels. And so right now we already see that complexity emerging. And I think for those of us who have simple websites that are just Gatsby, that is still a big consideration for us as well. How do we eventually get to the point where if we build that kind of an implementation for one of our clients, that they don't come back to us in six months and say, well, you just got to work on my features, now you need to refund me all my money. That's a big concern I think as well. Anyways, I know we're out of time. This is a very spirit discussion. I really appreciate all of the comments. I think that was very, very good. I'd love to talk with everybody afterwards. I'll be right outside. Thank you.


So Irina you have an amazing healing testimony if you want to share with a church and with those who are watching online What has had what happened to you? I? was limping for a while, and I didn't really think much of it, and I I was going to a wedding and I stepped out of the car and my knees started to break and Like to crack and then I got rushed into the emergency room And they found a tumor and they didn't really know what it was And then I got transferred to a different hospital, and they said that I had osteosarcoma, which is bone cancer Wow Wow, that's that's a little to digest in there Irina, how old were you when you found out when this happened? I was 17 years old very very young She was just a sophomore Submarine high school Just a limp on her leg. She did not imagine this Nobody could have imagined, you know, you are just going through high school Just going through it and then all of a sudden you have cancer. How did that affect your spiritual love your family? How did that affect you? I Was I was a Christian my whole life, but I didn't really follow like I didn't really follow God I knew who he was, but it wasn't really living for him So when I heard that I got cancer, I kind of just pushed God away I didn't really want to do anything with God and that made my process a little bit harder because I So you push God away That was your first reaction Many many of us when we go through hard process We think God like even though that we know about God We just push him. We think this is not fair. What is this happening to me? Why why are you allowing this into my life? Irina you also But it didn't stay there. So because she's here now. So something happened Irina what happened?  What happened? I Had a surgery and they didn't know if they were gonna cut off my leg Or they're gonna keep it and I had a dream that night that they were gonna cut off my leg And I just started crying and crying out to God and saying God I really want to live and I really want my leg and that I just started praying and I just kept Adding truth into my mind and just ignoring that That is amazing. Come on guys. Let's give it a cup to Jesus He she was remembering the truth even though that she started she claim on to God I mean she has two legs right now. So praise to God Praise to God Irina after that You told me you have 12 rounds of chemo Five surgeries. I mean she's whole and completing Jesus name But there is something that when we were talking that you told me as well that you had some bitterness some something in your heart What how was that affecting your life and how when you kind of like accepted Jesus back? How did help you through your process? I had a lot of unforgiveness towards my dad And when I was going through the process, it was really hard to just Being diagnosed with cancer and also having that unforgiveness. So I Started to cry out one night and just surrendering to God and surrendering like and just forgiving my dad at that time And I just felt so much peace and it just started living my life Hallelujah, hallelujah praise Jesus peace and Faithfulness to God God is a God who doesn't only wants to heal us physically, but he wants to make us whole He wants to just completely we're trying same as God. We are a spirit soul and body She would she got she got healed big as she got healed through chemo and she go through hill through surgeries But as well she got healing through the power of Christ. She got inner healing She forgave her dad and when she left that hospital She was not only healed physically, but she was also healed emotionally Right because what is the point if we're healed physically, but then there's still bitterness in our heart God wants to do so much more than just physically heal us He wants to heal us completely fully and totally because that's what we belong to him in Jesus name Come on guys. Let's give it up to God. Come on guys. He deserves better than this Irina what will be something that you can tell Family members a person who's going through life right now You know people who may be watching us in a hospital bed Family members who have children who are going through this. What can you a word of advice a word of encouragement? What can you tell them? So when you surrender to God, you will find your freedom That whatever like you're going through just give it to God because he knows what he's gonna do Amen. Amen. Thank you so much. Irina for sharing. Hallelujah. When you surrender to God, you find your freedom You surrender and you find your freedom you find your healing you find everything all glory to God


Adopted in 1948, the Universal Declaration of Human Rights establishes the equal dignity and worth of every person. Its principles are as relevant now as they were then. We have the right to speak up, to participate in decision-making, to an education and a decent life. Our shared humanity is rooted in these values. Societies which uphold human rights are fairer, more prosperous and more peaceful. Over the past 70 years, the Declaration has helped countless people gain greater freedom and equality. The dignity of millions has been uplifted and untold human suffering prevented. But its promise is yet to be fully realized. Today many of us are fearful about the way the world is heading. Human values are under attack, inequality, poverty, racism, conflicts, climate change. We must draw a line and stand up for our rights and those of others, wherever we are, at school, at work or on social media. We can all make a difference. Every day, everywhere, stand up for human rights and our shared humanity.


Welcome to part 2 of STM32 Trust video series about TFM. This video will cover the steps to get you started with the package. First, we are going to show how to download the package and then describe its content in detail. Let's review what are the download options. As mentioned in the overview, the TFM reference code is available as of today as one of the applications included in STM32Cube package for STM32L5. STM32Cube is a set of tools and embedded software bricks to enable fast and easy development with the STM32 microcontroller of your choice. This video will show the steps to download the STM32Cube L5 as a reference, but the same principle will apply to other STM32 microcontrollers once TFM supported will be extended. There are two options for downloading STM32Cube L5. The first one is to download it from st.com. You can search for STM32Cube L5 in the search bar. Clicking on the link, you will be redirected to this landing page, where you can find an overview of the package and a list of features that it includes. From this page, you can also reach the relevant user manual and application note from the documentation tab. You will find a list of documents, including the ones we mentioned in the overview video. As mentioned before, we would recommend you to have all this material handy during your developments. From here, we can go back to the overview page and scroll down to the bottom of the page. You will see the get software section, where you can check what is the latest version of the package, in this case version 1.4.0. Clicking on get software, you will be prompted with the package license agreement. After reviewing it, you can click on accept. At this stage, you can either fill the form with your information and click on the download button, or you can click on the login register to create a MISD account or to login to your existing one. If you don't have an account already, you can click on this link, fill the form and register. While if you already have one, you can simply put your email address and password and click on login. The download of the package will begin. Another recently introduced option for downloading STM32Cube package is to get it from STMichroelectronic's account on GitHub. Going back to the STM32Cube landing page, you can click on the get from GitHub link. This will open the corresponding GitHub page that includes an overview of the package and of its content. You can check out the code, as you would do with any other GitHub Git project. Let's now review the content of the package we just downloaded. STM32Cube L5 includes all the building blocks to get you started with your developments for STM32L5, drivers, midwars and example applications. Let's now open the release notes HTML for more details. In this HTML, you can find the description of the content and of its building blocks on the left. While on the right, you can find some other useful information, such as the revision history and what are the latest changes of each of the components of the system, like drivers, midwars and utilities. You will also find the known limitations for this revision, together with the list of the supported tools and compilers and the hardware development kits. Finally, you will also see a list of the dependencies. Another very useful reference included in every cube package is the project list HTML, included in the projects folder. This file contains a list of all the examples included in this revision. In the STM32Cube package, examples are classified in different categories. Examples, examples on a level, example mix, applications and demonstrations. For each one, you can find a short description, together with the indication of which ST hardware development kit that example is provided for. In this case, we have examples for the STM32L562 discovery kit, the L5 evaluation board and the Nucleo L552. Please note that these only reflects the porting included in this package. Each example could be tailored to any other supported device and development board. Let's search for the TFM application description. You will find the TFM application example that, as reported in the description, consists in the secure boot and secure female update application and the user application with TFM secure services at runtime. This configuration runs on the STM32L562 discovery kit and is the one we will use as a reference for this video. The package includes also another SBSFU application that runs on the Nucleo L552. This example provides a similar secure boot and secure female update reference code, but it does not include a TFM services implementation. Now, before diving into the application code, let's refresh what are the middleware components used by the application and see where we can find it. As mentioned in the overview video, the TFM reference application is based on three third-party middlewares, MCO boot, TFM and the Embed Crypto Library. The source code can be found opening the middlewares and third-party folder. In here, you will see the MCO boot folder that includes the open source implementation of the secure boot loader. You can refer to the included readme file for more information. The TFM folder that includes the software components of the TFM framework and implementation of the secure services at runtime. Also in this case, you can refer to the included readme file for more information. And finally, the Embed Crypto Library, a reference implementation for PSA cryptographic operations that is used by both the MCO boot and the TFM middlewares. Also in this case, you can refer to the STA readme included in the folder for further information. Let's see now where to find the TFM project implementation. We can click on projects, discover a kit, applications and we will find the TFM folder. As with any other STM32Q application project, you can refer to the readme.txt file for detailed information on the content, on how to prepare the setup and how to use the example. In the next video, we are going to go through a step-by-step compilation and execution of the whole project, following the instructions included in this document. But let's start now with an overview of each folder. The folder you will find here are the TFM SVSFU boot folder that includes the source code for the secure boot and secure firmware application, the TFM application folder that includes the TFM secure and non-secure application source code, the linker folder that includes the memory mapping shared between the TFM SVSFU boot and the TFM application projects, and the TFM loader that includes the Y-modem loader application example. The structure of the folders is similar for each project. Let's open for example the TFM application folder. You will see a dedicated readme.txt file that you can refer to for additional information, together with the folders including the projects for the supported toolchains, IAR, STM32Q by D and Kyle. Okay, this concludes this second video. Now that we have a better understanding of the content of the package and on where to find additional information, we can proceed with the step-by-step compilation and execution of the example. This will be covered in part 3. Thanks a lot for your attention. Don't forget to visit the STM32 trust landing page at st.com slash stm32trust. I look forward to seeing you in the next video of the series.


What's going on guys it's your boy DPJ here today with another Destiny video and in today's Destiny video we're going to check out what the brings to the tower on the 18th of September the first time he has come around since the Taken King has dropped he's located in the tower this week when you spawn in you just want a head left and you'll see him by these big black doors let's just see why he has this week okay interesting no weapon but still we do see there a new exotic piece of armor with now we're going to start with the legacy engram now this decoys into year one exotic so if you're missing a year one exotic you can buy this for 31 strange coins for the Titan we have an insurmountable school for this offers 280 defense with 78 strength mods are gain an additional melee charge gain bonus super energy from melee kills and minions of the darkness and gain bonus melee energy and orb pickups for the hunter we have young arm cover spine these are gauntlets offering 280 defense with 45 discipline and 45 strength mods are increased trip my grenade duration gain an additional trip my grenade charge increased reload speed with hand cannons and increased grenade throw distances costing 13 strange coins same as the Titan army and for the warlock we have a new Taken King exotic gauntlets the impossible machines these are through 280 defense with 63 strength mods are grants landfall increased melee attack speed and increased reload speed with Porsche rifles don't think we can check these out could be because I'm a my hunter no I didn't think so but they do look absolutely badass and then also costing 13 strange coins and then we have an exotic helmet engram you'll buy this for 19 strange coins take it to the crypto can hopefully get something you need out of it okay we can see a new consumable here called the three of coins as you can see it states stackable effect that increases the chances the next ultra you defeat will drop an exotic engram I'm about to waste all my strange coins on these motherfuckers and then go and grind bosses I really am but guys that's what Zers brought on the 18th of September not bad whatsoever great for you guys who are warlocks then again to be honest these all offer great defense so if you are struggling to get your light level up buy one of these bad boys and do what you gotta do guys hope you enjoyed the video do drop a like I do appreciate the support subscribe for daily destiny and I'll catch you in the next one peace out until next time post