15
Tounai
139d

Fuck Confluence and anyone telling me to write anything there. From now on, documentations will be in the repo, written in Markdown

Comments
  • 0
    Oooooh lovely
  • 0
    I don't mind md but what's the problem with conflu? Unless you're trying to plant uml or something it should be straightforward.
  • 6
    Great, now somewhere else I need to add to the list of "where the fuck is the docs for X?"

    - did you try confluence?
    - did you check oneDrive?
    - ah actually it might be in GDrive!
    - oh nope, it's in box!
    - wait nope my bad it's in the teams chat... I think.
    - ooh, I found it, was buried in the mono-repos readme!

    Fuck confluence; but seriously keep shit together regardless what your preferences are.
  • 0
    Technical info & maintenance procedures definitely in the README/ docs folder, design in some SaaS like Figma or Zeplin, and project docs on Confluence. Cross-referencing allowed
  • 0
    That's exactly what I do.
  • 0
    @neriald it’s slow, search does not work, editing text is a pain, it’s flashbang white, it’s hard to organise. Average Atlassian product, I know.
  • 0
    @C0D4 Well you know what? If it’s the mono repo, you put it somewhere near the code it refers to. Perfect for me. Saves me from using Confluence search or organising that stuff two times.
  • 0
    Everyone knows confluence is write-only
Add Comment