[eyeo.com] Job links shouldn't use anchors

[fhd]

Background

We currently use job links of this form:
​https://eyeo.com/jobs#web-developer

This makes it impossible for us to see how many page views individual job ads got - it all ends up as ​https://eyeo.com/jobs in the logs.

What to change

1. create generic header (Ex: includes/jobs/generic-header.tmpl) and generic footer (Ex: includes/jobs/generic-footer.tmlp) for job openings page, the information about job openings should go between this generic templates.
2. create pages/jobs.tmpl Where content of the overview page should be placed.
3. create pages/jobs/JOBTITLEs.md for each job opening, where the content of the job should be placed.
4. create pages/jobs/not-available with text like The position you are looking for is no longer available this page will be used to redirect users in case they open the non existing job page.

[saroyanm]

What about using query strings ?
Something like:
​https://eyeo.com/jobs?position=web-developer

@kirill will that work for you ?

[saroyanm]

@Sebastian would it be possible to use query string parameters value in the jinja template ?
I'm looking for similar solution:

<? include jobs/openings/{{ request.args.get("position") }} ?>

I think if we can use url parameter value, than we can have solution for current ticket, otherwise I see only current solutions:

1. Use Javascript to parse url and show appropriate content (Which will have accessibility issues)
2. Create separate page for each position (this will provide problems in maintaining)

I'm actually new to our CMS, so maybe there is some other option I've missed.

[sebastian]

No you can't. It's a static page generator, no dynamic web page framework. Neither would URLs with the job title given in the query string be nice. I actually realized that problem myself in the past. And started to make each job posting an own pages (this is how you would do it), but it became rather complex, that I dumped the code again.

[saroyanm]

Sorry, this got lost from my radar.
Yes that's a problem, so we will need to create separate page for each job opening in that case, it will make the process less manageable so Maren will need to ask us to create new job opening each time.
But I don't see other solution, also in case we will implement metadata would be nice to have separate metadatas for each job opening and beside that I think we will need to change the other pages for consistency and ability to share.

I'll open discourse discussion for that.

[saroyanm]

@Sebastian thanks for hints, the description updated.

[saroyanm]

Updated the not-available page text after aligning with Maren.

[saroyanm]

Revision:
​https://hg.adblockplus.org/web.eyeo.com/rev/0adfccb3182d