improve meta site, allow edit, minor fixes

Author: resmo

docs/index.md

@@ -14,4 +14,4 @@ oJobPub is an initiative with the goal, to create a free, simple and efficient p
 
 ## No Goals
 
-- [ ] oJobPub.org is **not** meant to be *another job board*, even though we might publish collect jobs publish using oJobPub just as a *PoC*.
+oJobPub.org is **not** meant to be *another job board*, even though we might publish collect jobs publish using oJobPub just as a *PoC*.

docs/project.md

@@ -6,29 +6,29 @@ To establish a JSON schema as a standard format for publishing vacancies we foll
 
 First, we need to decide who will be in charge of maintaining the standard. This could be a non-profit organization, a consortium of industry players, or an open-source community. A clear governance model ensures the standard evolves transparently and in a way that benefits everyone.
 
-* **Create a Core Team:** Assemble a small group of stakeholders, including recruiters, developers, and job board operators, to guide the initial development.
-* **Establish a Decision-Making Process:** Determine how changes to the schema will be proposed, discussed, and approved. This could be a formal voting process or a consensus-based approach.
+- [ ] **Create a Core Team:** Assemble a small group of stakeholders, including recruiters, developers, and job board operators, to guide the initial development.
+- [ ] **Establish a Decision-Making Process:** Determine how changes to the schema will be proposed, discussed, and approved. This could be a formal voting process or a consensus-based approach.
 
 ## 2. **Build a Community**
 
 A standard is only useful if it's widely adopted. This requires active engagement with the community.
 
-* **Publish the Schema:** Make the schema publicly available on a platform like GitHub. Use a versioning system (e.g., `v1`, `v2`) to manage changes.
-* **Create Documentation:** Write clear and comprehensive documentation. Explain what each field is for, provide examples, and offer guidance on how to implement the schema.
-* **Launch a Website or Forum:** Create a dedicated space for discussion, bug reports, and feature requests. This is where you'll gather feedback and build momentum.
-* **Engage with Key Stakeholders:** Reach out to stakeholders. Show them the benefits of the standard and encourage them to participate.
+- [x] **Publish the Schema:** Make the schema publicly available on a platform like GitHub. Use a versioning system (e.g., `v1`, `v2`) to manage changes.
+- [x] **Create Documentation:** Write clear and comprehensive documentation. Explain what each field is for, provide examples, and offer guidance on how to implement the schema.
+- [x] **Launch a Website or Forum:** Create a dedicated space for discussion, bug reports, and feature requests. This is where you'll gather feedback and build momentum.
+- [ ] **Engage with Key Stakeholders:** Reach out to stakeholders. Show them the benefits of the standard and encourage them to participate.
 
 ## 3. **Formalize the Standard**
 
 Once the schema is mature and has received sufficient community feedback, you can pursue formal recognition.
 
-* **Write a Specification:** Turn the schema and its documentation into a formal specification document. This should include a detailed description of every field, data types, and any business rules.
+- [ ] **Write a Specification:** Turn the schema and its documentation into a formal specification document. This should include a detailed description of every field, data types, and any business rules.
 
 ## 4. **Promote Adoption and Provide Tools**
 
 Promotion is key to making the standard a success.
 
-* **Develop Client Libraries:** Create official libraries in popular programming languages (e.g., Python, JavaScript) to make it easy for developers to use the schema.
-* **Build Validation Tools:** Offer a free online tool where anyone can paste their JSON and validate it against the schema. This helps catch errors and encourages correct usage.
-* **Showcase Success Stories:** As companies start to adopt the standard, highlight their success. This provides social proof and demonstrates the real-world value of the format.
-* **Maintain and Iterate:** Continue to solicit feedback and release new versions of the schema as the industry evolves.
+- [ ] **Develop Client Libraries:** Create official libraries in popular programming languages (e.g., Python, JavaScript) to make it easy for developers to use the schema.
+- [x] **Build Validation Tools:** Offer a free online tool where anyone can paste their JSON and validate it against the schema. This helps catch errors and encourages correct usage.
+- [ ] **Showcase Success Stories:** As companies start to adopt the standard, highlight their success. This provides social proof and demonstrates the real-world value of the format.
+- [ ] **Maintain and Iterate:** Continue to solicit feedback and release new versions of the schema as the industry evolves.

docs/why.md

@@ -10,7 +10,7 @@ Let's look at three topics regarding job postings:
 
 Publishing and finding jobs is a huge market. Nowadays there are **hundrets or thousands** of job portals, job boards and career platforms world wide. 
 
-An estimated **34.4 USD billion** is spent annually on online job advertisements. This figure for 2023 underscores the immense importance of online job boards and career platforms in modern human resources management. The market for online job ads is a central component of the global recruiting industry. These figures come from Staffing Industry Analysts (SIA), a leading analysis firm in the field of human resources management.
+An estimated **USD 34.4 billion** is spent annually on online job advertisements. This figure for 2023 underscores the immense importance of online job boards and career platforms in modern human resources management. The market for online job ads is a central component of the global recruiting industry. These figures come from Staffing Industry Analysts (SIA), a leading analysis firm in the field of human resources management.
 
 Needless to say, job portals typically **charge employers regardless** of whether they fill the position or not. 
 

mkdocs.yml

@@ -1,4 +1,9 @@
 site_name: "oJobPub - Open Job Publishing Initiative"
+site_description: "oJobPub is a community-driven effort to create an open standard for publishing job listings in a structured format, making it easier for job seekers and employers to connect."
+site_url: https://www.ojobpub.org/
+
+repo_url: https://github.com/ojobpub/docs
+edit_uri: edit/main/docs/
 
 nav:
   - Intro: index.md
@@ -11,6 +16,11 @@ nav:
   - About: project.md
 
 theme:
+  name: material
+  features:
+    - navigation.tabs
+    - content.action.edit
+    - content.action.view
   font: false
   logo: static/logo.png
   palette:
@@ -32,9 +42,7 @@ theme:
       toggle:
         icon: material/brightness-4
         name: Switch to light mode
-  name: material
-  features:
-    - navigation.tabs
+
 
 markdown_extensions:
   - pymdownx.highlight: