Thanks for supporting RiinoSite & NoE Blog in these days.
2022 is the 10th anniversary of this blog project, whose origin name is ‘transaction log’ in 2012.
In early 2015, we published riinosite1.0, which was in wixcom, with a 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 dropped the origin jekyll template hux.
In 2020, we merged riinosite with website of low illuminance (li.riino.site), and isolated style template, named it as ‘jekyll-theme-panda’.
Today, we get approximately 4 GB data flow each month, and ‘jekyll-theme-panda’ got over 2k downloads.
We can’t get this far without everyone’s help, and we want to say thanks to:
who provided/is providing very important guidance, help and impact on this project directly or indirectly.
In 2022, we will develop more backend services to support riinosite(RS), and optimize development procedure by pre-built components. Such projects will be launched via open-source libraries, remote servers, and more guidances.
What is 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 to fix bug, maintain 3rd dependences.
We are working on a project that initially owns high maturity architecture, security and IAM system with many experience of best practices. The basic idea is to use a simple flask core, driven by python asyc style redux manager which we are still working on at current step. And we also did a tech assessment to choose possible global storage and computing vendor. According to latest risk doc, we would like to use fully encryption when using vendor’s service, so this entire project will last 1-2 years at least to complete. Now we are still in infra development, once this is done, we can publish first prototype with a universal SSO system to support entire riinosite series resources, including NOE blog(this one) and low illu and any projects in future.
What about riinosite 4.0?
Currently we do not have an actual plan to migrate riinosite to any other frameworks or cloud vendors, unless there is an important feature that we desire to archive. Nevertheless, there is a fancy ‘riinosite 4.0’ topic that to use modern framework to rebuild this website. We may also consider dirty hybrid mode with techs like beautiful react hooks, but again, everything is just on paper.
We will release a series standard docs this year, by the our new pipeline for documentation and announcement ‘NoEVoix’. Among these docs, the risk one will include cyber security guidances including the references from OWASP, NIST , etc. As for riinosite, we will do nothing at current risk level, since: a) riinosite is a static website b)There is no confidential message since we haven’t enable login method or 3rd comment method.