3 ms·
> IIRC there was a time when Confluence axed their markup, and inevitably a table or a template would get completely screwed, and there was nothing you could do
by Twirrim 7y ago
> IIRC there was a time when Confluence axed their markup, and inevitably a table or a template would get completely screwed, and there was nothing you could do but recreate it. TERRIBLE design.
There was. I was using Confluence at the time, and it broke a lot of things. There was a wonderful filed bug at the time with a lot of angry people on it, where they promised to bring the old mechanism back as an option, and they never did. That told me everything I needed to know about Atlassian.
- abbadadda 7y agoAtlassian Jira/Confluence SUUUUUCKS. They have given up on making anything better. I try to do as much as possible on Markdown files in a GitLab repo using Atom's Markdown preview (e.g., documentation). Gliffy diagrams are still OK.
- xref 7y agoSame, README.md for most everything I can. Searching for info in the repo is also more productive than the search nightmare in jira/confluence.
- samanthalee233 7y agoGitLab employee here, nice to hear that GitLab is helping solve some of these workflow issues for you.
- abbadadda 7y agoFor sure! One thing to take a look at might be markdown numbering rendering in the browser. E.g., if I use `1. 1. 1. ` I only get ones, not 123 (last I checked).