CineBlue is promoted from recovered remote evidence only: the local archive is empty, while the README, package metadata, Webpack configs, and 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.
Dicoding front-end course submission for a movie search web app with movie listing, title search, genre filtering, responsive UI, and Webpack-based delivery scripts.
Provides a source-backed frontend delivery artefact that demonstrates API-backed UI composition, custom elements, responsive layout work, and reviewer-oriented setup documentation.
Vanilla JavaScript application initialized from `src/app.js`, composed with custom elements, backed by TMDB fetch calls in `data-source.js`, styled with CSS and Bootstrap, and bundled through Webpack common/dev/prod configs.
The case-study layer starts with why this problem was selected and how the context justified investment.
The course submission required a custom dynamic frontend that combined ES6, custom elements, Webpack, and AJAX data flow in one coherent app.
CineBlue is reconstructed from remote source evidence, so the portfolio framing must stay tightly bound to what the README, source tree, and configs explicitly prove.
It is worth highlighting because it shows disciplined frontend delivery under explicit technical constraints while also demonstrating conservative evidence handling.
The Dicoding fundamental front-end submission required a custom web application that used ES6 JavaScript, custom elements, Webpack, and AJAX-driven dynamic data.
Built a movie-search web app that renders popular movies, handles title search, supports genre-based discovery, and bundles the app through separate development and production Webpack configs.
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 scope was driven by explicit Dicoding requirements around ES6, custom elements, Webpack, and AJAX-driven dynamic data.
Movie listing, title search, genre search, and responsive display are all documented in source-backed materials.
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.
The documented feature set centers discovery interactions rather than account or transaction flows.
The submission criteria are explicit and meaningfully shaped the implementation choices.
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 course requirements as the baseline definition of what the product needed to prove.
Centered the UI around browsing, searching, and filtering so dynamic data handling remained visible to reviewers.
Separated development and production build behavior through dedicated Webpack configs.
Each decision keeps the path from insight to execution visible before ending on the outcome signal.
A componentized structure was needed without moving away from the required vanilla frontend stack.
Used custom elements for UI composition.
The app remains aligned with the submission requirements while keeping the interface modular.
Frontend review quality depends on both runtime behavior and build discipline.
Used common, dev, and prod Webpack configs.
The project demonstrates delivery-oriented frontend thinking, not just page rendering.
This section preserves the technical and operational substance: architecture, responsibilities, trade-offs, and implementation quality signals.
Vanilla JavaScript application initialized from `src/app.js`, composed with custom elements, backed by TMDB fetch calls in `data-source.js`, styled with CSS and Bootstrap, and bundled through Webpack common/dev/prod configs.
Provides a source-backed frontend delivery artefact that demonstrates API-backed UI composition, custom elements, responsive layout work, and reviewer-oriented setup documentation.
Outcome claims remain conservative and source-backed, while proof records and recruiter-safe links surface the strongest verification trail available.
README documents fulfilled submission criteria for Belajar Fundamental Front-End Web Developer
Strong case studies show both what was learned and where the current evidence stops.
Next iteration should rebuild a complete local archive, remove exposed API keys from source history if still active, and add neutral architecture diagrams before claiming stronger operational readiness.