diff --git a/assets/bootstrap.js b/assets/bootstrap.js new file mode 100644 index 0000000..2ea01c0 --- /dev/null +++ b/assets/bootstrap.js @@ -0,0 +1,4 @@ +import Collapse from './vendor/bootstrap/js/src/collapse.js' + +window.bootstrap = window.bootstrap || {} +window.bootstrap.Collapse = Collapse diff --git a/assets/main.scss b/assets/main.scss index 9b1eed4..d4dde7d 100644 --- a/assets/main.scss +++ b/assets/main.scss @@ -32,7 +32,7 @@ $primary: #000; // @import "../vendor/bootstrap/scss/breadcrumb"; // @import "../vendor/bootstrap/scss/pagination"; @import "../vendor/bootstrap/scss/badge"; -// @import "../vendor/bootstrap/scss/alert"; +@import "../vendor/bootstrap/scss/alert"; // @import "../vendor/bootstrap/scss/progress"; // @import "../vendor/bootstrap/scss/list-group"; // @import "../vendor/bootstrap/scss/close"; @@ -85,3 +85,9 @@ $bootstrap-icons-font-dir: "./"; box-shadow: 0 12px 24px rgba(0, 0, 0, 0.15) !important; } } + +.highlight pre { + background: transparent !important; + @extend .mb-0; + @extend .p-4; +} diff --git a/config/_default/config.toml b/config/_default/config.toml index 242dd1d..84d5836 100644 --- a/config/_default/config.toml +++ b/config/_default/config.toml @@ -6,3 +6,15 @@ staticDir = [ './vendor/bootstrap-icons/font/fonts', './static' ] description = 'The JSON Schema Registry. Enterprise-grade, high-performance, and self-hosted' github = 'https://github.com/sourcemeta' email = 'hello@sourcemeta.com' + +[markup] + [markup.highlight] + style = 'swapoff' + +[[module.mounts]] +source = "assets" +target = "assets" + +[[module.mounts]] +source = "vendor/bootstrap/js" +target = "assets/vendor/bootstrap/js" diff --git a/content/_index.html b/content/_index.html index f4e8d54..f17db7c 100644 --- a/content/_index.html +++ b/content/_index.html @@ -1,5 +1,26 @@ +++ 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" +++ {{< blueprint color="white" class="border-top pt-4 pt-md-5 pb-3" >}} @@ -80,31 +101,7 @@
- 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 -
-
- 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.
- - -A standard library of all the foundational schemas you'll ever need—from email addresses to currency codes—so you never have to bother with JSON Schema again
+ + + + ++ Commercial library with perpetual pricing. Pay once, own forever +
+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.
+Your company is smarter than that
+And you are probably not even unit testing your schemas for correctness
+ {{< /box >}} +And you might even be introducing security vulnerabilities with overly loose schemas
+ {{< /box >}} +Why waste your time designing complex schemas that have already been designed?
+ {{< /box >}} +We don't lock you in. Choose the method that works best for your workflow
+
+ 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
+ Most popular OpenAPI editors, such as Scalar, can de-reference external HTTPS requests to schemas hosted in public schema registries like schemas.sourcemeta.com
+
+ 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
+
+ For extra power and organisation-wide API Governance programs, ingest the schemas in JSON Schema 2020-12 compatible registries like the Sourcemeta Registry
+
+ 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
+
+ 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
+All schemas are publicly available on GitHub for evaluation, auditing, and contributions. However, any use of these schemas related to a for-profit product or service requires a commercial license. Read the license document for more details.
+ +Do you have questions regarding the license? Don't hesitate to reach out!
+ +Free forever for non-commercial projects such as personal projects, open specifications, research, and open-source organisations.
+Note: Requires attribution
+ View on GitHub +Offer our schemas to your end users as part of your own product (i.e. OpenAPI editors and API management platforms) in a white-labelling manner and without attribution
+ Let's Talk! +One-time payment
+ +Contact us for a full refund within 30-days of purchase. No questions asked
+This library is maintained by a member of the JSON Schema Technical Steering Committee. Your purchase directly supports our open-source contributions and continuous involvement in the JSON Schema ecosystem. Thanks for your help making the JSON Schema standard thrive!
+Solve the OpenAPI authoring problem for your company forever
+A fraction of the time and cost to produce these schemas yourself
+Every project, every team, forever. Including all new schemas
+Have an API and JSON Schema expert on your speed dial for help
+Avoid a whole class of input/output correctness and security bugs
+See what the world's leading specification experts are saying
+Do you have any other questions regarding the schemas? Don't hesitate to reach out!
+ +Yes. However, if your API is for-profit, you'll need a commercial license. Your end users can freely consume your published OpenAPI specification without needing their own license, as they're using your specification rather than directly consuming our schemas.
+Absolutely. These schemas are designed as composable building blocks. Reference them, extend them, or add additional constraints as you wish.
+All schemas target JSON Schema 2020-12, which is the dialect used by OpenAPI v3.1 and later. Support for earlier JSON Schema dialects will be added in future releases.
+We regularly update schemas to reflect new standards, fix bugs, and expand coverage for additional specifications. We follow semantic versioning, so you can upgrade at your own pace without breaking existing specifications.
+Yes. We welcome contributions via pull requests on GitHub.
+Yes, as long as you preserve the license-related metadata keywords that identify the schema origin and licensing terms for downstream consumers.
+Yes. This qualifies under the Community license. Users of your specification can freely use the schemas as they are consuming your specification rather than our schemas directly.
+Yes. A commercial license is required for any for-profit venture, regardless of whether your code is open-source.
+If you use the schemas unmodified, the embedded metadata provides automatic attribution. No additional action is required.
+One payment. Perpetual access. Never write schemas from scratch again.
+ + + + + + 30-day money-back guarantee • Maintained by a JSON Schema TSC member + +