72 lines
3.6 KiB
YAML
72 lines
3.6 KiB
YAML
uuid:
|
|
- value: 13312da0-7cf4-4825-ac6e-eb35c673e63e
|
|
langcode:
|
|
- value: en
|
|
type:
|
|
- target_id: daily_email
|
|
target_type: node_type
|
|
target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
|
|
revision_timestamp:
|
|
- value: '2025-05-11T09:00:18+00:00'
|
|
revision_uid:
|
|
- target_type: user
|
|
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
|
|
revision_log: { }
|
|
status:
|
|
- value: true
|
|
uid:
|
|
- target_type: user
|
|
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
|
|
title:
|
|
- value: 'Experimenting with web components'
|
|
created:
|
|
- value: '2024-02-29T00:00:00+00:00'
|
|
changed:
|
|
- value: '2025-05-11T09:00:18+00:00'
|
|
promote:
|
|
- value: false
|
|
sticky:
|
|
- value: false
|
|
default_langcode:
|
|
- value: true
|
|
revision_translation_affected:
|
|
- value: true
|
|
path:
|
|
- alias: /daily/2024/02/29/experimenting-with-web-components
|
|
langcode: en
|
|
body:
|
|
- value: |
|
|
<p>After my Beyond Blocks episode with Mark Conroy, I've spent some time this week experimenting with web components.</p>
|
|
|
|
<p>The team and I are building a new design system in Fractal and, as Drupal is our main application, we're using Twig as our templating language within Fractal so the changes are easier to port between systems.</p>
|
|
|
|
<p>Web components are agnostic, so they work within different languages and frameworks.</p>
|
|
|
|
<p>We also use other technologies, such as Vue.js, and third-party suppliers, so having an agnostic web component would reduce the time and effort needed to implement the design system across different technologies and applications.</p>
|
|
|
|
<p>If we can make self-contained web components that include their own styling and behaviour, that also improves re-usability and reduces the maintenance overhead as there would be one canonical version for everyone to use - not just a reference implementation everyone would need to recreate.</p>
|
|
|
|
<p>After this spike, I'm intrigued to see how we could use web components and what potential issues we can solve with them whilst reducing our implementation and maintenance efforts.</p>
|
|
|
|
<p>Are you interested in web components, too? <a href="/podcast/11-mark-conroy">Listen to the podcast episode with Mark Conroy</a>.</p>
|
|
|
|
|
|
format: full_html
|
|
processed: |
|
|
<p>After my Beyond Blocks episode with Mark Conroy, I've spent some time this week experimenting with web components.</p>
|
|
|
|
<p>The team and I are building a new design system in Fractal and, as Drupal is our main application, we're using Twig as our templating language within Fractal so the changes are easier to port between systems.</p>
|
|
|
|
<p>Web components are agnostic, so they work within different languages and frameworks.</p>
|
|
|
|
<p>We also use other technologies, such as Vue.js, and third-party suppliers, so having an agnostic web component would reduce the time and effort needed to implement the design system across different technologies and applications.</p>
|
|
|
|
<p>If we can make self-contained web components that include their own styling and behaviour, that also improves re-usability and reduces the maintenance overhead as there would be one canonical version for everyone to use - not just a reference implementation everyone would need to recreate.</p>
|
|
|
|
<p>After this spike, I'm intrigued to see how we could use web components and what potential issues we can solve with them whilst reducing our implementation and maintenance efforts.</p>
|
|
|
|
<p>Are you interested in web components, too? <a href="/podcast/11-mark-conroy">Listen to the podcast episode with Mark Conroy</a>.</p>
|
|
|
|
|
|
summary: null
|
|
field_daily_email_cta: { }
|