Website Maintenance & Expansion

Apr 2023 - Dec 2024

Role: Web Developer

Project Link
Website Maintenance & Expansion thumbnail
Tech Stack

Overview

This project covered the first long chapter of my BRIX engagement, starting when I was hired to take over an existing static landing page after the previous developer was no longer involved. During the first year, the scope was mostly limited to maintenance work such as moving the environment, cleaning up the interface, and keeping the existing pages stable. After the contract was extended in April 2024, the work expanded into adding new pages and restructuring parts of the landing page while still staying on a static HTML, CSS, and JavaScript setup.

In Collaboration With: Direct Client

Responsibilities

  • Took over the inherited Hostinger environment and kept the existing landing page running after developer handoff
  • Focused on responsive cleanup and visual tidying during the first year while the client did not request major additions yet
  • Maintained the original static pages such as Home, Product, Warranty Statement, Privacy Policy, and the old Gallery page
  • Removed the Gallery page when the content direction changed in the second phase
  • Built a static distributor page that initially displayed distributor cards
  • Added an article section to support broader content publishing and SEO-oriented website growth
  • Split the original combined product page into two separate pages for clearer structure
  • Handled practical GitHub-based versioning while continuing updates on the static site

Outcome

By the end of this phase, the inherited landing page was no longer just being kept alive. It had become cleaner, more responsive, and more complete from a frontend perspective, with additional distributor and article pages plus a clearer product-page structure. Just as importantly, this phase exposed the limitations of the static setup clearly enough to support the later CMS proposal.

Detailed Breakdown

The section above is optimized for fast recruiter review. If you want the full implementation context, open the details below.

The website began as a very simple static landing page inherited from a previous developer, and in the first year the goal was mostly to keep it stable rather than rebuild it. When the contract was extended, the challenge changed: new pages had to be added for distributors, articles, and product restructuring, but everything still lived in a static setup that showed its limitations through rigid file-based pages and less polished URLs such as .html paths.

The solution in this phase was not a full system rewrite yet, but a controlled frontend expansion. I stabilized the inherited environment first, improved the responsive layout, then extended the landing page structure with new static sections so the site could keep evolving until it was mature enough to justify the later CMS proposal.

Year-One Maintenance Flow

01

Take over the inherited static landing page and review the existing page set: Home, Product, Warranty Statement, Privacy Policy, and Gallery.

02

Keep the site running by handling environment continuity in Hostinger and cleaning up the layout where needed.

03

Improve responsive behavior and basic frontend quality without changing the website scope too aggressively.

Year-Two Expansion Flow

01

Remove the Gallery page as the content direction changes.

02

Add a static distributor page, then expand the site further with article pages to support stronger SEO content publishing.

03

Split the original product page into two separate pages and continue frontend adjustments even though the site structure still remains file-based.

This phase was still fully static, so the work was closer to practical landing-page maintenance and frontend expansion than to application development. It became an important learning chapter because I was dealing directly with responsive layout work, Hostinger infrastructure, GitHub usage, and the basics of maintaining a static HTML, CSS, and JavaScript website in a live client environment.

Implementation Flow

01

The inherited static files are reviewed first so the existing pages can be understood and stabilized before any broader changes are made.

02

Responsive fixes, visual cleanup, and environment continuity are handled directly inside the static codebase while the site remains deployed on Hostinger.

03

When the scope expands in the second year, new static pages and frontend restructuring are added incrementally without introducing a database yet.

Implementation Details

  • Worked on a static HTML, CSS, and JavaScript landing page codebase
  • Learned and applied responsive landing page adjustments in a real client-facing environment
  • Handled practical hosting continuity and environment familiarity on Hostinger
  • Used GitHub in an ongoing update workflow while maintaining the live site
  • Maintained a simple page structure consisting of Home, Product, Warranty Statement, Privacy Policy, and the old Gallery page in the early phase
  • Expanded the frontend by adding static distributor and article pages plus splitting the product page into two
  • Observed structural limits of static delivery such as visible .html routes and less flexible content management

This phase was technically simple compared with the later CMS work, but it mattered because it built the operational understanding and frontend baseline that led directly into the next system-improvement proposal.

Explore More Projects

A few more top picks that show adjacent product, platform, and operations work across the portfolio.

View All Projects
Brill One-Page Landing Page Development preview Brill One-Page Landing Page Development Brill Hepa Filter | New product development Strapped Plate Generator Enhancements preview Strapped Plate Generator Enhancements Strapped Plate | Product enhancement QRIS Refund Reconciliation System preview QRIS Refund Reconciliation System Alfamart | New product development Stock Opname Application preview Stock Opname Application BRIX Performance | New product development