Understand development and code
Development turns intent into behaviour. Separate document structure, browser interactions and server decisions. Define accepted inputs and output states before assessing a library or framework.
101 concepts to explore with their definitions and practical advice.
Search the full glossary
A reading path
1. Structure and presentation
HTML describes elements; CSS organises presentation. Use components suited to the action before adding custom behaviour.
2. Exchanges and contracts
An API describes expected exchanges. An endpoint, its inputs and responses should remain compatible with the journey using it.
3. Errors and change
Test empty states, interruptions and unexpected input on a copy. Keep versions and checks needed for an update.
Useful distinctions
Front-end / Back-end
Front-end covers the interface executed or rendered for the browser; back-end handles server processing. A visible interface check does not replace server validation.
API / Webhook
An API provides an exchange contract; a webhook sends a notification when an expected event occurs. The receiving system should account for repetition or delay.
Use the vocabulary to make a decision
Situation
A submission displays success but no record is retained.
Before deciding
Follow request and response, then the actual saved state. Separate the interface message from server confirmation.
A concrete check
Reproduce on a copy with test data and compare expected and observed results.
All concepts in this topic
Links open the full definition on its alphabet page. Acronyms and synonyms remain searchable from the main glossary.
- 404 page
- Algorithm
- AMP
- API
- API contract
- Asynchronous
- AVIF
- Back-end
- Baseline
- Bidirectional isolation
- Bot
- Broken link
- CacheStorage
- Catalogue facet
- Client
- Conditional request
- Correlation identifier
- CSS
- Cursor pagination
- Dependency graph
- Deployment
- DOM
- Dynamic content
- Endpoint
- Event-driven architecture
- Feature flag
- Form validation
- Framework
- Front-end
- Git
- GraphQL
- Head
- HTML
- HTTP 410 status
- HTTP header
- i18n
- IDE
- Idempotence
- iframe
- Incremental loading
- IndexedDB
- ISR
- JAMstack
- Java
- JavaScript
- JavaScript rendering
- jQuery
- JSON
- JSON Schema
- Lazy loading
- localhost
- Localized link
- localStorage
- Long task
- Middleware
- No-code
- Node.js
- Open source
- OpenAPI
- Paginated page
- Payload
- PHP
- Plugin
- Preflight request
- Progressive enhancement
- Progressive Web App
- Python
- Query string
- Redirect chain
- Render-blocking resource
- Rendering
- Responsive image
- REST API
- Semantic HTML
- Server-side rendering
- Service worker
- Session
- sessionStorage
- sizes attribute
- Source code
- srcset
- Staging
- Static site
- Storage Access API
- Structured logging
- Third-party script
- URL parameter
- URL rewriting
- Version control
- Web application
- WebAssembly
- Webhook
- Webhook delivery identifier
- Webhook retry
- WebMCP
- WebSocket
- WordPress
- XHTML
- XML
- XPath
- YAML
Frequently asked questions
Is a complex application always needed?
Choose functionality according to need and maintainability. A simple page or form may suffice; complexity is useful only when it addresses a real constraint.
Is JavaScript validation sufficient?
It helps guide input, but data and permission rules should also be enforced server-side. Test an input submitted outside the normal interface.
Primary reference documents
These documents explain the technical concepts. The reading paths and decision examples are editorial methods to adapt to your project.