95. AI-assisted website development
Module 19 · About 20 minutes · Lesson 94; review earlier concepts as needed
Open Interactive LessonDiscover
What changes when you use ai-assisted website development, and how can you prove it?
- Explain ai-assisted website development using the example source
- Predict the visual or structural effect of one controlled change
- Repair the supplied fault and verify actual output
Predict
Record the expected structure or visual change before rendering. Name one thing that should remain unchanged.
Understand
AI can help propose structure and styles, but its output must be checked. Define audience, requirements and acceptance tests, inspect semantics and selector behavior, and verify target-browser support. Never accept a claim of rendering as evidence. The prompt studio includes current source and actual diagnostics without sending data to a model. A correct simple implementation is preferable to unexplained complexity.
Important source lines
- index.html:1 <main><h1>Verified generated page</h1><button type="button">A real action control</button><p>Review every proposed change.</p></main>
- The document’s principal content, normally one visible instance. Attribute guidance: id useful for skip links.
- styles.css:1 button:focus-visible { outline:3px solid #234f9b; }
- This line groups or completes the surrounding structure. Inspect its actual parent/child relationship and compare with the lesson explanation.
The first example teaches this lesson’s primary contract. Additional examples are optional related references or applications, each with its own purpose and source; an example without an authored check requires the stated visual/manual review.
Example 1: AI-assisted website development
The reviewed implementation uses native control semantics instead of an incomplete custom role.
index.html
<main><h1>Verified generated page</h1><button type="button">A real action control</button><p>Review every proposed change.</p></main>
styles.css
button:focus-visible { outline:3px solid #234f9b; }script.js
Expected: The reviewed implementation uses native control semantics instead of an incomplete custom role.
Edit and Render This ExampleExample 2: Property: outline
Draws an outline without consuming normal box-model space.
index.html
<section class="stage"><article class="sample"><h2>Readable content</h2><p>Longer sample text demonstrates wrapping, spacing and typography. Change a value, inspect its computed style and compare the resulting box.</p><a href="#details">Read the details</a></article><article class="peer">A second item</article></section><section id="details"><h2>Details</h2></section>
styles.css
body { font:18px/1.5 system-ui; color:#17324d; margin:1rem; }
.stage { padding:1rem; border:1px dashed #9caec0; } .sample { padding:1rem; border:2px solid #849ab1; max-width:30rem; }
.sample { outline: 3px solid #a44322; }script.js
Expected: Inspect .sample in the block context. Draws an outline without consuming normal box-model space. The browser’s CSS.supports and computed-style report are the authority for this installed browser; a declaration can be valid but depend on additional layout or font conditions.
Edit and Render This ExampleExample 3: Pagination
Store the current page and derive its slice and boundary controls.
index.html
<section data-component aria-label="Pagination"> <ol id="rows"></ol><button id="prev">Previous page</button><button id="next">Next page</button><p id="page" role="status"></p> </section>
styles.css
* { box-sizing: border-box; }
body { margin: 0; color: #142537; background: #eef4fa; font: 16px/1.5 system-ui, sans-serif; }
[data-component] { max-width: 44rem; margin: 1rem auto; padding: 1rem; border: 1px solid #a1b2c4; border-radius: .75rem; background: white; }
button, input, select, textarea { font: inherit; padding: .4rem .65rem; margin: .2rem; }
button { cursor: pointer; } :focus-visible { outline: 3px solid #a33e0c; outline-offset: 3px; }
label { display: block; } [hidden] { display: none !important; }
table { border-collapse: collapse; } th, td { padding: .4rem; border-bottom: 1px solid #a1b2c4; }
script.js
const root=document.querySelector("[data-component]");
const data=['One','Two','Three','Four'];let page=0;const prev=root.querySelector('#prev'),next=root.querySelector('#next');function draw(){root.querySelector('#rows').replaceChildren(...data.slice(page*2,page*2+2).map(name=>Object.assign(document.createElement('li'),{textContent:name})));prev.disabled=page===0;next.disabled=page===1;root.querySelector('#page').textContent='Page '+(page+1)+' of 2';}prev.onclick=()=>{page--;draw();};next.onclick=()=>{page++;draw();};draw();Expected: Update the number of pages when records are filtered.
Edit and Render This ExampleExample 4: Property: padding
Creates internal space between content and border.
index.html
<section class="stage"><article class="sample"><h2>Readable content</h2><p>Longer sample text demonstrates wrapping, spacing and typography. Change a value, inspect its computed style and compare the resulting box.</p><a href="#details">Read the details</a></article><article class="peer">A second item</article></section><section id="details"><h2>Details</h2></section>
styles.css
body { font:18px/1.5 system-ui; color:#17324d; margin:1rem; }
.stage { padding:1rem; border:1px dashed #9caec0; } .sample { padding:1rem; border:2px solid #849ab1; max-width:30rem; }
.sample { padding: 24px; }script.js
Expected: Inspect .sample in the block context. Creates internal space between content and border. The browser’s CSS.supports and computed-style report are the authority for this installed browser; a declaration can be valid but depend on additional layout or font conditions.
Edit and Render This ExampleExample 5: Element: main
The document’s principal content, normally one visible instance.
index.html
<main><h1>Principal content</h1><p>The central task belongs here.</p></main>
styles.css
body { font:18px/1.6 system-ui; margin:1.5rem; color:#17324d; } img,video,svg { max-width:100%; height:auto; } th,td { padding:.5rem; border:1px solid #a8b8c8; } :focus-visible { outline:3px solid #a44322; outline-offset:3px; }script.js
Expected: The document’s principal content, normally one visible instance. Review its real DOM and native behavior; structural/media-only examples are labeled.
Edit and Render This ExampleBuild and test
The reviewed implementation uses native control semantics instead of an incomplete custom role. Repair the current exercise without removing necessary content. Checks inspect the stated structural/computed/stylesheet contract, not exact source text.
Starter index.html
<main><h1>Verified generated page</h1><div role="button">A real action control</div><p>Review every proposed change.</p></main>
Starter styles.css
button:focus-visible { outline:3px solid #234f9b; }Objective contract
[
{
"type": "count",
"selector": "button[type=\"button\"]",
"value": 1,
"label": "Include 1 matching button[type=\"button\"] element(s)"
}
]Hint 1
Locate the first difference between the intended result and the real preview. Inspect matching elements and computed styles.
Hint 2
The relevant source uses <button type="button">A real action control</button>. The exercise instead uses <div role="button">A real action control</div>. Identify its effect before changing it.
Hint 3
Restore the intended <button type="button">A real action control</button> operation or implement an equivalent structure/style. Run the actual checks and explain why it works.
Complete reference solution
index.html
<main><h1>Verified generated page</h1><button type="button">A real action control</button><p>Review every proposed change.</p></main>
styles.css
button:focus-visible { outline:3px solid #234f9b; }Explain, reflect and extend
Which part of the actual preview or inspector proves this result? Explain one boundary case and name what automated checks do not verify.
Apply this concept to a different realistic piece of content. Predict its structure or visual behavior, test narrow and wide widths where relevant, then record one invalid case and its repair.
Troubleshooting and professional practice
If nothing changes, confirm that you edited the active file and ran Run Preview, or enabled Auto Preview. Inspect the actual DOM because the browser may repair invalid nesting. For CSS, check selector matches, valid declarations, active queries and computed values. Preserve local asset paths and inspect warnings. The reviewed implementation uses native control semantics instead of an incomplete custom role.
Knowledge check
Explain why the stated result follows from the source. Predict a second input or width and test it independently. Automated contracts and written explanations are reviewed separately.
Optional AI prompts
- Explain this lesson’s source line by line using the actual objective above.
- Help implement one small extension and define normal, boundary and failure tests.
- Review/debug the source against actual preview observations; verify standards and never claim rendering without evidence.