92 lines
3.5 KiB
YAML
92 lines
3.5 KiB
YAML
uuid:
|
|
- value: c0d7b8ea-8a29-4d83-937d-52d951ce250b
|
|
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:02+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: 'Make it work, then make it good'
|
|
created:
|
|
- value: '2025-01-29T00:00:00+00:00'
|
|
changed:
|
|
- value: '2025-05-11T09:00:02+00:00'
|
|
promote:
|
|
- value: false
|
|
sticky:
|
|
- value: false
|
|
default_langcode:
|
|
- value: true
|
|
revision_translation_affected:
|
|
- value: true
|
|
path:
|
|
- alias: /daily/2025/01/29/make-it-work
|
|
langcode: en
|
|
body:
|
|
- value: |
|
|
<p>I've recently been writing a new custom module for a Drupal application.</p>
|
|
|
|
<p>I needed to create a form populated with options from an API endpoint, submitted the form values to another API endpoint and display some results to the user.</p>
|
|
|
|
<p>I'd architected and planned the steps I was going to need and knew how I was going to approach adding this new functionality.</p>
|
|
|
|
<p>My first objective was to make it work.</p>
|
|
|
|
<p>To get all the functionality in place so it was working as soon as possible with minimal distractions.</p>
|
|
|
|
<p>This meant I would find any issues sooner rather than later and what I'd created could be reviewed and tested by stakeholders, regardless of how it looked.</p>
|
|
|
|
<p>If needed, it could have been released at this point.</p>
|
|
|
|
<p>It was working.</p>
|
|
|
|
<p>Next, I did a second pass to make it good.</p>
|
|
|
|
<p>I updated the markup and styled it to match the provided designs.</p>
|
|
|
|
<p>I made small updates to terminology and messaging to ensure the tone of voice was correct and consistent with the rest of the application and various other small tweaks and improvements.</p>
|
|
|
|
<p>I could do all this knowing the functionality was already working, and I could focus on making it good.</p>
|
|
|
|
|
|
format: full_html
|
|
processed: |
|
|
<p>I've recently been writing a new custom module for a Drupal application.</p>
|
|
|
|
<p>I needed to create a form populated with options from an API endpoint, submitted the form values to another API endpoint and display some results to the user.</p>
|
|
|
|
<p>I'd architected and planned the steps I was going to need and knew how I was going to approach adding this new functionality.</p>
|
|
|
|
<p>My first objective was to make it work.</p>
|
|
|
|
<p>To get all the functionality in place so it was working as soon as possible with minimal distractions.</p>
|
|
|
|
<p>This meant I would find any issues sooner rather than later and what I'd created could be reviewed and tested by stakeholders, regardless of how it looked.</p>
|
|
|
|
<p>If needed, it could have been released at this point.</p>
|
|
|
|
<p>It was working.</p>
|
|
|
|
<p>Next, I did a second pass to make it good.</p>
|
|
|
|
<p>I updated the markup and styled it to match the provided designs.</p>
|
|
|
|
<p>I made small updates to terminology and messaging to ensure the tone of voice was correct and consistent with the rest of the application and various other small tweaks and improvements.</p>
|
|
|
|
<p>I could do all this knowing the functionality was already working, and I could focus on making it good.</p>
|
|
|
|
|
|
summary: null
|
|
field_daily_email_cta: { }
|