Implementing the customization feature brought me face-to-face with a significant challenge: the code that constituted each webpage was highly personalized. This meant that adding new functionality would require creating new code that didn't disrupt existing features, tailored to the unique structure of each of the four different webpages.
Despite my concerns about the potential complexity and time investment, I decided to attempt the implementation before considering giving up. Adopting a "try first" mindset, I started coding.
Fortunately, the coding was successful, but I sensed that adding a few more features could enhance the user's ability to have a clearer, personalized digital reading experience. After searching Google Scholar and randomly reading academic papers, I noticed that each site had varying paragraph lengths.
This idea clearly had the potential to enrich the customization feature. However, I realized that implementing this would be more challenging than adjusting font sizes, as it would involve altering paragraphs, padding, or margins – not just a simple CSS tweak. Faced with this technical dilemma, I shared my concerns with Andreas, who advised that technical problems should not become obstacles for design. Reaffirming my mindset as a designer, I began to work on the code implementation. The resulting product was as follows.
Testing the website post-implementation, I could feel that the new feature indeed made reading easier for users. It was a function that aligned well with the objectives of my project and brought a sense of satisfaction. The last two weeks were not only about implementing the work but also provided a clear reflection on my dual roles as both a designer and a developer. Coding was utilized as a tool to realize my work, and ultimately, I engaged with the project as a designer. This experience was pivotal in deciding the direction of my future career path.