diff --git a/config/_default/config.toml b/config/_default/config.toml index 84d5836..624badf 100644 --- a/config/_default/config.toml +++ b/config/_default/config.toml @@ -3,9 +3,7 @@ title = 'Sourcemeta' staticDir = [ './vendor/bootstrap-icons/font/fonts', './static' ] [Params] -description = 'The JSON Schema Registry. Enterprise-grade, high-performance, and self-hosted' -github = 'https://github.com/sourcemeta' -email = 'hello@sourcemeta.com' +description = 'A growing library of battle-tested JSON Schemas implementing standards from ISO, IETF, IEC, W3C, XBRL, and more. Ready to plug into your OpenAPI specs and API Gateways' [markup] [markup.highlight] diff --git a/content/_index.html b/content/_index.html index c26cc14..39938cf 100644 --- a/content/_index.html +++ b/content/_index.html @@ -1,64 +1,255 @@ +++ title = "Home" -github = "sourcemeta/registry" - -[[navigation]] -title = "Docs" -link = "https://registry.sourcemeta.com" - -[[navigation]] -title = "Features" -link = "#features" - -[[navigation]] -title = "Pricing" -link = "#pricing" - -[[navigation]] -title = "Open Source" -link = "#opensource" - -[[navigation]] -title = "Support" -link = "https://github.com/sourcemeta/registry/discussions" +aliases = ["/products/std"] +++ {{< blueprint color="white" class="border-top pt-4 pt-md-5 pb-3" >}}
Blaze: Compiling JSON Schema for 10x Faster Validation. Read our paper
-

The JSON Schema Registry

-

The JSON Schema Registry

+

Accelerate Your XML-to-JSON Modernisation Initiative

+

Accelerate Your XML-to-JSON Modernisation Initiative

- Enterprise-grade | High-performance | Self-hosted + For Regulatory Industries | Fully Standards Compliant | Premium Support

-

- Enterprise-grade | High-performance | Self-hosted +

+ For Regulatory Industries | Fully Standards Compliant | Premium Support

-

JSON Schema is at the core of your governance program, but working with it shouldn't be a headache. Our self-hosted registry eliminates the complexity of operating schemas at scale. Led by a member of the JSON Schema Technical Steering Committee.

+

A growing library of battle-tested JSON Schemas implementing standards from ISO, IETF, IEC, W3C, XBRL, and more. Ready to plug into your OpenAPI specs and API Gateways. Eliminate years of schema development, ongoing maintenance, and the regulatory risks of implementing standards yourself.

+ +

Led by a member of the JSON Schema Technical Steering Committee

-
- - View on GitHub - - Explore a live instance +
+ + Schedule Consultation + + Explore Schemas
- + The Sourcemeta JSON Schema Registry {{< /blueprint >}} -{{< components/ribbon >}} +
+
+
+
+

Expertly Implemented Standards

+

Each schema represents careful implementation of the standards that power modern infrastructure (which often cost thousands to access). Your APIs get proven, compliant foundations without the burden of interpreting complex specifications or maintaining the schemas yourself.

+
+
+
+
+ + IETF + + + ISO + + + IEEE + +
+
+ + IEC + + + W3C + + + XBRL + +
+
+
+
+
+
+ +
+
+
+

Regulated Industries Can't Afford Schema Implementation Risk

+

Eliminate compliance exposure, implementation complexity, and maintenance burden

+
+
+
+ {{< box header="Regulatory Risk" icon="bi-arrow-repeat" title="Schema errors become regulatory violations" >}} + In regulated industries, validation failures aren't technical bugs; they're compliance breaches. When schemas accept malformed data or fail to enforce constraints, you're exposed to regulatory penalties and audit failures. Hand-crafted schemas rarely capture every edge case that auditors scrutinise. + {{< /box >}} +
+
+ {{< box header="Implementation Burden" icon="bi-toggles" title="Industry standards often exist only in XML" >}} + Many standards provide XML schemas, but often JSON implementations are non-existent or poorly documented. Translating XML Schema to JSON Schema requires deep dual-format expertise and significant time investment. Most organisations can't do it or burn extraordinary resources trying. + {{< /box >}} +
+
+ {{< box header="Ongoing Maintenance" icon="bi-hourglass-split" title="Standards evolve, and your schemas must too" >}} + Industry standards release updates. Regulations change. JSON Schema and OpenAPI change too. Maintaining schema accuracy isn't a one-time project; it's perpetual expert work. We track updates, maintain backward compatibility, and ensure your schemas stay compliant as regulations evolve. + {{< /box >}} +
+
+
+
+ +
+
+
+

Pricing

+

Sourcemeta is led by Juan Cruz Viotti, a member of the Technical Steering Committee that defines and maintains the JSON Schema specification itself. You are not buying interpretation, but definitive expertise from the source. This level of implementation quality and support simply doesn't exist elsewhere.

+
+
+
+
+
+

Community

+
+
+

Free

+
    +
  • Full access
    • +
  • Commercial evaluation
    • +
  • Non-commercial use
    • +
  • Open-source projects
    • +
  • Research and education
    • +
+ + + Explore on GitHub +
+
+
+
+
+
+

Enterprise

+
+
+

Custom Pricing

+

Tailored to your organisation's size, compliance requirements, and support needs

+
    +
  • Commercial Licensing
    • +
  • Production deployment rights
    • +
  • Company-wise usage
    • +
  • Custom licensing terms
    • + +
  • Enterprise Support
    • +
  • Direct access to JSON Schema TSC member
    • +
  • Priority technical support
    • +
  • Assisted onboarding and integration
    • + +
  • Optional Add-Ons
    • +
  • Custom schema development
    • +
  • On-demand schema training
    • +
  • Self-hosted or managed schema registry
    • +
  • High-performance schema validation (Blaze)
    • +
+ Schedule Consultation +
+
+
+
+
+
+ +
+
+
+

What's the Alternative?

+

This is not about $ref. It's about having the in-house talent and correctly implementing dozens of specifications, reading paywalled standards, handling edge cases, keeping up with updates, and obsessively guaranteeing compliance.

+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Do it yourself + + With ChatGPT + + Ignore the problem + + With Sourcemeta Sourcemeta +
Reading Specifications€30,000
(375 hours)		Hope ChatGPT was illegaly trained with the potentially copyrighted standardsNot needed Done for you
Implementation & Testing€60,000
(750 hours)		Ask ChatGPTBasic type checks everywhere Hundreds of schemas ready and more coming
Annual Maintenance€20,000/year
(250 hours)		Ask ChatGPT againNone (as you are barely validating) Done for you
Standards Compliance If done correctly No guarantees No compliance at all Guaranteed
Security Risks Low (if done correctly)Data breach: €50K-500K+
GDPR: €20M or 4% revenue		Security incident: €100K+ Battle-tested
SupportYour team's problemYour team's problemYour team's problem Premium support by a member of the JSON Schema Technical Steering Committee
Total First Year€110,000+
Assuming you managed to hire a JSON Schema expert		€0 → Catastrophic Risk€0 → High RiskROI in the first month
+
+ +

Cost calculations assume a mid-level developer at €80/hour (conservative industry average)

+ + {{< talk-to-us >}} +
+
+ +

- Great organisations rely on our tooling + Industry leaders rely on our tooling

-{{< /components/ribbon >}} - -{{< promotion >}} - -
-
-

Designed to solve schema management at scale

-

We live and breathe JSON Schema—as expert consultants, - book authors, - award-winning researchers, and open-source maintainers. This isn't just another registry; It's the result of - years of insights operating JSON Schema in production.

- -
-
- {{}} - - Browse, search, and dereference your collections of schemas, even across multiple GitHub repositories, from a single place - - {{}} -
-
- {{}} - - Stop reinventing the wheel. We ship hand picked industry standard ontologies that you can plug into your API specifications right away - - {{}} -
-
- -
-
- {{}} - - Dependency-free (not even a database), stateless, horizontally-scalable, and customisable with a simple JSON configuration file - - {{}} -
-
- {{}} - - Written in C++ and powered by Blaze, the world's fastest JSON Schema validator, proven by research to be at least 10x faster that alternatives +
- {{}} +
+
+
+
+ {{< testimonial github="ronitelman" name="Ron Itelman" role="O'Reilly Author" >}}This is definitely going to become an incredibly important reference library for defining concepts using best in class standards{{< /testimonial >}}
-
- -
-
- {{}} - Forget about JSON Schema drafts and dialects. Use the version you know and let us convert to any target your tooling demands, on the fly - - {{}} +
+ {{< testimonial github="mwadams" name="Matthew Adams" role="JSON Schema TSC" >}}This is a terrific project and should be a standard subscription for any enterprise working with JSON Schema{{< /testimonial >}}
-
- {{}} - - Level up your API Governance program with ever-evolving statistics to flag anti-patterns, invalid schemas, overly loose schemas, and more - {{}} +
+ {{< testimonial github="paraskakis" name="Emmanuel Paraskakis" role="Founder at Level 250" >}}This aligns exactly with my thinking! OpenAPI should not include schemas but should reference them externally from a source of truth like this one{{< /testimonial >}}
-
- -
-
- {{}} - Visually explore schema evaluation (like a step-through code debugger) to troubleshoot tricky schema issues without losing your sanity - - {{}} +
+ {{< testimonial github="ikenna" name="Ikenna Nwaiwu" role="API Governance Consultant at Ikenna Consulting" >}}Before this library, defining foundational schemas in an enterprise was a time-consuming, error-prone task that could result in inconsistencies. This library is a game-changer, delivering huge time savings while ensuring improved API consistency and strong governance of API definition files{{< /testimonial >}}
-
- {{}} - - Deploy as an internal micro-service that serves the JSON Schema needs (linting, validation, debugging, etc) of your own commercial offerings - {{}} +
+ {{< testimonial github="egekorkan" name="Ege Korkan" role="W3C Web of Things Expert" >}}Right now there is a big disconnect between ontology work and API work. This project has the potential to bridge that gap by making widely used ontologies available on JSON Schema{{< /testimonial >}}
- - {{< talk-to-us >}}
-
-
-
-
- -
In our experience, the average API company wastes at least $200k per year on simple schema related problems
-
    -
  • Over 75% of API developers make use of JSON Schema
    • -
  • Over 90% of those developers waste time with substandard schema tooling
    • -
  • Over 80% of those developers get stuck when writing non-trivial schemas
    • -
- -
-
- - Kin Lane - -

- JSON Schema is ubiquitous and critical to our operations, yet so many of us have barely scratched the surface - when it comes to putting the specific to work, let alone getting our house in order -

-
-
- Kin Lane, The API Evangelist -
-
- -
-
- - JSON Schema holds the lead in API specifications according to the Postmant State of the API report +
+
+
+
+ + JSON Schema for OpenAPI course +
+
+ +
+
- Source: Postman's State of the API Report +
+
+
+
+

+ + Build in-house JSON Schema expertise

+

On-demand training: Master JSON Schema for OpenAPI

+

Learn advanced patterns, schema-first design, and production-grade techniques from a member of the JSON Schema Technical Steering Committee. 14 modules and over 9 hours of content covering the entirety of JSON Schema 2020-12, from basics all the way to dynamic references.

+ Buy the Video Course +
+
-
-
-

Pricing

- -

Deploy the Sourcemeta JSON Schema Registry for free (all features included) for evaluation, personal, open-source, or non-commercial purposes. For commercial deployments, you must purchase a license. All editions are available on GitHub for auditing purposes and contributions.

+
+
+

Open Source

-

We are committed to building nothing less than the highest quality JSON Schema tooling in the market. As a lean bootstrapped company, our revenue allow us to invest an immense amount of effort to perfect our foundational technology, all the way to our custom JSON parser and record-breaking JSON Schema validator.

+

We maintain critical open-source projects for the JSON Schema ecosystem. Explore the full suite on GitHub.

-
-
-
-
Community
-
-

Free

-
    -
  • All features included
    • -
  • For commercial evaluation, open-source projects (not affiliated with a for-profit company), research, non-profit organisations, and personal use
    • -
- Get Started -
-
+
+
+ Learn JSON Schema + + Screenshot of the Learn JSON Schema website +
-
-
-
Enterprise
-
-

Custom

-
    -
  • All features included
    • -
  • Premium support
    • -
  • Assisted onboarding
    • -
  • Free updates
    • -
  • Custom invoicing
    • -
  • Add-ons
    • -
  • Managed hosting
    • -
  • Custom schema design
    • -
- Contact Us -
-
+ +
+ JSON Schema CLI + + Screenshot of the JSON Schema CLI in action +
+ diff --git a/content/api.webp b/content/api.webp deleted file mode 100644 index af9a9dd..0000000 Binary files a/content/api.webp and /dev/null differ diff --git a/content/discoverability.webp b/content/discoverability.webp deleted file mode 100644 index 650f927..0000000 Binary files a/content/discoverability.webp and /dev/null differ diff --git a/content/gitops.webp b/content/gitops.webp deleted file mode 100644 index e280b84..0000000 Binary files a/content/gitops.webp and /dev/null differ diff --git a/content/health.webp b/content/health.webp deleted file mode 100644 index 9ba6d18..0000000 Binary files a/content/health.webp and /dev/null differ diff --git a/content/hero.svg b/content/hero.svg deleted file mode 100644 index e211cea..0000000 --- a/content/hero.svg +++ /dev/null @@ -1,56 +0,0 @@ - - - hero - - - - - - - - - - - - - - - - - - Push schemas - - - Intelligence.AI - Schema Registry - - - Generate schema - documentation - - - Serve editor - autocompletion - - - Reference schemas - - - - - - - - - - - - - - - On the fly schema - upgrades - - - - \ No newline at end of file diff --git a/content/products/std/iec.svg b/content/iec.svg similarity index 100% rename from content/products/std/iec.svg rename to content/iec.svg diff --git a/content/products/std/ieee.svg b/content/ieee.svg similarity index 100% rename from content/products/std/ieee.svg rename to content/ieee.svg diff --git a/content/products/std/ietf.svg b/content/ietf.svg similarity index 100% rename from content/products/std/ietf.svg rename to content/ietf.svg diff --git a/content/products/std/iso.svg b/content/iso.svg similarity index 100% rename from content/products/std/iso.svg rename to content/iso.svg diff --git a/content/kinlane.jpeg b/content/kinlane.jpeg deleted file mode 100644 index 4bd786f..0000000 Binary files a/content/kinlane.jpeg and /dev/null differ diff --git a/content/performance.webp b/content/performance.webp deleted file mode 100644 index 66e2254..0000000 Binary files a/content/performance.webp and /dev/null differ diff --git a/content/postman-jsonschema.webp b/content/postman-jsonschema.webp deleted file mode 100644 index 00b54fd..0000000 Binary files a/content/postman-jsonschema.webp and /dev/null differ diff --git a/content/products/_index.html b/content/products/_index.html deleted file mode 100644 index 4e0ce95..0000000 --- a/content/products/_index.html +++ /dev/null @@ -1,3 +0,0 @@ -+++ -title = "Products" -+++ diff --git a/content/products/std/_index.html b/content/products/std/_index.html deleted file mode 100644 index eb48c99..0000000 --- a/content/products/std/_index.html +++ /dev/null @@ -1,732 +0,0 @@ -+++ -title = "JSON Schema Standard Library" -description = "A standard library of all the foundational schemas you'll ever need so you never have to bother with JSON Schema again" -github = "sourcemeta/std" - -[[navigation]] -title = "Browse Schemas" -link = "https://schemas.sourcemeta.com/sourcemeta/std" - -[[navigation]] -title = "Pricing" -link = "#pricing" - -[[navigation]] -title = "Open Source" -link = "#opensource" -+++ - -{{< blueprint color="white" class="border-top pt-4 pt-md-5 pb-5" >}} -
-

- Design OpenAPI Specs
That Actually Validate Correctly_ -

-

- Design OpenAPI Specs
That Actually Validate Correctly_ -

- - - -

A growing collection of over +300 battle-tested schemas (ISO, IETF, IEC, W3C, etc) to power your next API spec, so you never have to bother with JSON Schema again

- -
- - Get Started - - - - Browse Schemas - -
- -
- Maintained by a member of the JSON Schema Technical Steering Committee -
-
- -
-

What's Inside: Some Sample Schemas from the Library

-

- Hint: Your OpenAPI specs in YAML format can directly reference these schemas in JSON format using $ref -

- - - -
- -
-
-
-
-
-
- jsonrpc/v2.0/request.json -
- - -
- - - - - - Browse All 300+ Schemas - -
- - -
-
- 
1
- 
Loading schema...
-
-
- - -
-
- - About This Schema - -
-
-
- - Implements the official JSON-RPC 2.0 specification for remote procedure calls -
-
- - Validates request structure, method names, and parameter formats -
-
- - Used by thousands of APIs for standardized RPC communication -
-
-
-
- - -
-{{< /blueprint >}} - -
-
-
-
-

Built on the foundations of our digital world

-

Every schema in this library represents careful implementation of the standards that power the modern internet (many behind expensive paywalls), ensuring your APIs are built on proven, battle-tested, and compliant foundations.

-
-
-
-
- - IETF - - - ISO - - - IEEE - -
-
- - IEC - - - W3C - - - XBRL - -
-
-
-
-
-
- -
-
-
-

Most API companies waste years reinventing the wheel, and still do it wrong

-

Your company is smarter than that

-
- -
-
- {{< box header="Correctness" icon="bi-arrow-repeat" title="Your schemas are broken and you don't know it" >}} - We worked with dozens of API companies, and less than 4% of developers unit tests their OpenAPI schemas. Unsurprisingly, they had subtle schema bugs that you can avoid. - {{< /box >}} -
-
- {{< box header="Compliance" icon="bi-toggles" title="All of those standards exist for a reason" >}} - Take country codes. Too strict? You reject less-known countries. Too loose? You introduce compliance issues, and accept SQL injection attacks and other vulnerabilities. We take the risk out. - {{< /box >}} -
-
- {{< box header="Productivity" icon="bi-hourglass-split" title="Writing schemas yourself is expensive" >}} - Just the ISO 8601 date and time specification is 50+ pages long and costs around $500 USD. We implemented it in 115 variants covered by 6000 edge cases. And that's a single data type. - {{< /box >}} -
-
-
-
- -
-
-
-

Use the schemas your way

-

We don't lock you in. Choose the method that works best for your workflow

-
- -
-
-
-
- HTTPS URLs -
-

HTTPS URLs

-

Directly reference schemas from schemas.sourcemeta.com using the $ref JSON Schema keyword and de-reference them with well known OpenAPI tools like redocly bundle

-
-
-
-
-
- OpenAPI Editors -
-

OpenAPI Editors

-

Most popular OpenAPI editors, such as Scalar, can de-reference external HTTPS requests to schemas hosted in public schema registries like schemas.sourcemeta.com

-
-
-
-
-
- Git Submodule -
-

Git Submodule

-

Our schemas are publicly available on GitHub. Pull them as a submodule like any other dependency and reference them from your OpenAPI specs using relative file paths

-
-
-
-
-
- Schema Registries -
-

Schema Registries

-

For extra power and organisation-wide API Governance programs, ingest the schemas in JSON Schema 2020-12 compatible registries like the Sourcemeta Registry

-
-
-
-
-
- Download Archive -
-

Download Archive

-

Often useful in scripting environments. Fetch the latest ZIP or tarball from GitHub Releases and use the JSON files that come with it as you wish

-
-
-
-
-
- Copy & Paste -
-

Copy & Paste

-

Sometimes you don't need to get fancy. You can always browse the schemas in schemas.sourcemeta.com and just copy-paste the ones you need

-
-
-
-
-
- -
-
-

Pricing

- -

This library is maintained by a member of the JSON Schema Technical Steering Committee, ensuring top quality compared to other vendors. Your purchase directly supports our open-source contributions and continuous involvement in the JSON Schema ecosystem.

- -
-
-
-
-
-

Community

-
-
-

Free

-

Requires attribution

- -

Free forever for non-commercial projects such as personal projects, open specifications, research, and open-source organisations.

- -
- View on GitHub -
-
-
-
-
-
-
-
-
-

Enterprise

-
-
-

Custom

-

Startup discounts available

- -
    -
  • Onboarding assistance
    • -
  • Premium support (Slack Connect or Discord)
    • -
  • Request any new schemas you need
    • -
  • Custom schema design on request
    • -
  • Custom training on request
    • -
  • OEM redistribution on request
    • -
- -
- Contact Us -
-
-
-
-
-
- -

Read the license document for more details. If you have questions , don't hesitate to reach out!

-
-
- -
-
-
-

What's the Alternative?

-

This is not about $ref. It's about having the in-house talent and correctly implementing dozens of specifications, reading paywalled standards, handling edge cases, keeping up with updates, and obsessively guaranteeing compliance.

-
- -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Do it yourself - - With ChatGPT - - Ignore the problem - - With Sourcemeta Sourcemeta -
Reading Specifications€30,000
(375 hours)		Hope ChatGPT was illegaly trained with the potentially copyrighted standardsNot needed Done for you
Implementation & Testing€60,000
(750 hours)		Ask ChatGPTBasic type checks everywhere Hundreds of schemas ready and more coming
Annual Maintenance€20,000/year
(250 hours)		Ask ChatGPT againNone (as you are barely validating) Done for you
Standards Compliance If done correctly No guarantees No compliance at all Guaranteed
Security Risks Low (if done correctly)Data breach: €50K-500K+
GDPR: €20M or 4% revenue		Security incident: €100K+ Battle-tested
SupportYour team's problemYour team's problemYour team's problem Premium support by a member of the JSON Schema Technical Steering Committee
Total First Year€110,000+
Assuming you managed to hire a JSON Schema expert		€0 → Catastrophic Risk€0 → High RiskROI in the first month
-
- -

Cost calculations assume a mid-level developer at €80/hour (conservative industry average)

- - {{< talk-to-us >}} -
-
- -
-
-
-

Trusted by elite API architects

-

See what the world's leading specification experts are saying

-
- -
-
- {{< testimonial github="ronitelman" name="Ron Itelman" role="Founder at TrustLoop.ai" >}}This is definitely going to become an incredibly important reference library for defining concepts using best in class standards{{< /testimonial >}} -
- -
- {{< testimonial github="mwadams" name="Matthew Adams" role="Founder at Endjin Limited" >}}This is a terrific project and should be a standard subscription for any enterprise working with JSON Schema{{< /testimonial >}} -
- -
- {{< testimonial github="paraskakis" name="Emmanuel Paraskakis" role="Founder at Level 250" >}}This aligns exactly with my thinking! OpenAPI should not include schemas but should reference them externally from a source of truth like this one{{< /testimonial >}} -
- -
- {{< testimonial github="ikenna" name="Ikenna Nwaiwu" role="API Governance Consultant at Ikenna Consulting" >}}Before this library, defining foundational schemas in an enterprise was a time-consuming, error-prone task that could result in inconsistencies. This library is a game-changer, delivering huge time savings while ensuring improved API consistency and strong governance of API definition files{{< /testimonial >}} -
- -
- {{< testimonial github="egekorkan" name="Ege Korkan" role="W3C Web of Things Expert" >}}Right now there is a big disconnect between ontology work and API work. This project has the potential to bridge that gap by making widely used ontologies available on JSON Schema{{< /testimonial >}} -
-
-
-
diff --git a/content/products/std/from-copypaste.png b/content/products/std/from-copypaste.png deleted file mode 100644 index 85c5d46..0000000 Binary files a/content/products/std/from-copypaste.png and /dev/null differ diff --git a/content/products/std/from-editors.png b/content/products/std/from-editors.png deleted file mode 100644 index 679a2e1..0000000 Binary files a/content/products/std/from-editors.png and /dev/null differ diff --git a/content/products/std/from-https.png b/content/products/std/from-https.png deleted file mode 100644 index 3193f34..0000000 Binary files a/content/products/std/from-https.png and /dev/null differ diff --git a/content/products/std/from-registry.png b/content/products/std/from-registry.png deleted file mode 100644 index f092a30..0000000 Binary files a/content/products/std/from-registry.png and /dev/null differ diff --git a/content/products/std/from-submodule.png b/content/products/std/from-submodule.png deleted file mode 100644 index fa744b1..0000000 Binary files a/content/products/std/from-submodule.png and /dev/null differ diff --git a/content/products/std/from-zip.png b/content/products/std/from-zip.png deleted file mode 100644 index 09529e5..0000000 Binary files a/content/products/std/from-zip.png and /dev/null differ diff --git a/content/reusability.webp b/content/reusability.webp deleted file mode 100644 index e5718cc..0000000 Binary files a/content/reusability.webp and /dev/null differ diff --git a/content/screenshot.webp b/content/screenshot.webp index a05fb49..1436c2d 100644 Binary files a/content/screenshot.webp and b/content/screenshot.webp differ diff --git a/content/products/std/w3c.svg b/content/w3c.svg similarity index 100% rename from content/products/std/w3c.svg rename to content/w3c.svg diff --git a/content/products/std/xbrl.svg b/content/xbrl.svg similarity index 100% rename from content/products/std/xbrl.svg rename to content/xbrl.svg diff --git a/layouts/index.html b/layouts/index.html index f9ed69f..c9753ad 100644 --- a/layouts/index.html +++ b/layouts/index.html @@ -3,5 +3,4 @@ {{ .Content }} -{{ partial "opensource.html" . }} {{ end }} diff --git a/layouts/partials/navigation.html b/layouts/partials/navigation.html index b98ae06..bf043ae 100644 --- a/layouts/partials/navigation.html +++ b/layouts/partials/navigation.html @@ -7,16 +7,26 @@
diff --git a/layouts/products/list.html b/layouts/products/list.html deleted file mode 100644 index b8b32d5..0000000 --- a/layouts/products/list.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - {{ .Title | default .Site.Title }} - - - - - - - - - - - - - {{ $style := resources.Get "main.scss" | toCSS (dict "outputStyle" "compressed") }} - - - - - - - - - - {{ partial "navigation.html" . }} - -
- {{ .Content }} -
- - {{ partial "opensource.html" . }} - - {{ partial "footer.html" . }} - {{ $js := resources.Get "bootstrap.js" | js.Build (dict "minify" true) }} - - - diff --git a/layouts/shortcodes/editor.html b/layouts/shortcodes/editor.html deleted file mode 100644 index cc827cb..0000000 --- a/layouts/shortcodes/editor.html +++ /dev/null @@ -1,55 +0,0 @@ -{{- $filename := .Get "filename" -}} -{{- $type := .Get "type" -}} -{{- $language := .Get "language" -}} -{{- $details := split (.Get "details") "|" -}} -{{- $detailCount := len $details -}} - -{{- $bgGradient := "" -}} -{{- $iconColor := "" -}} -{{- $icon := "" -}} -{{- $panelTitle := "" -}} - -{{- if eq $type "fail" -}} - {{- $bgGradient = "linear-gradient(135deg, #3d0a0a 0%, #1e1e1e 100%)" -}} - {{- $iconColor = "text-danger" -}} - {{- $icon = "bi-exclamation-triangle-fill" -}} - {{- $panelTitle = "Problems" -}} -{{- else if eq $type "success" -}} - {{- $bgGradient = "linear-gradient(135deg, #0a3d1a 0%, #1e1e1e 100%)" -}} - {{- $iconColor = "text-success" -}} - {{- $icon = "bi-check-circle-fill" -}} - {{- $panelTitle = "Output" -}} -{{- end -}} - -{{- $highlighted := transform.Highlight .Inner $language "" -}} - -
-
-
-
-
-
-
- {{ $filename }} -
-
-
- {{ $highlighted | safeHTML }} -
-
-
-
- - {{ $panelTitle }} ({{ $detailCount }}) - -
-
- {{ range $index, $detail := $details }} -
- - {{ $detail }} -
- {{ end }} -
-
-
diff --git a/layouts/shortcodes/github-button.html b/layouts/shortcodes/github-button.html deleted file mode 100644 index 7f7e109..0000000 --- a/layouts/shortcodes/github-button.html +++ /dev/null @@ -1,2 +0,0 @@ - - View on GitHub diff --git a/layouts/shortcodes/lead.html b/layouts/shortcodes/lead.html index 37793ce..6b8def8 100644 --- a/layouts/shortcodes/lead.html +++ b/layouts/shortcodes/lead.html @@ -1 +1 @@ -

{{ .Inner }}

+

{{ .Inner }}

\ No newline at end of file diff --git a/layouts/shortcodes/promotion.html b/layouts/shortcodes/promotion.html deleted file mode 100644 index c3fcef7..0000000 --- a/layouts/shortcodes/promotion.html +++ /dev/null @@ -1,25 +0,0 @@ -
-
-
-
- - JSON Schema for OpenAPI course -
-
- -
-
- -
-
-
-
-

Master JSON Schema for OpenAPI

-

Learn advanced patterns, schema-first design, and production-grade techniques from a member of the JSON Schema Technical Steering Committee. 14 modules and over 9 hours of content covering the entirety of JSON Schema 2020-12, from basics all the way to dynamic references.

- Take the Video Course -
-
-
-
-
-
diff --git a/layouts/shortcodes/talk-to-us.html b/layouts/shortcodes/talk-to-us.html index 4ec12eb..85068c7 100644 --- a/layouts/shortcodes/talk-to-us.html +++ b/layouts/shortcodes/talk-to-us.html @@ -9,7 +9,7 @@
Do you have any questions?

I'm Juan Cruz Viotti, founder of Sourcemeta, member of the JSON Schema Technical Steering Committee, O'Reilly author, and award-winning University of Oxford alumnus.

I'd love to discuss how JSON Schema, OpenAPI, and Sourcemeta tooling can help you build world class APIs.

- +