https://www.dendron.so/ logo
Join Discord
Powered by
# chat
  • s
    I don't know where to put these thoughts, so I just drop them here. Different types of people (for example Dev/Tech, Supporter, and maybe even User, access the same Notes about an Application.) But the way they think and traverse through the notes/Application is fundamentally different. The urge to have a 2. hierarchy, and maybe be able to switch between them always comes back to me
  • r
    We're hitting this as the moment where we're trying to build something for the majority of users but the specialists are trying to add features/fields that, yes are important in some contexts, but for the vast majority are not useful. In this case because the goal is to deliver something that gets 80% of people 80% of what they need, we don't add those features/fields.
  • r
    It's why I recommend most people don't use the official oracle docs for their databases, they're meant for DBAs, something like techonthenet or w3schools is what most people want, but you sometimes need that detail
  • r
    How you combine the two whilst avoiding duplicated effort is the hard question...
  • s
    My initial thoughts were just about User Experience, not even just hide, or add Information. People can extract what they need and leave the stuff they don't. For example, we have a Document Management Software based on SharePoint. Let's just assume 1 Person would create and use the Notes to highlight the difference. And the Information they add is the same. I as a tech Person would orient myself on SharePoint Structure and Components 
    WebApp.SiteColl.Web.Web.Whatever
    TermStore.Regulations.iDontKnow
    While Support People likely thinks in the structure of the Application 
    ProcessManagement.Processes.Metadata
  • s
    For me, what you want is already the next step
  • s
    Initial thought to different areas/levels of Information is to add some kind of Metadata to 
    Blocks
    of Information. 
    Level3
    , or Roles like 
    User
    Developer
  • s
    Copy code
    markdown
## Summary
No Role Info for everyone

[#Developer#]
### Technical implementation
some fancy Info
  • s
    Don't know what I think about a selector on the final Page to change the Content
  • m
    Does anyone know how to automatically
  • k
    Being able to define "level of details" (or more generallly tagged optional content) inside notes might be an interesting idea.... đź‘Ť Not sure if it would match the 80% of users will need it condition though...
  • k
    But I think once Dendron supports plugins at all levels of functionality
  • k
    I could see someone developing such a feature
  • k
    as a plugin
  • k
    and then you could also add it to your publishing... that you could have a simple setting value (maybe just JS local storage backed) which lets you specify you "activated" content tags
  • k
    And the hierarchy thing could maybe be solved by some kind "symlink" feature? I don't know 🤔 Being able to link whole hierarchies (or just single notes) into other hierarchies
  • c
    Interesting, a “dynamic level of detail”. I’ve could see teaching content use this approach too (explain a concept at beginner, intermediate, advanced difficulty). My initial reaction for how to address this inside dendron would for the basic page to have the level of detail that works for everyone, then put any specialized persona specific content in a child page.
  • c
    https://arbital.com/p/bayes_rule/?l=1zq was an education project that tried to do this using a choose your own adventure style opening
  • c
    I also see people doing this as one offs for explorable explanations. You can implement thjs right now using the HTML “details” element in markdown, although you may need some custom css to help people realize the block is clickable http://tomasp.net/coeffects/
  • k
    IDP roulette - A fun past time whenever I login to a service I haven't used in a while. Since I'm never consistent with how I create an account, I end up creating new accounts more often then not 🤷‍♂️

    https://ik.imagekit.io/s9fua8eoi/Mouse_Highlight_Overlay_rgmywzA19.pngâ–ľ

  • r
    Unrelated but if you want an alternative to Goodreads I migrated to https://thestorygraph.com/ last year and have been enjoying it
  • k
    interesting, never heard of it
  • d
    Not sure if this was shared yet but this is great for me https://code.visualstudio.com/blogs/2022/07/07/vscode-server
  • k
    is this a microsoft blessed version of https://github.com/coder/code-server ?
  • d
    I haven’t used that but from the name - yea it can run your VScode in a browser. But what’s cool about this is that you can spin it up on your personal computer. So that’s what I’m going to do with my main personal dendron repo so that I can access it easily from work, my phone, etc.
  • d
    And it’s less setup than when I looked at GitHub codespaces. Seems fairly simple to use. Will report back!
  • d
    hey everyone! does anyone have a preferred way of nicely structuring code commands with short descriptions? it's a use case i often find myself in. here's an example of what i do today:
    Copy code
    ## Kubernetes

- get deployments: `kubectl get deployments`
- get pods: `kubectl get pods`
- describe a pod: `kubectl describe pod <name>`
- get logs: `kubectl logs <podName>`
  • d
    does anyone have a better way / suggestion? maybe using a table? maybe a way that easily allows for sharing commands on a more granular level / referencing a line or something? open to ideas, thanks!
  • s
    I will often use commented code blocks:
    Copy code
    yaml
# Get deployments
kubectl get deployments
# Get pods
kubectl get pods
# Describe a pod
kubectl describe pod <name>
# Get logs
kubectl logs <name>
  • d
    i like that much better than what i have, thanks!
1...134135136...148Latest