since you replied to the [ ], wanted to also give you heads up

Anyone know how to get markdown emoji (extension) to autocomplete emoji in notes? Or have a similar solution/extension? EDIT: trying

idleberg.emoji-code

which uses snippets for now. EDIT: moving onto

perkovec.emoji

because snippets came up way too much when typing

I really like the concepts behind dendron. However, some of the features require knowledge that I don’t have (e.g., schemas). I have been wrestling all day asking myself a few questions and I want some feedback. 1. Should I just go back to a different program made for more simpletons like me (e.g. Obsidian or Zettlr) and implement some of the concepts there (although it wouldn’t be smooth)? 2. Is there more simple ways to learn some of these features than I’m realizing? 3. Should I just pass over some of these features and keep using dendron until some of these features are easier to use for a user like me? I think that’s it. 😆

I'm familiar with concepts like schemas from the work I do but I'm limiting myself to the bare minimum features so far. I plan to use other features later when it makes sense in my workflow.

I think kevin does onboarding for new users so I guess that's another option as well: https://www.dendron.so/#onboarding

Yeah. I have thought about doing that. I could actually do it this week too. Work is usually in the way.

As an entry level developer I can see the power of Dendron and what it can be. I also have taken a gradual approach to learning markdown-based pkm. That's why I used Obsidian for a month before really diving into Dendron. For many of my colleagues in physics who are not IT types, Obsidian will be the goto recommendation for a gentle intro to the vaults that I'm working on. Some will gravitate toward Dendron if they want to get stronger as an engineer, others may just feel more comfortable working outside of an IDE.

That being said, I did consider setting up an onboarding session but 98 percent of issues I've had I ended up figuring out. It's a fantastic offer and I'm glad more people can get up to speed. In my case, I guess I hope @User can concentrate on other things while I debug my issues. A few aspects of Dendron I have yet to crack though, in order of priority: 1. snippets (I've dealt with some odd bugs) 2. schemas (which I think will be more useful as my notes expand) 3. multiple portable user environments and settings syncing with VScode 4. developing on vscode extensions to somehow contribute features in the future

i have some extended sessions for folks that have a hard time making the regular slots. i’ve sent you a link over dm as for having trouble getting started, i will take responsibility there. dendron is meant to be for everyone but the initial implementation inside vscode definitely includes a lot of additional complexity. that's where having your feedback is really helpful to make sure dendron is easier to begin with. 1. different programs -> other tools like obsidian are definitely easier to get started with. and the theory behind dendron's dot delimited hiearchies can be used anywhere (though certain features like refactoring, lookup, and other hierarchy specific functions will be missing) 2. simpler ways of learning -> i'm currently working on a re-vamped tutorial to go over the core ceoncepts. you can see the beginning of it here: https://www.dendron.so/notes/678c77d9-ef2c-4537-97b5-64556d6337f1.html 3. pass over some features -> certain features like schemas are optional. they are definitely not required to use dendron and we're actively working on simplifying them.

1. when you say snippets, you mean vscode snippets? we had issues with snippet completion showing up when it's not supposed to but that should be fixed with 0.20. let me know if that's not the case 😅 2. schemas - this needs work to simplify it and smooth out some edge cases. probably 01/21 work 3. for portable environmets, i use different versions of vscode. @User also brought up being able to use workspace agnostic vaults which I hope to have implemented in a few weeks (https://calendly.com/thence/meet-extended) 4. contributions always welcome. docs here: https://dendron.so/notes/81da87be-2d4e-47b5-a1d6-c0d647e1ab00.html will be posting some good first issues later today 😇

I was gonna ask if there are some good firsts to get me going 😄

I'm hoping to get set up and start tackling some of them as I get used to TS.

To be fair, you are on 0.20.0 - So, it's early on. I also heard you talk in a podcast about why you went with vscode and it makes sense. Thanks for the feedback from all. I have a meeting scheduled, and I learn some things along the way! "we're actively working on simplifying them." - Thanks. 😂

So what are the main features you find complicated or irritating? As Kevin wrote schemas for example are purely optional. There is only limited loss if you omit them for now. If you share your obstacles I'm happy to help if I can

Thanks! I understand they are optional, but I want them, and I don't know how to use them. 😊 I don't know how to create the X.schema.yml file properly in vscode and where to put it within my vault. It's hard for me to understand the explanation of it's anatomy in the documentation also. I can't follow the logic. It's over mi head.

Would a UI help in creating them? That you have a visual form of creating them with input fields?

What do you want them for? I mostly use it for templates

I think it would. But, not a 💯

Note Templates, yes. And, as I understand them, they are templates for topics, which, I find to be a feature that could be helpful, especially for projects (which is one of the examples given).

I’ll also throw out that I’ve recently been exploring schemas as well, and while I don’t claim to be an expert on them, I’d be happy to walk through the couple I’ve set up with you over dm or voice sometime other than today if you think that would be a benefit

My use case is having a standard for my journal and meeting notes

If you share what your intent is we might be able to build it up together

Here is where I am: I want to understand the tools in the toolbox (dendron = toolbox). So, it's not that I'm looking at the problem, and I'm saying, that is the tool that will solve the problem because I know how that tool works. It's that I see there is a tool there, and I don't know how to handle it, or how I would use it yet, but I want to know in case I run across the perfect problem it would solve for me. So, what @User suggested with "walk through the couple I’ve set up" would be the best for where I am.

Very happy to anytime, I’ll probably be building another couple out in the next few days too, so I’ll have more examples or can hold off on one or two to build alongside you if you want. Just ping me whenever if it’s of interest, no issue if not!

is there a list f all features?

nice, thanks

kevin was faster xD

is there a setting for leaving behind a ref when you extract a chunk of text into a new note?

Not that I'm aware of but it would be highly useful!