Unused File Cleanup
During development, sometimes we left unused files in our repository. Tracking which one that is not relevant anymore could be a problem. As a part of the plan to improve our codebase, we encourage you to check against your files, see if you can find any unused files and remove it.
Web Infra Team (kudos to Ferdinand) has been helping to make the process easier. See this link for more information: https://github.com/traveloka/www/wiki/Auditing:-Finding-Unused-Files
Old Feature Control Cleanup
Some of us might familiar with WEB_FEATURE_CONTROL Content Resource. In the good old days, we use that content resource entry as a feature control. But now, we have Web Feature Control: https://content.traveloka.com/feature-control-web
Have you seen the announcement in #frontend-club? If you haven't, Web Infra Team will remove WEB_FEATURE_CONTROL Content Resource entry in the end of June. So, if you still use it, kindly migrate your feature control to our new feature control. You can use <FeatureControl />component to replace your old feature control if you still need one.
Operational Tools as Static Website Migration
Our operational tools are currently running in some of EC2 instances. If you noticed, we are currently don't need any server side processing, so running those instances might a bit overkill.
That's why, Tools Infra Team currently will convert those instances into certain kind of static files. With this, we can reduce the operation cost, and also serve our tools easily. However, there will be some things that we should do. See their plan here: https://docs.google.com/document/d/1ntLdq91hydK5glMNiSg0MzTYaKB0TycmHpfGgcnDA24/edit#heading=h.eqb7boffelmk
Project Themis (Technical Excellence Metrics Dashboard)
Anyone know about https://layar.test.tvlk.cloud? As a part of the effort to maintain Web Tech Excellence Metrics, we will need a dashboard to see where we currently standing. Also, it will be nice if we can see the progress from time to time.
Core Infra Team currently are executing a project codenamed Themis. In the future, tech excellence metrics will always be measured against every Pull Request, so any changes that potentially disrupt our operation, or makes our performance suffer will not be allowed to merge.
Join #themis channel if you want to closely follow their progress.
Micro-Frontend Preparation
Imagine if one day, we can release our web separately, without affecting other product. Dream no more, since Web Infra Team currently is preparing for micro-frontend to allow us to have this capability in the future.
However, there will be some efforts needed from us. Currently, they are assessing the details of each page to ensure that we can safely separate each of the page implementation. There are some things that they still need to struggle with like how do we manage the new repository, how do we maintain the CI/CD process, and how to manage the dependency better.
For this initiative, @web-evangelist will ensure that you are always up to date.