Scalar: Generate interactive API documentations from Swagger files

Wow -- this is quite impressive. I&#x27;m delighted to see new offerings in this space. Kudos to the team! I spent some time tinkering with the deployed preview (<a href="https:&#x2F;&#x2F;docs.scalar.com" rel="nofollow noreferrer">https:&#x2F;&#x2F;docs.scalar.com</a>). I liked the thoughtful implementation around customizations &#x2F; versioning, etc.<p>Some places I hit friction while exploring: - It was tough to close the &quot;Test request&quot; window. - I wasn&#x27;t sure how to interact with the product without more trial and error.<p>Two suggestions I thought might be useful: 1. Add OpenAPI linting to the editor. Right now it works with invalid specs as long as long the JSON is formatted correctly. 2. Allow users to import an example spec from the initial Getting Started page. (The editor is a good home for it, too, but I would have found it sooner).<p>Disclosure: I&#x27;m a Redocly employee, but have managed doc projects in a variety of tools. This is a neat approach! Great work and congrats.

I&#x27;m interested in new offerings in this area, as all of the existing options are pretty janky. A couple of thoughts:<p>Operation.summary is typically derived from the documentation for an API operation, and should not be used as the operation title as it is far too long. Instead use the operationId and path.<p>I can&#x27;t get it to render schemas for a bunch of my OpenAPI documents, and there are no error messages to guide me. Does this handle recursive schemas (which can never be fully expanded)?

This so nice. Well done! I&#x27;ll surely give it a try. I appreciate the fresh theme in particular.<p>Nit: don&#x27;t call them Swagger files — OpenAPI has been around long enough to warrant recognition.

Some context for the less-informed (like myself):<p>&gt; The OpenAPI Specification, previously known as the Swagger Specification is a specification for a machine-readable interface definition language for describing, producing, consuming and visualizing web services.

Nice project. The space is crowded with many similar products. I couldn&#x27;t get any primary differentiators between it and similar products already mentioned in this thread<p>I prefer self-hosted or internally managed product only! However, what&#x27;s really hard to find is a solution that integrates with technical &amp; business documentation stacks. If anyone knows any good products please please please share...<p>I feel stuck using a frustrating product like Confluence and tried a few open source alternatives but couldn&#x27;t get conviction to switch (bad vs worse). We&#x27;ve been trying &#x27;swimm.io&#x27; but everybody has to go out of their way to incorporate it into their workflow, sooo nobody really using it! It doesn&#x27;t help that most of us use vim&#x2F;neovim and not IDEs ... majority of engineers don&#x27;t really like the documentation part of their work and most tools make it worse!

I think the perfect use-case for this would be to embed it in a application, kind of like GraphQL Playground. Not sure I&#x27;d use it for user-facing documentation though, as it seems it doesn&#x27;t have SSR or HTML output. Docusaurus Integration would be nice for that reason.

Aren&#x27;t Redocly and Swagger UI open-source too?

Hey HN, Marc co-founder &amp; CEO of scalar here!<p>Thanks so much for your thoughtful feedback and giving our first open sourced tool a try. Please don&#x27;t hesitate to reach out here or email me directly at marc@scalar.com if you have any feedback or if I can help you in any way shape or form with your API.

Awesome! I recently encountered the need of expanding a Spring Boot Admin instance to offer OpenAPI docs for custom Spring Boot Actuator endpoints which are in their own group, hidden from the main API. As SBA requires custom views to be Vue.js components, this will probably fit pretty nicely.

I’m having a lot trouble navigating it on Safari for iOS on iPad.<p>- The top bar disappears behind the navigation bar of Safari and there doesn’t seem to be a way to get it to reappear. - I tried to refresh the page to see if it would re-render and put the bar below the navigation bar, but I can’t pull down to refresh. Something is floating a window inside the window and I’m just pulling that around. - Tried clicking refresh in the nav bar and it didn’t fix the hidden top bar. - It’d be nice to be able to collapse the swagger editor in the reference view. Right now the left navigation is separated from the documentation and request tester on the right by 1&#x2F;3rd of the screen (that is not being used at all).

I like your project. Glad to see alternatives to this <a href="https:&#x2F;&#x2F;docusaurus-openapi.netlify.app&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;docusaurus-openapi.netlify.app&#x2F;</a>

Ooh this looks pretty sweet. Probably too new for me to convince my enterprise employer but will keep an eye on this for sure.

Isn&#x27;t swagger deprecated for like a decade? It looks like it supports OpenAPI, but interesting to focus on Swagger

Looks like a similar solution to <a href="https:&#x2F;&#x2F;github.com&#x2F;stoplightio&#x2F;elements">https:&#x2F;&#x2F;github.com&#x2F;stoplightio&#x2F;elements</a> - will give this a whirl some time!

Cool to see this.<p>I hate redocly and swagger UI , and all of &quot;enterprisey&quot; offering on an open standard like OpenAPI.

How does this differ from stoplight.io?<p>Is it just another theme (not that we can’t use another theme)?

Will &#x2F;token oauth bearer authentication be added anytime soon?

Why did you decide to open-source it? How will you make money?<p>edit: why downvotes?

The demo seems a little bit off-sync.

Looks very JavaScripty.<p>I like my API documentation to mainly be boring old static HTML, with any interactive features using JavaScript layered over the top.<p>Using HTML makes it faster to load, easier to get it indexed by search engines, easier to save and run offline and easier to process through LLM tools like ChatGPT and Claude.