Skip to content

Commit 5810ffc

Browse files
authored
Improve clarity in quickstart.md
Clarify the accessibility of job openings and the saving path for ojobpub.json.
1 parent 9a6ff20 commit 5810ffc

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/implementation/quickstart.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,10 +5,10 @@ There are 5 easy steps to revolutionize job publishing.
55
## 1. Website
66
You need **your own domain and website**: e.g. www.example.com.
77

8-
You publish your full description of your job openings in a web page. This can be using a CMS, static site generator or plain HTML, as you like. As a result, your job opening are linkable like: https://www.example.com/career/job-product-manager/.
8+
You publish your full description of your job openings in a web page. This can be using a CMS, static site generator or plain HTML, as you like and become accessible using a link, e.g. https://www.example.com/career/job-product-manager/.
99

1010
## 2. Create ojobpub.json
11-
Create an [ojobpub.json](./ojobpub-format.md) in the path `/.well-known/ojobpub.json` (all lower case!) in a **specific JSON format containing structured meta information** about your job openings and link to the full job description on your website.
11+
Create an [ojobpub.json](./ojobpub-format.md) and save it under the path `/.well-known/ojobpub.json` (all lower case!) in a **specific JSON format containing structured meta information** about your job openings and a link to the full job description on your website.
1212

1313
!!! tip "File or Application?"
1414
While we have used a static ojobpub.json file to demonstrate the simplest way to provide the data, this endpoint is not limited to a static file. It could just as easily be served by a dynamic application or script. An open source tool to help creating a ojobpub.json is currently in development.

0 commit comments

Comments
 (0)