Monday, April 21 2025 \u2013Last week, Mr. Peter asked me to redesign part of a page layout to improve readability and make it easier to extract information. The page contained multiple tables and lots of data, so clarity was key. Since the existing layout was developed by the previous person in charge, I first took time to understand the underlying code to ensure a smoother redesign process.<\/p>\n\n\n\n
After familiarizing myself with the structure, I experimented with various styles and layout arrangements through trial and error. My goal was to achieve a cleaner, more user-friendly interface and in the end, I landed on a final version that I believe significantly improved the overall look and feel.<\/p>\n\n\n\n
In addition to the redesign, I continued testing other features as thoroughly as possible. During this process, I discovered a small but important bug: when creating a new data entry, the recorded time (not the date) was incorrect. Once the underlying issue in the API was fixed, I proceeded to implement the necessary changes, and the bug was successfully resolved.<\/p>\n\n\n\n
Toward the end of the week, I began tackling another concern, restricting unauthorized users from accessing the UI page directly. Although they couldn\u2019t access any data, having the UI visible still posed a security concern. After some research, I found an article suggesting several methods to handle this. One approach seemed practical and aligned with our needs, so I discussed it with Mr. Peter. He agreed to let me try it out.<\/p>\n\n\n\n
Before making the changes, I cleaned up the code and committed all current updates to avoid mixing them with the upcoming major changes. Although I attempted to implement the new method by the end of the week, it didn\u2019t fully work. I shall continue this task this week.<\/p>\n","protected":false},"excerpt":{"rendered":"
Monday, April 21 2025 \u2013Last week, Mr. Peter asked me to redesign part of a page layout to improve readability and make it easier to extract information. The page contained multiple tables and lots of data, so clarity was key. Since the existing layout was developed by the previous person in charge, I first took … <\/p>\n