TentangMalaka is promoted from recovered remote evidence only: the local archive is empty, while the remote README and static source tree still document the submission clearly.
This reading path makes the problem choice, evidence quality, user framing, execution decisions, and proof trail visible without overstating what the sources support.
Static article-site submission about Tan Malaka built with semantic HTML, CSS layout work, and small JavaScript navigation behavior.
Provides a source-backed coursework artefact for reviewing semantic HTML structure, static layout composition, and front-end content organization without claiming production usage or audience outcomes.
Single-page static site served from `index.html`, styled through `assets/css/style.css`, supported by image assets, and enhanced by `assets/js/script.js` for responsive navigation and smooth scrolling between page sections.
The case-study layer starts with why this problem was selected and how the context justified investment.
A static article site still needs clear semantic structure, layout discipline, and reviewer-visible criteria to stand out as a credible coursework artefact.
TentangMalaka is reconstructed from recovered remote evidence, so every public claim must stay tightly constrained to what the README, source tree, HTML, CSS, and JS files explicitly prove.
It is worth upgrading because it adds a conservative recovered-source case that demonstrates evidence discipline and foundational frontend structure without inventing unsupported outcomes.
The Dicoding basic web-programming submission required a static website that used semantic HTML sections, appropriate content placement, a profile aside, and layout composition with float or flexbox.
Built a static article website about Tan Malaka with header navigation, main article sections, a quote section, contact/profile aside content, footer structure, responsive styling, and JavaScript-assisted navigation interactions.
Evidence is surfaced with its source type and credibility note so the recruiter can quickly see what is directly backed versus intentionally constrained.
The project record is backed by explicit README, HTML, CSS, and JS source references from the remote repository.
The README documents a basic web-programming submission centered on semantic sections and layout structure.
When formal research artefacts are not available, the page still explains who the work served and why that user framing is justified by the existing sources.
Its strongest verified value comes from submission criteria and source-tree structure.
The implementation proves content organization and semantic composition, even without live audience evidence.
The goal is to show the trace from research and insight to concrete product or system decisions, then to the outcomes those decisions supported.
Each step keeps the movement from evidence to action explicit before the rationale expands it.
Used coursework submission requirements as the baseline definition of success.
Organized article content into explicit sections and supporting static assets.
Promoted the project only after remote evidence was explicit enough for factual recovery.
Each decision keeps the path from insight to execution visible before ending on the outcome signal.
A weakly archived project becomes misleading if portfolio copy extends beyond what recovered files support.
Kept every public claim anchored to the remote README and source tree only.
The project becomes portfolio-safe without overstating its documentation depth.
For a basic web-programming submission, structural correctness matters more than decorative complexity.
Framed the project around semantic sections, layout composition, and small JavaScript behavior.
The artefact reads as solid foundational frontend work.
This section preserves the technical and operational substance: architecture, responsibilities, trade-offs, and implementation quality signals.
Single-page static site served from `index.html`, styled through `assets/css/style.css`, supported by image assets, and enhanced by `assets/js/script.js` for responsive navigation and smooth scrolling between page sections.
Provides a source-backed coursework artefact for reviewing semantic HTML structure, static layout composition, and front-end content organization without claiming production usage or audience outcomes.
Outcome claims remain conservative and source-backed, while proof records and recruiter-safe links surface the strongest verification trail available.
README documents fulfilled semantic HTML and layout submission criteria
Strong case studies show both what was learned and where the current evidence stops.
Next iteration should rebuild a complete local archive, replace placeholder article titles with fully sourced content, and add setup notes before claiming stronger documentation or deployment readiness.