just started learning web dev and i made a small project with html and css. I'm trying to figure things out on my own without tutorials that walk me through the whole thing. only looking up stuff when i get stuck. Any tips from people who remember their first project would be awesome
I recently finished a ~6 month course on web development. JavaScript, TypeScript, CSS, Maven and other modern horrors influenced me to rebel again today's often bloated approach of developing websites and aplications.
"Developer" became a dirty word for me. The thinking (or should I say lack if thinking?) that everywhere is fast internet and infinite amount of computing resources tickles my mind in a uncomfortable way.
Sure, computers are fast, packets travel across the underwater optic cables nearly at the speed of light but it looks to me that a lot of web and software development is allowing bad practices and sloppy code because "just throw more resources at it".
I don't want to be a developer, I wish to become a programmer.
Thus, I made 100% pure HTML website to document my journey into the embedded systems and low level programming (and maybe a few more things along those lines).
It's may not be perfect, it may not follow the best of the best practices but I will get there as I go.
EDIT: Took note on the comments and updated the site. Not all is implemented that was suggested. The suitable color scheme for Darth Vader still awaits among many other ideas. Instead, I played around with tables, not sure if this is the way to go. But we'll see. This is an experiment, a fucking rebellious and hackish experiment, to see how far can this be pushed and still stay withing the bounds of pure HTML.
Also I need help cause I wanted to make the text brown by using the css but the code doesn't work, what am I doing wrong? Or I just cannot see it and it actually worked?
Okay, like i have no experience. So i memorized what i knew thoroughly, and made this:
Oh and if you want to change it or add more to it then here's the entire thing (Can i just put it in the body or have to give a link?): <!DOCTYPE html>
<p>Cucumbers are green-darkgreen vegetables that are said to be made up of over <b>95% water. </b><br>They originate in <i>Ancient China </i>& parts of Asia like <i>India, and Nepal</i></p>
<p>Cucumbers are of course, an important part of agriculture, they feed millions everyday.<br></p>
<p>Cucumbers are eaten & sold all around the world, they're mainly eaten as light snacks.<br></p>
<p>Cucumbers have a taste as of water but with crunch. Seasoning with salt makes them around 100x better. <i>(Okay i made that 1 up but it's not false...)</i></p>
Everyone knows <b>, <i>, <a>, and <code>. But HTML has a whole second cast of inline elements that most developers go entire careers without typing once — <ins>, <dfn>, <abbr>, <var>, <q>, <mark>. Not because they're broken or deprecated. They're rare because the use cases are genuinely narrow, and when one does come up, the reflex is to reach for a <span class="something"> instead.
I bumped into this building out a prose/content section for a UI system — once you start styling text properly, you notice how many real semantic elements you'd been ignoring. So here's the whole forgotten cast, in a single sentence that legitimately uses eleven of them:
Here's what that actually is:
<p>
The experiment revealed <mark>a significant energy spike</mark> in
the reactor core. Previous readings of
<del>42.7 terawatts</del> were revised to
<ins>51.3 terawatts</ins> after recalibration. The formula
<var>E</var> = <var>mc</var><sup>2</sup> governs the conversion,
where H<sub>2</sub>O serves as the coolant medium.
<abbr title="Void Energy Reactor Interface">VERI</abbr> logs
confirm the anomaly. As Dr. Vasquez noted,
<q>the readings exceed all theoretical models</q>
(<cite>Void Research Quarterly</cite>). This phenomenon, known as
<dfn>energy cascade</dfn>, occurs when containment thresholds are
breached. The <s>original safety protocols</s> have since been
replaced.
</p>
The cast, and where you'd actually use each
Edits and corrections.<ins> and <del> are added and removed content — they pair up for change tracking, and both accept datetime and cite attributes so the edit is machine-readable. <s> is the one people conflate with <del>: it marks content that's no longer accurate or relevant (a stale price, an outdated claim), which is a different statement than "this was deleted." Two elements exist precisely because those mean different things.
Notation.<sub> and <sup> are for cases where the position carries meaning — chemical formulas (H₂O), exponents (I²R), ordinals, footnote markers — not for "make it small and raised." <var> is a variable in math or code, which is why P, I, and R above are each wrapped in one.
Reference and meaning.<mark> is a relevance highlight — it's literally what search engines use to highlight your query in the results. <abbr title="…"> gives an abbreviation its expansion, surfaced as a tooltip. <dfn> marks the one spot where a term is defined (its introducing instance, not every later mention). <cite> is the title of a work — a book, paper, album — and notably not a person's name, which is the thing nearly everyone gets wrong. And <q> is an inline quotation where the browser inserts the quotation marks for you: correct for the document's language, and correctly nested if you put a quote inside a quote. You never type a " again.
Why bother
Every one of these throws a bit of meaning into the page that a styled <span> silently discards. Screen readers announce them. <q> localizes its punctuation. <abbr> exposes the long form. <ins>/<del> are a real, parseable changelog. A <span class="highlight">looks the same and means nothing.
The only honest reason to avoid them is that the browser defaults are inconsistent and, frankly, ugly — <mark> is highlighter-yellow, <q>'s marks are whatever, half of them are unstyled. But that's a few lines of CSS, not a law of physics. Give <mark> a brand-tinted background, <ins> a green underline, <abbr> a dotted one, <q> colored quote marks, <dfn> an italic weight — and suddenly an entire sentence of semantic richness reads as clean, deliberate typography.
Most of these you'll reach for maybe once a year. But once a year correctly — with the meaning intact and the styling handled — beats a <span> that's lying about what it is.
I finished writing this a little while ago, it’s called THE WINDMILL, and it’s a horror adventure type game, entirely written in html.
Each screen is individually drawn from a text template inside <pre> tags, and functions using page timers, a random number generator, and is otherwise a click puzzle like myst. You can pick up items, each item is a separate folder containing the entire game, modified to take into account you having that item.
The game design is about 2500 separate html files, copied over to each item folder lol.
I'm a person who studies and builds websites. When looking for design and layout inspiration, I visit many different websites.
However, I've noticed that a surprisingly large number of sites still don't follow semantic HTML practices and have poor accessibility support. This includes sites from small businesses as well as larger companies.
Is it the same where you live? Do you also see many websites that don't properly implement semantic HTML and accessibility standards?
SOLVED. Thanks folks! I am working on a basic level HTML homework assignment. It is required that some of the text should be bold, but not all of it. I don't understand why all text is automatically bold. Or is that the font? I am including what my webpage with code looks like and the code that went into the webpage.