1st paragraph containing a sub-title for the Technicalities section.
2nd paragraph giving a whole lot of technical information about the topic in this section.
Coding:
y = x + 5
- list item A ordered
- list item B ordered
- list item C ordered
Coding:
b = 11
3rd paragraph containing a sub-title for the Read again section.
4th paragraph with really interesting technical information that readers come back to, for reference purposes, again and again.
Coding:
echo "Hey " . $user . "! This is just gr8!"
5th paragraph containing a sub-title for the Examples section.
6th paragraph giving practical examples where people have used the features already explained, so that the reader can relate to the theoretical models given.
Coding:
let i = 0;
- list item D unordered
- list item E unordered
- list item F unordered
7th paragraph containing a sub-title for the Details section.
8th paragraph explaining technical details of this section.
This would be a fairly long section, as it is full of useful details,
explaining the concepts already given.
This could go before the
Examples section, but to prevent the reader from getting bogged
down in detailed explanations, the Examples section comes
before the Details section.
9th paragraph containing a sub-title for the Other Possibilities section.
10th paragraph proposing alternative technical possibilities in order
to give the reader a wider range of possibilities to explore. Apart
from language syntax, which is clearly defined and must be
followed to the letter, all information is given on a take it or leave it basis.
This page is full of information, after all, and
while suggestions of best practice can be offered, it should
not be prescriptive in any way.
Coding:
total += newValue
Another (final) paragraph might contain thanks to contributors and references to research material. This, and other information, such as Copyright and Address, might also be displayed in a footer section, which is not included in this project.
This project is meant to emulate a Technical Information Page, as per
the Javascript example given in the definition of this project.
However, out of the programming languages that I have played around with
so far, I could not make a choice as to which one I should use for my
example of a Technical Information Page.
Add to that my intention to create my test projects from memory, as far as possible, I did not even check the correct Latin filler words in the paragraph below. With minimal use of looking up how to get some effect in CSS, for example, I did add comments to show those little things that had momentarily slipped my mind.
Therefore, I used semi-meanigful miscellaneous words, other than the usual Latin, like 'Lorem ipsom (or was it Lorem ipsem)', to fulfill the required user stories in the project definition. Or perhaps this is just my personal style. After all, just about every programming language already has a technical page of its own. It is not my intentioin to redesign the wheel in this project.
The absense of a glaring white background is easier on the eyes.
And the mellow pink and grey color scheme is
meant to help the reader to relax, so they can stress a little less and
absorb more of the rather interesting technical information on display.