For me the wiki page is the simpler to maintain and update with this info, however I understand that it is no the better solution, I would suggest to create a parse to get info of the current here and report data in the website. I could work on the parser, writing it in python and run it in a cronjob.
What do you think?
@nbozon do you see a better solution?

hey @veroandreo ! I would love to contribute in this issue,please guide to how to proceed..

hey @veroandreo ! I would love to contribute in this issue,please guide to how to proceed..

Hi @rinkydevi! Thanks for your interest! What exactly you would like to contribute to? If what @lucadelu suggests, then he is the one that should guide you :) AFAIU, his idea is to parse some content from https://grasswiki.osgeo.org/wiki/Sponsors into the grass website, especially the "Sponsors" subpage under the Contribute menu.

If you are interested then, please fork this repo following instructions here, install hugo, study how it works (I know only lil), make small changes and tests (some instructions in the README), build the site locally, and when you are ready to contribute, create a PR from your fork.

@veroandreo i can the make make the sponsers subpage and a option under contribute menu

it will take i while but i will do it

For the instructions to set up for contributing and testing changes to grass-website, just take a look at this repo's README. I was quite impressed with the simplicity of Hugo. Literally you use "hugo server" in the root directory of this repo, and it is ready in two seconds. There is a link to ope n to a local website. When you're editing an input file, each time you save this page is rebuilt and the webpage is reloaded automatically in a fraction of a second. Quite painless!

my 2 cents in this old issue. I'd argue, as @veroandreo was proposing, that it may be good to have this info in the site (at least because it looks nicer than the wiki), rather than being redirected to the wiki. @lucadelu I may be missing something, but as both Hugo and the Wiki can be edited using markdown I don't understand why having an additional piece of code + a cron job just for parsing info in the wiki (more code to maintain, debug, more space to get things wrong, etc) would be easier to maintain and update than having an html or markdown in Hugo. Besides, that wiki doesn't seems to be updated that frequently...