PENGIN PI! A CRM with the back bone of a feature light ERP system. Utilitarian in design, easy to extend, customize, and deploy. Made by a community, supported by Tobu Pengin.
We need to create the jobs route in our routes. This should be an independent jobs.py file in the routes folder.
The routes we need to create:
jobs view, the main view when someone clicks the jobs link in the main nav bar. This should be publicly available. If there are no jobs in the database, you should render a default template that states, "We are currently not hiring". Otherwise, we need to render a table that lists the jobs. This should render similarly to how we render the threads in our forums.
job view, the view for a specific job. The form needs to list the job's ORM to completion, similarly to how we render a product from products
job create view: we need the hiring role to be allowed to create jobs from the main view. Needs to only be viewable and permissable to hiring, just like product creation is for admin
job edit: we need to be able to edit the job, just like admin can edit product. Hiring and admin also need to be able to dive down into the job and edit or delete it. This should perform similarly to how we handle product editing
We need to create the jobs route in our routes. This should be an independent jobs.py file in the routes folder.
The routes we need to create: