A six-digit hexadecimal web color commonly has the form:
#RRGGBB
The three pairs represent:
Each pair ranges from:
00
through:
FF
Examples:
#FF0000
strong red
#00FF00
strong green
#0000FF
strong blue
The hexadecimal representation is a compact way to express digital color values.
HTML identifies the structure and meaning of page content.
Examples include:
<h1>Page Title</h1>
<p>A paragraph of information.</p>
HTML can represent:
A basic page separates document information in the head from visible page content in the body.
CSS controls visual presentation such as:
A simple rule is:
h1 {
color: #3366CC;
}
The selector identifies what is being styled.
The declaration supplies a property and value.
HTML and CSS have different jobs:
HTML: structure and meaning.
CSS: presentation.
The Internet is the connected network infrastructure.
The Web is a system of resources and communication that uses that network.
A browser uses Internet connectivity to participate in Web request/response interactions.
Not every Internet-based communication is a webpage.
In a simple web interaction:
browser/client
↓ request
server
↓ response
browser/client
The browser:
The server:
A simplified flow is:
User enters URL
↓
Browser interprets URL
↓
Browser sends request
↓
Server processes request
↓
Server sends response
↓
Browser interprets response
↓
Browser displays page
A visible page may require several additional requests for CSS, images, or other resources.
The client sends the request.
The server sends the response.
A response can include:
A successful response can include HTML that the browser renders.
A UML activity diagram can use partitions or swimlanes to show who performs each action.
For a web interaction, useful lanes are:
Browser / Client
Server
The request crosses from the Browser lane to the Server lane.
The response crosses back.
Partitions add responsibility information to the normal activity-diagram flow.
A conceptual partitioned flow is:
BROWSER SERVER
Create request
--------------------> Receive request
Process request
Create response
Receive response <--------- Send response
Interpret response
Display result
The diagram should communicate both:
Consider:
https://example.com/teams/wildcats
The main introductory parts are:
Scheme
https
Host
example.com
Path
/teams/wildcats
The URL gives the browser structured information about how and where to request a resource.
Consider:
https://example.com/search?team=wildcats
The query parameter is:
team=wildcats
The name is:
team
The value is:
wildcats
Multiple parameters can be separated with:
&
User input may need URL-safe encoding before it becomes query data.
A supplied C# application can combine:
Conceptually:
base URL
+
query structure
+
safe user value
=
constructed URL
The URL is still text until the program asks the environment to open it.
When C# opens a URL, the C# application does not become the browser.
The responsibility flow remains:
C# supplies URL
↓
browser opens URL
↓
browser sends request
↓
server responds
↓
browser renders result
This course activity does not require an automated web API.
The learner can observe information displayed on the webpage and make a true/false judgment.
For example:
Is it raining?
can become:
isRaining = true
or:
isRaining = false
That Boolean can feed simple if or if/else logic.
Module 5 connects several representations and systems:
User input
↓
URL
↓
Query parameter
↓
Browser request
↓
Server response
↓
Displayed webpage
↓
Human interpretation
↓
Boolean state
↓
Program decision
The important skill is understanding which participant or representation is responsible at each stage.