Video by via Dailymotion Source Subscribe Here: https://bit.ly/3dh3Yj1 Daura e Tarjuma e Quran – Host: Shuja Uddin Sheikh 1st Time In Electronic Media’s History Complete Translation & Tafseer Of Quran Kareem. #ShujaUddinSheikh #DauraeTarjumaeQuran #ARYQtv Official Facebook: https://www.facebook.com/ARYQTV/Official Website: https://aryqtv.tv/Watch ARY Qtv Live: http://live.aryqtv.tv/Programs Schedule: https://aryqtv.tv/schedule/Islamic Information: https://bit.ly/2MfIF4PAndroid App: https://bit.ly/33wgto4 Go to Source
-“나도 예전에는 패한 뒤 혼자 울어”
-“AI와의 승부, 답안지대로 두는 느낌”
2022 삼성화재배 월드바둑 마스터스에서 여자 프로기사 최초로 메이저 세계대회 준우승을 차지한 최정 9단.
최정 9단은 준결승(4강)에서 변상일 9단에게 169수 만에 흑 불계승을 거뒀는데, 대국 도중에 벌어진 한 장면이 화제가 됐습니다.
패색이 짙어진 변상일 9단이 안경을 벗고 눈물을 흘리더니, 급기야 자신의 뺨을 때리며 자책하는 돌발 행동을 한 겁니다.
변상일 9단은 대국이 끝난 후 최정 9단에게 사과했지만, 바둑 팬들 사이에서는 ‘변상일 9단이 예의 없는 행동을 했다’는 비판이 나왔습니다.
채널A ‘뉴스A’ 오픈 인터뷰에 출연한 최정 9단은 “그 일은 잘 해결이 됐다”면서 변상일 9단을 이해한다는 반응을 보였습니다.
최정 9단은 “시합을 할 때마다 계속 시험을 치르는 기분이 든다”면서 “특히 이기고 싶었던 바둑일 경우에는 졌을 때 느끼는 괴로움이 엄청 크다”고 말했습니다.
그러면서 “나도 예전에 이기고 싶었던 바둑을 지면 너무 괴로워서 혼자 엉엉 울기도 했다. 승부사라면 겪을 수밖에 없는 괴로움이다”라고 덧붙였습니다.
최정 9단은 바둑계의 화두인 인공지능(AI)에 대한 생각도 밝혔습니다.
2016년 열린 AI 알파고와 이세돌 9단의 대국은 바둑에도 AI 시대가 왔음을 상징적으로 보여주는 대결이었습니다.
현재 AI 바둑 프로그램은 프로기사의 훈련에 사용될 정도로 바둑계에 큰 영향을 끼치고 있습니다.
이런 가운데 최정 9단은 AI로 인해 바둑이 획일적으로 변한 느낌이 든다고 말했습니다.
최정 9단은 “AI가 들어오기 전에는 선수들마다 각자의 색깔이 드러나고 재미 있었는데, 지금은 답안지가 있는 바둑을 두는 느낌이다”라고 말했습니다.
일각에선 AI로 인해 점차 프로기사들의 설 자리가 좁아질 수도 있다는 우려를 내놓습니다.
하지만 최정 9단의 생각은 달랐습니다.
최정 9단은 “자동차가 나왔다고 해서 달리기라는 종목이 사라진 것은 아니다”라면서 인간 기사만이 둘 수 있는 바둑이 남아있을 것이라고 밝혔습니다.
In a previous article, we shared trends we’ve seen in the Acquia ecosystem and how they apply to our projects at Evolving Web. One of those trends is the growing importance of composable digital experience, central to how Drupal works. In this article, we will explore how composability, which started as a development concept, has now an expanding role in content management and content governance.
What is Composability?
Composability is at the very core of Drupal’s open source principles. Composable CMS is the idea that we should create robust building blocks that we can reuse across a single website, an ecosystem of websites, or every single Drupal project.
Composable CMS isn’t a single thing. It could actually lead us to different architectural choices. For example:
- A wheel and spoke model, if we have a content hub that dispatches content to a set of satellite websites
- Individual websites that don’t share content, but do share the same structure
- A model where content is generated on many individual websites, and then shared in a completely distributed way, without a central hub
- A multi-channel setup where content is shared from a CMS to completely separate channels like CRM, digital signage, a native app
Composability implies dividing content up into atoms so that it can more easily translate from one use case to another. For example, if we define an event as having a date field, we can add it to a calendar on our site, but also use schema.org metadata to indicate the event date on Google search results.
Why is Composability Useful?
Composability is a powerful concept because it gives us a content model that is predictable. From there, we can expect each content entity to have particular properties (a label or title, a language)
It helps us make good decisions about code and content reuse, challenging us to think about how configuring a single template, creating a piece of functionality, or authoring a piece of content, might be useful or reusable elsewhere.
With this type of granularity, content becomes searchable and findable when we apply the right markup and metadata that enables reusability.
It helps us create brand and messaging consistency as we should have fewer content elements to keep updated.
Composable Tactics in Drupal
By using a platform like Drupal, you’re already doing composability. You’re reusing the modules and base content structure of every other Drupal project, and benefiting from that. If you want to enable metatags for your content, you can turn on that feature and apply it to all your existing content.
If you’re using Layout Builder with custom block types, or the Paragraphs library to enable reuse of granular “Paragraph” elements, you’re already leveraging composable features for content reuse. You can learn more about how to use Paragraphs and Layout Builder via this article: How content editors use the drupal layout builder.
Features like Drupal’s core Media Library and the Entity Reference field provide content editors with the tools to reuse content within a single Drupal website or project..
You’re also taking advantage of composability when using Drupal’s Migrate API to leverage existing content and pull it into Drupal, or when using JSON:API or REST API to expose Drupal content to other platforms and channels.
Configuration management allows us to export the content model to code, making it potentially sharable to other websites in our ecosystem. The new recipes initiative seeks to make elements of Drupal configuration more portable, to encourage this type of reuse and create a more standardized method of component reuse in Drupal core.
Composability Beyond Drupal Core
Acquia’s Site studio complements Drupal and provides a mature product that teams can use to manage a library of reusable content, and also the templates (components) for storing granular content, and even the layouts and styling that applies to those components.
It provides a predefined/standardized approach to managing the layers of composability that we outlined above. The benefit of a solution like this is that it steers teams towards composability and gives them pre-built examples of how reuse plays out in a typical website.
It also has tools for sharing the library of content across websites in the same ecosystem, which saves architectural time in setting this up.
Site Studio is a great example of taking the potential of Drupal’s composability and laying it out in a way that’s ready for teams to take and run with. It also comes with opinions about how components and content should be managed, which might be too flexible or too restrictive for some teams. I highly recommend taking a deeper dive and checking out Acquia’s Site Studio demo.
Offering site owners and content editors the ability to re-use content and other building blocks comes with a few challenges.
Challenge 1: Understanding Context
If content is used in many contexts, it’s hard to communicate to content editors what the results of their changes will be. Imagine a typical preview feature, allowing you to preview how content appears on a single page. If you are editing an image to be reused in five different ways, it’s hard to anticipate the impact of cropping it in a certain way. From this comes the question of how to create meaningful previews.
Solution: Help content editors understand the meaning and parameters of their choices:
- Provide some instructions on image selection that takes into account how the image will be used. And
- Provide context about metadata if that metadata is visible when content is displayed on social media, but not when content is displayed on a simple page on the website.
Challenge 2: Accessibility
Multiple contexts also makes accessibility a challenge. Accessibility guidelines encourage teams to create meaningful content structures and flows. When editing a single content component that appears in different pages, think about how it will affect the flow and the hierarchy
- Create a robust content model that enforces an accessible content structure. This means planning out which components can be used where so that they follow a logical hierarchy (e.g. a heading structure that doesn’t skip a level).
- Educate content editors so that each component is accessible regardless of context (e.g. writing link text that is self-explanatory regardless of context).
Challenge 3: Proliferation of Choices
The sheer quantity of content can also proliferate in the world of composable CMS. While the idea is to reuse components, it often also means sharing of components and adding more options to some websites that might have had a simpler content model in the past. The proliferation of content elements and templates means more choice for content editors, and can lead to more confusion about the use case.
- Provide clear examples of not just how to create content, but why to use one type of component vs. another.
- Give content editors the tools they need to find existing content, as well as some context around how it’s already being used.
Challenge 4: Approval Workflows
If content can be reused across different websites within an ecosystem, it likely changes the approval workflow whenever content needs updating. Let’s say you have authored a page, got it approved and published it. In a composable context, some components of your page might have to be approved separately, making it harder for you to update one aspect of the page that is being re-used in other places.
- Create a clear content governance plan that defines what belongs in a content library and how that content gets approved and updated.
- Invest time in constantly curating and maintaining the library of reusable content rather than taking a “set it and forget it” approach.
Drupal and the Composable Enterprise
In our experience at Evolving Web, governance around modularity and composability is and will remain the biggest challenge. But despite all the challenges listed above, composability is an approach that gives institutions a competitive advantage as they can innovate and adapt to changing business needs rapidly.
When we get to the point when site builders and content creators can have visibility as to what content components are out there and how they’re being used, as well as establishing best practices for making this type of content widely available, we’ll be able to fully take advantage of this approach.
Read more about Content Governance: Why Web Governance Is Essential to Your Digital Content Strategy