Closed kmuehlbauer closed 2 years ago
Currently pelican
is moving plugins to a new place, changing registering of plugins etc. This leads to some issues with the current builds. I've disabled some of the plugins, to get it building again.
This needs revisiting.
@mgrover1 did great efforts to bring the openradarscience landing page to the new ages. Thanks a bunch! This looks very nice and we can work from that updating the different package sites.
https://mgrover.dev/open-radar-test/
We would need to decide, how to incorporate this. Currently we have a repo (this very repo) for the sources and a repo for the actual html representation (https://github.com/openradar/openradar.github.io). I'd suggest to archive this very repo and move everathing to https://github.com/openradar/openradar.github.io.
As there is some bot-magic involved we need to be careful bringing everything into place. @mgrover1 let's talk this though tomorrow.
Thanks @mgrover1, great job.
The page is now powered by new infrastructure. Issue resolved.
Citing from a comment by @jfgui https://github.com/openradar/openradar-landing-page/pull/11#issuecomment-871920721:
Another thing we could add is a page where publications are listed.
I've thought about that too, but without using GitHub infrastructure this would be much more complicated. I've described the process to add news in the wiki https://github.com/openradar/openradar-landing-page/wiki/dev.-News. If we think, that creating a pull request is too much of a problem, we could think about using GitHub issues for that.
The idea is:
news-approved
) to the issue.I'm not sure, if we can circumvent pull requests (pushing directly from an issue workflow). If not, we could use the [openradar-bot(https://github.com/openradar-bot)] to fork and pull request the news entry.
Thoughts or other ideas?