https://www.dendron.so/ logo
Powered by
# questions
  • u
    The title is 
    Front End Engineer - AWS, IoT DPP
    Thanks for the tip on that! Right now their main focus is on the Code Challenge since I believe that needs to be passed before going on to talk to anyone in person 🙂 They're doing a crash course on data-structures and algorithms at the moment 😄
  • u
    One more thing, do you know how much weight is put on internal referrals there? BC they have a friend who works for AWS actually but didn't list him on their initial application
  • k
    it helps get you in the door but if your already doing the loop, then its less necessary. but it doesn't hurt to mention it to your hiring manager
  • u
    Ok cheers thanks!
  • u
    Bug Request Submitted too 🙂 https://github.com/dendronhq/dendron/issues/749
  • u
    Bug request is such a fun thing, do you want a feature report too? )
  • f
    I didn't even notice but this is great xD
  • t
    So, I have a note a.b.md, and a note a.md, in a multi-vault workspace. When in a.b.md, I can't seem to do a block-header ref to a.md. Bug?
  • t
    ![[dendron://vault/a#HeadFoo]]
  • k
    that should work. can you try lower case kebab to create the link? if you select 
    #HeadFoo
    you can use the 
    copy note ref
    cmd to create the link https://wiki.dendron.so/notes/eea2b078-1acc-4071-a14e-18299fc28f47.html#copy-note-ref
  • v
    I was wondering if I need to set up some configuration? Would appreciate if someone could take a look at this example. The template "journal.template.daily" won't apply at all if I open a new note named "journal.daily.2021-05-22".
  • b
    have you tried using the "insert note" dendron command to make use of the template you have? i'm not sure if it is fully possible to be automatic. check here: https://wiki.dendron.so/notes/861cbdf8-102e-4633-9933-1f3d74df53d2.html
  • v
    Yeah so insert note seems working. But based on the example given, it should be detected automatically ? Not sure if it is a deprecated example.
  • b
    yeah that i'm not sure about
  • h
    Can you try 
    reload index
    and see if it fixes it?
  • v
    Yeah I have tried multiple times, reloading index and reloading the workspace
  • h
    hmm. let me take a look at the video and see if anything seems wrong.
  • h
    could you try using this schema instead? :
    Copy code
    version: 1
imports: []
schemas:
  - id: journal
    parent: root
    children:
      - daily
      - weekly
      - yearly
  - id: daily
    namespace: true
    template:
      id: journal.template.daily
      type: note
  - id: weekly
    namespace: true
  - id: yearly
    namespace: true
  • v
    yeah using your file works, so I guess "schemas : " is the problem ?
  • h
    yeah, we introduced schema versioning at some point and the video for templates was taken before that. Sorry about the confusion.
  • k
    yeah, sorry about the confusion. i'll make sure to update the docs!
  • n
    Hi, is there a version 2 of the config yaml file? I see the documentation and it seems to not apply for mine which is version 1
  • n
    I also see there's apparently some sort of new directory layout. Is there a way for me to easily convert, or is it easier if I just start from scratch?
  • k
    we're still on version1. what's your current layout?
  • n
    Copy code
    version: 1
vaults:
    - 
        name: work
        fsPath: work
        allowPublish: false
    -
        fsPath: vault
useFMTitle: true
noLegacyNoteRef: true
site:
    copyAssets: true
    siteHierarchies:
        - root
    siteRootDir: docs
    usePrettyRefs: true
    title: Dendron
    description: Personal knowledge space
    duplicateNoteBehavior:
        action: useVault
        payload:
            - work
            - vault
initializeRemoteVaults: true
  • n
    Oh you meant directory tree
  • n
    I thought there might have been a v2 of the config, because allowPublish just didn't work to block notes under the work category from being published at all
  • n
    The workspace has a folder for each vault. Each vault folder has root.md , root.schema.yml then the notes
  • b
    I'm still wrapping my head around publishing so my remarks may be just nonsense but I read your config as if you don't want to publish the work vault at all. If that's true the setting under 
    duplicateNoteBehavior
    looks a bit strange. I would then omit the work vault there.
  • b
    I'm in a similar situation that one of my vaults contains work-related and hence sensitive information that shouldn't be published. What I'm thinking of is to create another workspace and reference only the directory with my personal vault in it and use this workspace for publishing. Is that a sensible idea?
1...323324325...757Latest