marttilaine

When someone wants to contribute without understanding the code workflow, he should not contribute.

There are definitely many projects where you don't need to understand every single aspect of the codebase to be able to contribute a meaningful fix or even a feature.

It benefits the contributor and the project if they have a simple pointer to e.g. where the application logic code is, or where the distribution-related code is, etc.

I experimented with something similar in one of my larger side projects a couple of years ago:

https://github.com/shipmight/shipmight/blob/master/src/ARCHI...

At the top of each file there was a tree of links to other ARCHITECTURE.md-files in the repo, like this:

    * ARCHITECTURE.md <- you are here
    * backend/ARCHITECTURE.md
        * backend/api/ARCHITECTURE.md
        * backend/cli/ARCHITECTURE.md
        * backend/ui/ARCHITECTURE.md
        * backend/utils/ARCHITECTURE.md
    * frontend/ARCHITECTURE.md
    * internal-charts/ARCHITECTURE.md

For anyone struggling with Helm YAML syntax errors in their day job, I shamelessly advertise my browser-based debug tool Helm Playground:

https://helm-playground.com/ - https://github.com/shipmight/helm-playground

Thanks for the tip about Lucidchart line drawing, will check out how they do it.

What would you imagine as the optimal AI workflow? Iassume it's more complex than just issuing commands like "move AWS-section under Infrastructure"?

Yes, it's planned! My knowledge on distributing a Linux desktop app is a bit limited, but I plan to add .deb and .rpm releases soon.

There is potential to import and export DOT and e.g. Mermaid. Of course the editor functionality would be limited to what those formats support, and diagram layout would not be exported 1-to-1, as it's recalculated by the renderer of that format eventually. These are not on the immediate roadmap.

Hmm. Not able to reproduce this issue. Do you see the clipboard icon turning to checkmark on the second copy too? If not, then the browser blocked the second clipboard operation.

Thanks for reporting! Fixed.

Sorry about this, was an oversight. Should not do that anymore!

Thank you all for the feedback on this! I agree. It didn't seem like such an issue during development, but that was a misjudgement. Removed that functionality now. Should not add to history anymore (shareable URLs should still work).

As mentioned in the sidebar, this tool is inspired by https://shadows.brumm.af/

I've used it a lot, but it always lacked a few features I would've used extensively, such as shareable links, copying to Figma with a button click, ability to change the background color, and a library of ready-made shadows. Also, I think the terminology is perhaps a bit clearer for someone who hasn't looked deeply into how this layering technique works.