{"id":3405,"date":"2026-11-19T12:31:27","date_gmt":"2026-11-19T10:31:27","guid":{"rendered":"https:\/\/www.kaarne.fi\/superstore\/?p=3405"},"modified":"2026-11-19T12:31:31","modified_gmt":"2026-11-19T10:31:31","slug":"let-learners-compare-a-filled-field-with-a-missing-one","status":"publish","type":"post","link":"https:\/\/www.kaarne.fi\/superstore\/articles\/let-learners-compare-a-filled-field-with-a-missing-one\/","title":{"rendered":"Let Learners Compare a Filled Field with a Missing One"},"content":{"rendered":"<p>A venue label appears on one event card and is absent from another. The lesson becomes useful when learners can explain the difference between the saved value, the template&#8217;s rule and the visible result. Simply showing one complete and one broken-looking page blurs those questions.<\/p>\n<h2>Choose one optional value<\/h2>\n<p>Use a fictional workshop site with a short optional room label. Prepare two practice entries with the same title, image, description and other relevant content. Give them distinct identifiers so learners can locate them, but keep those identifiers out of the rendered comparison when possible. Fill the room label in one and leave it absent in the other.<\/p>\n<p>Check the installed field provider and template before teaching. The exercise concerns a permitted absent value, not a failed validation rule. If the actual field is required, choose a genuinely optional example or revise the lesson design rather than describing an invalid record as a supported state.<\/p>\n<h2>Agree the display rule before the comparison<\/h2>\n<p>Write the expected treatment for this exercise: a filled label appears in the agreed place; when absent, the template omits both the label and any separator that belongs to it. This is a proposed design contract for the example, not a universal default supplied by WordPress or a field plugin.<\/p>\n<p>The <a href=\"https:\/\/www.advancedcustomfields.com\/resources\/text\/\" target=\"_blank\" rel=\"noopener\">official ACF Text documentation<\/a>, for example, distinguishes a required setting, a default value and editor placeholder text. Those controls should not be treated as interchangeable proof of what a template renders. Verify the actual stored value and display logic of your chosen setup.<\/p>\n<h2>Give learners a prediction sheet<\/h2>\n<p>Before opening both rendered cards, ask for three short predictions. Which element should differ? Which parts should remain the same? What would an empty gap or lone separator suggest checking? Let learners make a prediction without requiring them to know the implementation code.<\/p>\n<p>Then reveal the cards through the agreed preview route. Ask learners to describe what they can actually see. Record expected and observed treatment separately. A difference may be intentional; an unexpected result may concern the prepared data, the rendering rule or the view being inspected.<\/p>\n<h2>Connect the observation back to the entries<\/h2>\n<p>Have learners locate the source entry for each card and inspect the relevant field. Ask them to point to the correspondence: this saved value supports this visible label; this entry has no value, so the agreed omission rule applies. Do not let a plausible-looking editor hint stand in for a saved field value.<\/p>\n<p>If the cards differ in additional ways, pause the teaching comparison. A different image or unrelated title length may distract from the one condition being studied. Repair the prepared pair through the normal training process and explain why controlling that difference matters. The exercise should invite reasoning rather than guessing which visual change the trainer intended.<\/p>\n<h2>Ask for an explanation before another edit<\/h2>\n<p>Use questions that reveal the learner&#8217;s model:<\/p>\n<ul>\n<li>Which difference came from the content and which depended on a template rule?<\/li>\n<li>Would making the field required answer the same design question?<\/li>\n<li>What evidence would you inspect if the empty card still displayed a separator?<\/li>\n<li>What would you expect if a value were added to the second entry?<\/li>\n<\/ul>\n<p>Allow the learner to add the agreed value in their assigned practice record and compare the result with that last prediction. Use the supported saving route and avoid altering another learner&#8217;s controlled example. The purpose is to explain a condition, not to maximise the number of edits.<\/p>\n<h2>Finish with a bounded conclusion<\/h2>\n<p>A useful learner explanation might distinguish the saved label, its optional status and the chosen omission behaviour. It should not become \u201call missing fields disappear automatically.\u201d Other field types and templates need their own documented treatment.<\/p>\n<p>Keep the two initial states, intended rule and reset note with the lesson. If the template changes, rehearse the comparison again before using it with another class. A once-useful screenshot cannot establish the behaviour of a different configuration.<\/p>\n<p>Keep the two examples alike except for the field being studied. A prepared demo set can make that difference easier to examine during a live lesson.<\/p>\n<p>Build the prior connection with <a href=\"https:\/\/www.kaarne.fi\/superstore\/articles\/teach-dynamic-templates-with-one-field-and-one-visible-change\/\">one field and one visible change<\/a>. Prepare the paired entries with <a href=\"https:\/\/www.kaarne.fi\/superstore\/articles\/give-every-staging-content-batch-a-reason-to-exist\/\">a recorded purpose for the content batch<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>One filled label and one permitted absent value can reveal whether learners understand content, validation and the chosen rendering rule.<\/p>\n","protected":false},"author":1,"featured_media":3441,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_hide_featured_image":false,"_jetpack_featured_image_duplicate_dismissed":0,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[35],"tags":[],"class_list":["post-3405","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ai-digital-tools"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"https:\/\/www.kaarne.fi\/superstore\/wp-content\/uploads\/sites\/7\/2026\/11\/sf-08-02.webp","_links":{"self":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3405","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/comments?post=3405"}],"version-history":[{"count":7,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3405\/revisions"}],"predecessor-version":[{"id":3543,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/posts\/3405\/revisions\/3543"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/media\/3441"}],"wp:attachment":[{"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/media?parent=3405"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/categories?post=3405"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaarne.fi\/superstore\/wp-json\/wp\/v2\/tags?post=3405"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}