Why simply provide links in the initial release?
- In the init release, listing those links delivers the most valuable information with minimal effort.
Why is the last task strikethrough?
- When breaking down the tasks in the first place, I believed Full Text Search was an important functionality. People need it to search against the site for quick reference. However, I later realized that in the initial stage, the site contained very limited information, so the functionality didn’t make much sense. In addition, the Hugo Relearn Theme implements Full Text Search, meaning one less thing to worry about. Thank you Relearn Theme Contributors
How did you design the site’s technical architecture?
- I leveraged AI to assist in analyzing the tech design. In addition, I understood that I would need to invest time and resources to experiment with and refine both the design and implementation.
Any difficulties in the init release?
- Going from zero to one is always the most challenging part of building a product. Things like purchasing domain, applying for SSL certificate, etc. are relatively easy, because you can get the feedback and adapt to it quickly. However building the site itself, especially for the init release was not that easy.
- The ‘real’ initial release was originally built using the excellent Grav CMS, and it worked pretty well until later I realized below requirements, which ultimately led me to switch to Hugo SSG.
- I’d like to provide ‘historical’ version/release of the entire site and I need it to be done easily.
- The site should be built with static elements as much as possible for better CDN delivery.
- Maintaining a PHP server requires significantly more effort compared to using a static web server.
- As a result, I migrated the site from Grav to Hugo during the initial release itself. I made the adaptation as early as possible to prevent further deviation and minimize technical debt.