Richard Williamson was in the process of migrating the nLab over to the cloud, and he said in this nForum post that he was going to make public the new source code for the nLab on github after the migration is over. However, in this more recent nForum post Richard Williamson has resigned from the nLab with immediate effect.
This will cause a significant number of issues for the nLab in the upcoming future. Since Richard Williamson seems to be the only person working on the migration of the nLab to the cloud, with his resignation, it is very likely that nLab would remain in this half-unfinished state in the foreseeable future, where only about 1/20th of the articles in the nLab are editable, and no new articles are capable of be created. Furthermore, the codebase of the nLab here in Github is now outdated and won't ever represent the actual codebase used by the current iteration of the nLab, since the nLab has already switched over to Richard Williamson's new codebase, which is still private.
adeel
commented
2 years ago
Richard Williamson was in the process of migrating the nLab over to the cloud, and he said in this nForum post that he was going to make public the new source code for the nLab on github after the migration is over. However, in this more recent nForum post Richard Williamson has resigned from the nLab with immediate effect.
This will cause a significant number of issues for the nLab in the upcoming future. Since Richard Williamson seems to be the only person working on the migration of the nLab to the cloud, with his resignation, it is very likely that nLab would remain in this half-unfinished state in the foreseeable future, where only about 1/20th of the articles in the nLab are editable, and no new articles are capable of be created. Furthermore, the codebase of the nLab here in Github is now outdated and won't ever represent the actual codebase used by the current iteration of the nLab, since the nLab has already switched over to Richard Williamson's new codebase, which is still private.