replace `npm+hugo+bash` with `getpelican`

[eladkal]

This should make release process easier

[Satish-Medar]

Hi sir, I would like to work on this issue. Please assign it to me. I will replace npm + hugo + bash with getpelican as requested. Thank you!

[NarmalaSk]

Hey eladkal I want to work on this migration of npm+hugo to getpelican.but Is there any new branch so that I can develop get pelican version of airflow in that Branch and Submit the prs Also It is important that airflow site need to be in python

Also working on new branch keeps it as staging you know

[NarmalaSk]

@eladkal @potiuk what do you guys think ??

[rawwar]

Hey eladkal I want to work on this migration of npm+hugo to getpelican.but Is there any new branch so that I can develop get pelican version of airflow in that Branch and Submit the prs Also It is important that airflow site need to be in python

Also working on new branch keeps it as staging you know

@NarmalaSk , Are there any issues to do this on your fork branch and raise a PR?

[NarmalaSk]

@rawwar I can do that for suppose I will change a requirements.txt, raise a pr workflow fails and if I think I build full site,keep a bunch of prs ,how they can review all files it would be around 1k+ files right. If it is in a new branch it will go smoothly, These are my thoughts But if we can do like that I will do

[eladkal]

@NarmalaSk You can not work directly on branches in this repo as you don't have write privileges.
The work needs to be done on your own fork.

[NarmalaSk]

fine eladkal i have understood ,can you assign the issue to me

[eladkal]

Note the umbrella issue for modernizing our doc build process
apache/airflow#44373

[potiuk]

Superseded by #1244. No need for "getpelican" etc. cc: @kaxil