Add dottxt case study

[rlouf]

This PR adds a case study with dottxt. I was invited to submit this PR by @jviotti. The illustrations are still missing.

[github-actions]

Hi @rlouf! Thanks a lot for your contribution!

I noticed that the following required information is missing or incomplete: issue reference, kind of change description

Please update the PR description to include this information. You can find placeholders in the PR template for these items.

Thanks a lot!

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
website	✅ Ready (View Log)	Visit Preview	4c2e321

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (463a579) to head (4c2e321).
⚠️ Report is 35 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #2007   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           30        30           
  Lines          672       672           
  Branches       211       211           
=========================================
  Hits           672       672           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[jviotti]

@Relequestual @jdesrosiers @gregsdennis @Honyii Any comments?

[gregsdennis]

I think the subject and content is great, however it could be reframed somewhat.

Currently it reads as .txt is the hero that is bridging the gap between LLMs and JSON Schema. Instead, what we're looking for is more along the lines of JSON Schema is the hero that allowed .txt to provide more reliable output from LLMs.

If the post could be reframed that way, I think we have a good candidate.

[jdesrosiers]

Interesting use of JSON Schema. I don't generally have much to say about case studies. I usually review these things mostly for technical accuracy with regard to JSON Schema concepts. I see no issues in that area.

[github-actions]

Hi @rlouf! Thanks a lot for your contribution!

I noticed that the following required information is missing or incomplete: issue reference, kind of change description

Please update the PR description to include this information. You can find placeholders in the PR template for these items.

Thanks a lot!

[github-actions]

Hi @rlouf! Thanks a lot for your contribution!

I noticed that the following required information is missing or incomplete: issue reference, kind of change description

Please update the PR description to include this information. You can find placeholders in the PR template for these items.

Thanks a lot!

[rlouf]

It took me a while to get around to updating the article, and I think that JSON Schema is now hero?

[jviotti]

Reads very well to me!

[jdesrosiers]

@gregsdennis Could you have a look when you have a chance and confirm that this is what you wanted to see.

[gregsdennis]

Yes, this is much better. Thank you for the reframe. Let's do it!

[jdesrosiers]

@json-schema-org/web-team Please merge when ready.

[github-actions]

Congratulations, @rlouf for your first pull request merge in this repository! 🎉🎉. Thanks for your contribution to JSON Schema!

[Utkarsh-123github]

Thanks @rlouf for your contribution.🚀