Career Page

[ChiragSinghal2001]

Related Issue

Closes: #[issue number]

Description of Changes

Checklist:

• [ ] My code adheres to the established style guidelines of this project.
• [ ] I have conducted a self-review of my code.
• [ ] I have included comments in areas that may be difficult to understand.
• [ ] I have made corresponding updates to the project documentation.
• [ ] My changes have not introduced any new warnings.

Screenshots

Original	Updated

Please provide any necessary screenshots to illustrate the changes made.

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
grabtern-frontend	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 29, 2024 5:10am

[github-actions[bot]]

Thank you, @ChiragSinghal2001, for creating this pull request and contributing to GitHub-ReadMe! Our review team will thoroughly review the pull request and will reach out to you soon! Please make sure you have marked all the completed tasks as done. We appreciate your patience and contribution!

[ChiragSinghal2001]

[anmode]

note: we have to create an API for updating, and creating job posts. We will have the UI in the admin dashboard.

[anmode]

One important to note: in future may be we will passing more URL params as refer id.. how we will handling those? Is it possible to handle that via using page routing. can we simple have index.js in place of [jobID].page.js?

[ChiragSinghal2001]

One important to note: in future may be we will passing more URL params as refer id.. how we will handling those? Is it possible to handle that via using page routing. can we simple have index.js in place of [jobID].page.js?

we can create something like ([...params].js) to catch all routes if dynamic params increase .

[ChiragSinghal2001]

note: we have to create an API for updating, and creating job posts. We will have the UI in the admin dashboard.

The API to create job posts has already been added to the backend.

[anmode]

One important to note: in future may be we will passing more URL params as refer id.. how we will handling those? Is it possible to handle that via using page routing. can we simple have index.js in place of [jobID].page.js?

we can create something like ([...params].js) to catch all routes if dynamic params increase .

Umm.. this needs to be rethink. Let's connect to have discussion over this!

[ChiragSinghal2001]

One important to note: in future may be we will passing more URL params as refer id.. how we will handling those? Is it possible to handle that via using page routing. can we simple have index.js in place of [jobID].page.js?

we can create something like ([...params].js) to catch all routes if dynamic params increase .

Umm.. this needs to be rethink. Let's connect to have discussion over this!

Sure

[ChiragSinghal2001]

Changes in UI in new commit

[anmode]

Some last small fix: 1. In case of no job do not show the header of the page ( which is open position...)( does not look )

2. 

   black color looks very odd ( white would be good)

[ChiragSinghal2001]

Some last small fix: 1. In case of no job do not show the header of the page ( which is open position...)( does not look ) 2. black color looks very odd ( white would be good)

okk sure

[ChiragSinghal2001]

Some last comment.. Nd is it mobile responsive?

yes it is

[ChiragSinghal2001]

UI is improved and a new page added

[anmode]

@ChiragSinghal2001 cool, Really amazing thanks for making this 🚀 . Please make sure to take it down your API key as this repo is open-source. We will create our own API key.