3 ms·
Nice. Very intriguing. Question: Do you have an option where your backend could be used to supply content to a frontend public website? Mind you, given your da
by chiefalchemist 6y ago
Nice. Very intriguing.
Question: Do you have an option where your backend could be used to supply content to a frontend public website? Mind you, given your data structure, I'm not sure how that would work.
Let me give you an example. I like to read, mostly long form non-fiction (i.e., books). Naturally, I highlight things of importance. I want to take those ideas and get them into something where I can organize, add categories and tags, etc.
Yes. A basic WordPress site would be sufficient. But given a tool like yours, why not try to take up a level? On the backend, my "thoughts" well organized. The frontend some view of that I'd want to share with the public.
Thoughts?
- fastball 6y agoThanks! And the answer to your question is yes, absolutely! Hopefully quite soon (we already have a working demo) we will introduce "card pages", which will be public (or semi-private, it'll be configurable) pages that represent either a card itself or that card's children. These pages can then be embedded into any other webpage. The idea is to both support behavior akin to embedding a tweet, where you are just viewing a singular card as a card, but also to allow people to effectively create "documents" on Supernotes (that can then be shared publicly) by displaying the children of a card in "seamless" mode, so that even though it's actually a bunch of cards under the hood, it'll look like a blog post, or wiki article, or readme, or whatever. Every card on Supernotes will be able to have multiple pages, so that you can have a truly publicly-facing representation (which might limit how people can interact with it) but simultaneously embed your card somewhere else that is semi-private (like a Notion doc for your team) and allow people to actually interact / edit the card from there.