The current linking functionality in SN is good, but lacks some options. One of such options is ability to add a linked card in an embedded form.
For instance, I always have cards for specific projects or task subsets. Currently, I have to link these in other cards when relevant and keep navigating back and forth if I want to say check a task on the linked card.
When pasting or creating a link, it would be tremendously powerful to have the option to paste it as an embed, where one can interact with the elements of the embed (check off tasks, navigate to links, etc).
This is implemented really well in Heptabase, please see sample
This wouldnât help me much. I like how a link to another card pulls up that card in preview mode. Embedded notes are indeed quite useful in other notes/pkm apps but those typically donât have a card length limit.
I like the simplicity and card âsoft limitsâ in Supernotes.
I suppose a variation of your idea, where a portion of the linked card could be revealed as an embed might work okay? Or maybe embeds of any length could have soft limits. But Iâm not sure if those extra layers of complexity would be worth it.
For another idea, maybe embeds would only show in seamless card mode.
Not everyone uses the application in the same manner. Just because it wouldnât help you much doesnât mean it doesnât have a good use case. I donât use some parts of SN that Iâm sure others do.
None of what you mentioned would go away or contradict this, as you can clearly see in the demo, the regular links are still available. If one doesnât want embeds then simply donât use it, no need to limit them to a specific mode.
Of course. Embeds could be helpful for some, even if I wouldnât use it. I just wonder how it could successfully fit into the cards with soft-limits paradigm that sets this app apart from others. Perhaps others can offer ideas.
@fuzzy.beach Could I ask why adding the card as a child doesnât match your use case? Then you can navigate to the parent, see all the children in one page, and check off their tasks, etc.
I use the parent child pattern somewhat differently than this. Letâs imagine I have a daily card that captures whatever daily notes, thoughts, etc. I also have a âTop Tasksâ card that captures my current priority tasks. This card is âlivingâ and gets updated all the time.
Now if i keep adding children to it, itâs going to end up with 100s of those rather soon.
Hey all, a very good discussion here. Thought it might be useful to provide some of our insight into this.
Most other more technical note-taking apps are long-form outliners and are block-based rather than card-based. Each paradigm has their own strengths and weaknesses, and indeed with long-form approaches embedding makes a lot of sense.
By focusing on short-form cards we encourage your notes to be more simple, reviewable and linkable. Generally embedding cards in other cards, goes against this approach and encourages longer duplicated content. This is also why weâve built a parent-child flow, so you can quickly house relevant cards within each other.
At Supernotes weâre also not too keen to just tac-on features that other apps have, we like to take our time to tackle the problem head on and build something different that helps you even more. So while we arenât too excited about adding embeds within cards, we do want to make it easier to navigate between cards and interact with them such as adding child cards below a card in preview mode and more things in the pipeline.
Iâm marking this as âunder-considerationâ at the moment, because while we wonât offer full card embeds, we may offer a universal concatenated version of card links along with url links. So if you write a link (whether itâs a card or url) on a new line by itself it will become a little preview.