Thanks for supporting RiinoSite & NoE Blog in these days.
2022 is the 10th of this blog project, whose origin name is ‘transaction log’ in 2012.
In early 2015, we published riinosite1.0, which was in wixcom, with fixed template.
In 2017,the website was merged into GithubPage. Since then, GithubPage is the first option to deploy riinosite.
In 2019, we redesigned entire website from scratch using jekyll, and we drop the origin offcial jekyll template.
In 2020, we merged riinosite with website of low illuminance (li.riino.site), and seperated style template, named it as ‘jekyll-theme-panda’.
Today, we get approximately 4 GB data flow each month, and ‘jekyll-theme-panda’ has got over 1.9k downloads.
We can’t got this far without everyone’s help, and we want to say thanks to:
Professor - Yi-Shin Tung , Graduate Institute of Networking and Multimedia, Nationaly Taiwan University.
Professor - Hsuan-Tien Lin, Department of Computer Science & Information Engineering , Nationaly Taiwan University.
Front-end Tech Lead - Damon Zhang, PricewaterhouseCoopers Shanghai AC.
BA Lead - Lily Gao, PricewaterhouseCoopers Shanghai AC.
Professor - Jun Zeng , School of Big Data and Software Engineering, Chongqing University
Professor - Naoaki Okazaki , Okazaki Lab, Tokyo Institute of Techology
Jekyll Community and Ruby Community
who provided important guidance on this project directly or undirectly.
In 2022, we will develop more backend services to support riinosite(RS), and optimize development procedure by pre-built component. Such projects will be launched via open-source libraries, remote servers, and more guidance.
What the next step of this website?
Currently there is no plan to rewrite this website using modern framework, but it may happen in riinosite4.0 in the future. Currently we will send tiny update on component like TOC, and fix bug, maintain 3rd dependences.
Backend services?
What about riinosite 4.0?
Cyber security?