We have about 6 000 documents in our main content pages. Regenerating static HTML version, send to a Lucene index every updated document at every merge to master would be intensive for no real benefit.
How about we remove the need for the static site generator to require a full generation run at every change. One reason most static site generator has to require a full run are cases when you want to list folders with sub pages.
Why not leverage an already baked-in feature from the web server and let it generate sub pages for us.
That way our static-site generator won’t need to have this task to be done.
Expected tasks
We have about 6 000 documents in our main content pages. Regenerating static HTML version, send to a Lucene index every updated document at every merge to master would be intensive for no real benefit.
How about we remove the need for the static site generator to require a full generation run at every change. One reason most static site generator has to require a full run are cases when you want to list folders with sub pages.
Why not leverage an already baked-in feature from the web server and let it generate sub pages for us.
That way our static-site generator won’t need to have this task to be done.
Expected tasks