I'm considering of making the OpenAPI->API Reference converter an Open Source project, and then charging only if you need advanced features, like wysiwyg/inline editing, change approvals, automatic testing of the examples in the docs etc.
It's just that I'm not sure I can do it until I have these advanced features. If I can't make money out of this I have to return to my day job, and stop developing portal.dev.
Would it work for you if you could export this as a static website that you could run on your own servers? (you could do that in a Github action), or, alternatively, use some sort of React component that renders the API docs in your app?
Shameless plug: here's my indie-project that converts an OpenAPI/Swagger spec into something that aims to look like Stripe's API Reference:
https://portal.dev
At my previous workplace we've built the whole docs portal (including the API reference) as a custom static website with Contentful (a json CMS) underneath.
It was a real pain in the ass to edit and maintain, that's how I got the idea.
I'm building a tool to render Stripe-like API docs from OpenAPI/Swagger files.
I thought that the best way to get people to discover my tool and be useful at the same time is to build docs for various open APIs.
(Let me know if you need API docs for your open, or even better, an open source API, and I'll make it happen!).
How it works:
- The OpenAPI/Swagger is stored on S3 and rendered on the server-side using NextJs (on Vercel).
- I use NextJs's incremental static rendering (ISR) to render the doc in the background.
- NextJs's middleware (a new thing in NextJs 12) routes the request to an appropriate route based on the subdomain.
- I'm looking to make the docs generator an open source in the future, when I build out the editing feature which will be paid.
Found this endpoint while exploring GitHub's openapi specs. It returns a random phrase like 'Keep the flow going'. It rotates the phrase every 5 seconds or so.
The UK has partially funded AZ and added a clause into the contract that will prioritise UK for future vaccine exports from the UK. And that's exactly what's happening, all AZ produced in UK stays in UK)
Whereas a similar contract between Germany and Biontech (Germany paid biontech $445 million to help develop the vaccine) didn't include a clause defining export priorities.
Pfizer-Biontech is exported all over the world.
Canada, for example, gets their Pfizer-Biontech from the EU, instead of Michigan where they're also produced.
I wouldn’t be surprised if I saw this in a mad max convoy. But in a good sense. Love the minimalist industrial design.
I’m sure it would raise some eyebrows if I rode this on a street where I live. I’m not sure however I’d ever want this as my main vehicle (unless I’m in a postapocalyptic mad max scenario where this would be a must).
DPAGE is not able to remove user data (even if it's illegal), because we don't store it. However, storage hub providers will have the ability remove it.
What dpage can do is deny the access to illegal content by blocking illegal dpage.io urls. But then, a user can pick to use another app that serves the pages created on dpage.
Correct. However, the idea is that you can run your own storage hub on a server of your choice, or, in the future, choose one or more storage providers that you trust and keep your data there (storage providers can't read your encrypted data)
This way you'll be able to pick both: 1) your storage provider 2) the app that works on top of your data
Hi, one of the DPAGE creators here. We’re a team of two guys who used to work at Wix (website builder). We felt that there are not many good options if you want to quickly set up a minimalistic webpage or publish some content online. So we built dpage. With dpage you can edit your pages in a dropbox paper-inspired editor and give them human readable urls. We want it to be good for personal homepages, keeping and sharing your notes, snippets and embedded content (e.g. youtube videos, twitter posts, or github gists).
In terms of tech, it’s built on top of Blockstack’s decentralized infrastructure. You log into DPAGE using a decentralized id, and your data is stored on Blockstack's decentralized storage hub (Gaia). At any point you can run your own storage hub and store your data on your own server.
DPAGE doesn’t store user data, it connects to user’s storage hub from the browser when user logs into the app. Gaia storage hubs are usually publicly accessible, but all private information is end-to-end encrypted with the private keys associated with the user’s Blockstack id.
As a result, there’s no vendor lock-in with DPAGE, users can bring their data with them to other apps, they have complete control over their data. For example, if Facebook was built this way, a user who doesn’t like FB could seamlessly start using another app and keep all their contacts and messages.
We realize that it might be harder to monetize a product, when you can’t lock-in users into your app. You basically voluntarily open yourself up to the competition. On the other hand, the total value that the product can create for the world is much greater if the data is controlled by the users and they can permission other apps to use it. Imagine all the innovation that could happen if all the data on Facebook was open to developers (with the permission of users who own the data).
We’d love to hear your thoughts or feedback about the idea or the app.
Actually, if you scroll down there's an explanation of what will happen when you click create. Perhaps it would've been better to add a tooltip on create.
But generally I agree, it's hard to design UIs in crypto, having to install and use a plugin like MetaMask doesn't add to the trustworthiness of the site.
All very good suggestions, they will help prioritize what to do next!
Yes, charts only use d3. By now the charting code has become a small d3-based js charting library.
Before I continue working on this I'm trying to understand who the potential users are and how they would use software like this. Thx for your comment.
It's just that I'm not sure I can do it until I have these advanced features. If I can't make money out of this I have to return to my day job, and stop developing portal.dev.