What is the best way to onboard my team to dendron...
# questions
d
What is the best way to onboard my team to dendron. A traditional team that is using confluence, word docs etc. but would love to transfer everyone over to dendron
k
a few ways to do it. if everyone is comfortable using vscode, markdown and git, you could create a workspace for your team. we have some example layouts for teams here: https://wiki.dendron.so/notes/98f6d928-3f61-49fb-9c9e-70c27d25f838.html if you have folks that won't be comfortable in this environment, a few thoughts: - if folks primarly are reading docs: - to share the entire workspace, you can publish your internal repository and host it inside your private network (I believe github pages allows publishing privately) - if you need to share selected documents, you can use the [gdoc](https://wiki.dendron.so/notes/hA02kromgLKegxaG2VHKE.html) export to share notes via google docs - if you need to publish to confluence, you can use tools like [GitHub - duo-labs/markdown-to-confluence: Syncs Markdown files to Confluence](https://github.com/duo-labs/markdown-to-confluence) to do so - if folks want to **write**: - they can edit via github/gitlab (whatever your hosting repository is) and commit files via the web interface (downside is they won't be able to see dedron specific markup) - we've talked about adding a chrome extension to make this process easier so you can get a dendron preview in the browser when you're editing this way
d
My initial thoughts in terms of complexity leans towards having the less technical folks edit markdown directly on GitHub/gitlab . They just lose the nice hierarchy and things in vscode
And then optionally send some dendron documentation to onboard onto using vscode if they want (I imagine a non technical user could use vscode if they learned a few commands )
k
that would be a solid start. let me know if you run into any friction with this. happy to help!
@User let me know if you have specific questions about the teams process
d
hello as well @User
a
@User @User Thanks a lot!! Lot to digest for me here, but I think I got the general idea. I think I will get better understanding as I dabble more in Dendron.
Though from reading the above information, my quick impression is that a chrome extension will be way to go. Though in general I avoid browser extensions because of the scope for mischief and malice is huge in browser extensions.
d
actually i think browser extensions are supposed to be very secure compared to say web applications. but i am not an expert here.
a
ohk. I thought it all depended on how much due diligence chrome-store team put in before allowing chrome-extension in the chrome-store
d
btw @User i have no relation to dendron dev team, just an avid user. let me know how it all goes for you. i really would love my team to use this...
a
sure, will report my user experience with the teams setup in Dendron, once I figure it out.
d
so update, im just like.... chugging along with my own internal documentation with dendron
and im hoping i will just publish this to my team as a "handbook" / open thinking knowledge base
instead of overwhelming with a shiny tool out the gate, ill show how i actually have managed all this information im learning and then just demonstrate that hopefully with some pages i publish?
we use gitlab so ill have to see about how to host it... would really like something that looks like the dendron wiki
k
you might want to consult @User who is using dendron in a similar fashion and just published to gitlab 🙂
r
Yeah happy to chat! I'm using it as a tool to share the output with my team rather than have them also input (for now anyway) but happy to chat about how I'm using it and got publishing on gitlab working
d
That’s exactly what I’m thinking of doing
Show the way and if they get excited and want to contribute - that’s awesome
So how does it look on gitlab ? Is it themed like the dendron wiki?
Or is it on the actual gitlab uri
r
Looks exactly like the dendron wiki as it's published to gitlab pages which just hosts html pages. Derek has put together some gitlab CI/CD that you should just be able to clone then put your vault into and it work https://gitlab.com/ScriptAutomate/template.publish.gitlab
Or you can copy the relevant stuff into your repo if you have a more complex vault setup
You'll need runners to do the actual building, my company has a set of shared runners anyone can use but not sure what your setup is or what to do on public gitlab
5 Views