-
Notifications
You must be signed in to change notification settings - Fork 0
/
post-an-ad.qmd
123 lines (83 loc) · 6.25 KB
/
post-an-ad.qmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
---
toc: true
---
# Post a Job Ad
::: {.notice .notice-blue}
💡 You can email `jcrouser@smith.edu` if you run into any problems or need help.
:::
::: {.notice .notice-red}
It's polite to **close** your ad after your search has officially concluded.
:::
While we often post positions quickly after they are publicized, departments can also add their own advertisements to the site. **Make sure your department and university aligns with the website criteria**. [See the criteria](/#sec-criteria) for more information.
## Ways to Post
There are two ways to post your ad:
1. You can add your information by **editing our Github repository** (and eventually creating a pull request). Follow the instructions on the page below. **This is our preferred method for users who are comfortable navigating GitHub and editing plaintext files.**
2. If you do not feel comfortable navigating GitHub or editing plaintext files, you can email `jcrouser@smith.edu` and Jordan will happily post your ad for you.
## Required Content
Each job posting includes several required metadata fields, as well as a brief description of the position.
### Required Metadata Fields
The following information is required for every job posting, whether submitted on GitHub or via email. If submitted via GitHub, you are responsible for populating these fields in the YAML frontmatter of your job posting. If submitted via email, please include this information in your email.
- **Institution**: the name of your institution.
- **Location**: the city and country of your institution.
- **Deadline**: the date by which applications should be received. If the deadline is soft/rolling, please provide an approximate date or the day on which review of applications will begin.
- **Active**: whether the position is still open.
- **Type**: the type of position: tenure track, visiting, or adjunct.
- **URL**: a link to the official job posting.
### Guidelines for Job Descriptions
We encourage you to heavily abbreviate the official job description in order to minimize boilerplate and convey as many concrete, salient facts about the position as possible. We especially encourage you to communicate considerations like:
- Teaching load
- Availability of startup funds
- Availability of sabbaticals, especially pre-tenure sabbaticals
- Desired research areas, of applicable
- Desired seniority level, of applicable
We strongly encourage all job descriptions to be **one paragraph**, followed by a single line describing the review process and date.
## Posting on GitHub
::: {.notice .notice-blue}
Following these instructions requires an account on github.com. If you don't already have one, the best approach is probably to [email your posting](#emailing-your-posting).
:::
To post on GitHub
1. Navigate to the `jobs` folder of the `cs-pui` repository on GitHub, [linked here](https://github.com/cs-pui/prototype/tree/main/jobs).
2. Click the "Add file" button and select "Create new file".
3. Name your file with the following format: `Institution-Name-YYYY-MM-DD.qmd`, filling in the name of your institution as well as the year, month, and day of the closing of the position. Note that the file extension must be `.qmd`, **not** the more-familiar `.md` extension for markdown documents.
4. Copy and paste the following code block into your new file.
- Hovering over on the upper right of the code block will reveal a clipboard icon. You can click this icon to instantly copy the code.
5. Replace the placeholder metadata and text with the actual information for your posting.
6. Click the green "Commit changes" button at the bottom of the page.
7. Choose to create a new branch and start a pull request. The exact name of the branch is not important.
8. Click the green "Propose changes" button.
That's it! One of the site maintainers will review your pull request, make any required formatting changes, and merge it onto the site shortly.
### Formatting Requirements
Please attend to three small pieces of formatting, which are all illustrated in the code block below:
1. Please separate the line describing the deadline and deadline approach from the main description using **two** consecutive `<br>` tags.
2. Please ensure that the 🗓️ icon appears at the beginning of this line.
3. Please ensure that the deadline itself is surrounded by triple `***` on both sides, like this: `***October 1st, 2024***`. This will render as a highlight: ***October 1st, 2024***.
- Please also check that the date you describe in this line matches the deadline in the metadata.
```yml
---
institution: Example College
location: Example City, Example Country
deadline: 2024-10-01
active: true
type: Tenure Track
url: https://cs-pui.github.io/
---
St. agur blue cheese edam **mascarpone**. Port-salut stinking bishop when the
cheese comes out everybody's happy cut the cheese cheddar paneer cheddar feta.
Queso blue castello queso gouda smelly cheese chalk and cheese cottage cheese
cheese on toast. Cheese slices pepper jack cheese on toast cheese and biscuits.
**Mascarpone** blue castello *cheeseburger*. St. agur blue cheese st. agur blue
cheese cheeseburger bavarian bergkase cheesy feet squirty cheese who moved my
cheese jarlsberg. Cheese and biscuits danish fontina pepper jack blue castello
camembert de normandie emmental airedale airedale. Who moved my cheese st. agur
blue cheese.
<br> <br>
🗓️ Review of applications begins ***October 1st, 2024*** and will continue
until the position is filled.
```
## Emailing your Posting {#email}
To email your posting, please include both the required metadata and the job description in the body of an email to Dr. Jordan Crouser (`jcrouser@smith.edu`).
## Closing Your Ad {#close}
After your search has officially concluded, **please close your ad**. To do so, you can again work either through GitHub or through email.
1. On Github, please navigate to the `*.qmd` file for your job posting. Change the `active` field from `true` to `false`. Please again commit your changes to a new branch. We'll merge in your changes to close the job.
2. You can also email Dr. Jordan Crouser (`jcrouser@smith.edu`) with a request to close your ad. Make sure to clearly identify which ad is yours, especially if your institution has made multiple postings this job season.