How to create static page for jobs


I am going to implement search using apache solr, I am stuck in the implementation of the static job page.

Is there any way, I can create static pages for all jobs added in the solr search index?


You question requires more context to answer. :slight_smile:

I am looking for serverless solution for new job portal. For static pages or blog pages, I can do it through Hugo static site generator easily but what about job pages. I am going to use amazon elastic search for indexing the job, but for job description page do i need to create 5000 json file for every html job description page and how approx how much time Hugo will take to create 5000 job pages from 5000 json files.

Can hugo create static file one by one? For example if I add one job json file in the system, hugo should create corresponding html job description page on fly? it should nolt rebuild whole 5000 htmls file agian, obviously it will take time.

If it is possible, what is the hugo command to create one single html file?

to quote bep:

basically this is still in the works: Build pages from data source · Issue #5074 · gohugoio/hugo · GitHub

Thanks For Answer
So I need to create 5000 JSON file to create 5000 job description page. What I am thinking about that to create Micro services in golang to create 5000 JSON file for hugo to create static site. Do you think this solution is good as server space is not a problem?
This would be one time job and going forward, I will create one json at the time of new job post.
How can I create one static file without touching/processing other static file on real-time using hugo command for sake of the speed of page generation?

Should I move to Gatsby to create job description on fly using one data source?

If you do not care for search engines to crawl those pages then go ahead.

Search engines always seem to prefer plain HTML, as far as I know.

I have no experience with microservices. But I have created Markdown pages from data sources locally with Bash scripts. So I suppose that you could manipulate the JSON so that each one has its own static description page along with a list.