7 ms·
Show HN: Atlassian Design for Bootstrap v5
Atlassian Design for Bootstrap 5. Beautifully crafted Bootstrap components ready for your next project.
- ilrwbwrkhv 3y agoWhy would anybody in their right minds make their app look like Jira?
- pokstad 3y agoExactly my thoughts. This design is going to trigger my PTSD.
- NewJazz 3y agoMy coworkers literally did this with out internal apps and I have no idea why. I hate it so much.
- sebazzz 3y agoIn that case it should show loaders and placeholders whenever it can, and often.
- laurent_du 3y agoWhat's wrong with JIRA? It looks good and does its job well.
- simonbarker87 3y agoIn my opinion tech internet loves to dunk on Jira as it's seen as the manifestation of all the problems of Scrum and Agile. It's a "thing" people can point to so it becomes Jira's fault. People will nit pick over, sometimes justifiable, UI/UX issues with the product but the level of hatred you see can't be explained by that alone. In reality the problem is with Scrum and Agile.
- gjvc 3y agoAtlassian, through their flagrant and wanton behaviour of enabling and encouraging such activities, are the main drug dealers to and for Scrum and Agile junkies.
- orangepanda 3y agoMy nit pick over Jira's UX - they recently changed how board is implemented, breaking ctrl+f
- lmm 3y agoNope. Scrum and Agile are great. Jira is in many ways the antithesis of them: it favours processes and tools over individuals and interactions, it elevates comprehensive documentation over working software, and it encourages following a plan over responding to change.
- simonbarker87 3y agoSorry I should have been more clear and said "manifestations of all the problems of Scrum and Agile have become". Jira has implemented all those features because that's what the industry (managers and people that like control) wanted Agile to become, so, to make money they did so. I don't blame them for that, they aren't the defenders of Agile. Again, the problem isn't Jira. If you strip away all the reporting, burn down charts etc what you are left with is an exceptionally powerful Kanban board with, in my opinion, a solid user experience.
- XorNot 3y agoIf you strip away all that stuff, you could be using another, better product and should be.
- simonbarker87 3y agoI'm yet to find one to be honest. - Trello feels like a toy (it's not, we use it extensively for core business activities but I don't like it for software) - GitHub issues feels too focussed on devs - Todoist is clearly designed for solo use - Monday.com is for more generic project management - Notion is a mess when you have a lot of tickets - I don't want to use ClickUp After going though all of those I realised that Jira is pretty good for me.
- lmm 3y agoIt performs terribly and gets in the way of doing productive work. The part it does well is enabling obstructive micromanagers and giving them pretty-looking charts to help create a false impression that development is predictable.
- laurent_du 3y agoCould you explain how Jira gets in the way of doing productive work? I genuinely don't understand where is the issue.
- lmm 3y agoYou usually have to fill in a bunch of unnecessary mandatory fields before you can do anything, and by default you have to follow the workflows that have been set up by someone with more permissions than you. In particular that means that if you ever accidentally drag a card to the wrong column or something (very easy to do with the incredibly slow UI) you can't undo it and probably have to remake the ticket from scratch. Also it nudges you towards using the ticket ID rather than any actual descriptive name everywhere, so everything you do accumulates this extra layer of indirection.
- p_l 3y agoThe workflow thing is why the usual advice with JIRA is to keep to Atlassian-supplied workflows instead of developing your own. The custom workflows are often mandated by clueless managers, and often even if you have clueful JIRA admin they will silently try to fix manager's dumb idea instead of having the manager eat the turd sandwich. Once, a coworker of mine decided that enough is enough, and decided to implement a workflow exactly as specified by management. After week or two of totally lost productivity and reporting, system-supplied workflow was returned to and the manager never again tried to play with workflows.
- DrBazza 3y agoAbsolutely this. Useless product managers adding custom fields and values that make zero sense. Developer issues (eg. github issues) aren't the same as helpdesk requests, and aren't the same as customer enquiries. Yet Jira happily smashes them all together.
- KronisLV 3y ago> What's wrong with JIRA? It looks good and does its job well. I don't really like Jira: * it is on the slower side of things, unless you throw a decent amount of hardware at it in a self-hosted deployment (then again, something like OpenProject is similarly slow, the only truly fast piece of software in the class I've experienced was Kanboard, but it's very specialized and really light on features, so not a 1:1 competitor) * the API isn't all that pleasant to use, even though you can sort of understand that due to the level of complexity/customization (I recall struggling with a Java client library, when I had to find issues based on the values of custom fields and some other constraints I think, but it was a while ago) * their text formatting was pretty horrendous and unreliable on the version that I used, which is perhaps my biggest actual gripe: if you had snippets of code under and issue, as well as lists, images and a bunch of other formatting, it *reliably* broke for me whenever I tried making any changes, when I tried pasting stuff in, or using the UI buttons for formatting That said, it looks okay and I have no problem with the actual design system. In addition, if Jira lets you do what you need to, then there's nothing wrong with that either - keep using whatever works! Take my "complaints" with a grain of salt: I last used it a while ago and therefore don't remember super specific details, aside from the text formatting being an absolute pain every single time.
- doix 3y agoThe API and the search are probably the only positive things I can say about Jira. JQL is probably peak issue-tracker searching, I don't see how it can be improved. Maybe in 5 years from now LLMs can accept arbitrary input and find what I'm looking for, but until then, JQL is great. Also I thought API is great, or at least the community python package is[0]. It's probably the best experience I had integrating with an issue tracker. FWIW, I used it in a semiconductor company that used it to manage work on their ASICs, so things were fairly heavily customized and there were over 100k tickets. [0] https://github.com/pycontribs/jira https://github.com/pycontribs/jira
- DrBazza 3y agoClearly you've never tried to format code in either an issue description or comment. And I can only guess you've never had a product manager justifying their jobs by adding in a bajillion custom fields and field values into an issue. And then filters that use those. This case is a user problem, but the Jira does little to prevent or help.
- dbbk 3y agoIt looks good?? It's a mish-mash of UI dating back to seemingly the 90s. Take one wrong turn and the UI falls apart.
- quickthrower2 3y agoTo sell to the kind of people who spend a fortune on Jira!
- kentosi 3y agoI don't think that this is associated with Atlassian (the JIRA company) in any way. Or at least I can't find any association on this github page.
- kadomony 3y agoCame here to say this. Glad I'm not alone. This seems like such an odd investment to make given the development community's near-universal hatred for Jira/Confluence.
- pier25 3y agoI'm surprised they used Bootstrap. Atlassian is big enough to create their own CSS custom framework.
- throwaway7c4ffa 3y agoI think they made the right decision. Bootstrap has been around for years and the level of experience they built up has great value. In my view the question is "why shouldn't they build on top of an existing stable base?". If I made that decision for a business, we would have started the discussion there. An argument for creating our own framework would need to convince me of its value to the business. Just because the company has resources to do it, doesn't mean it is the best use of those resources l.
- gjvc 3y agorandom opinions and no due diligence; this exemplifies everything which is wrong with this industry.
- pier25 3y agoBootstrap has many limitations, even when customizing it with SCSS. I went down that road last year and ended up ditching it because there's not enough customization. I can't imagine any company wanting a distinctive design for their components using it.
- rickette 3y agoThis isn't affiliated with Atlassian.
- pier25 3y agoOoooohh now that makes sense. I was on my phone and didn't catch that.
- chrisco255 3y agoThey have their own React component kit: https://atlaskit.atlassian.com/ https://atlaskit.atlassian.com/
- CSDude 3y agoAtlassian already has its own UI kit. It's in React but there is also a CSS version. https://atlaskit.atlassian.com/ https://atlaskit.atlassian.com/
- chrisco255 3y agoYeah this follows the same design language I believe.
- Aeolun 3y agoGot to love that atlaskit is so unuseable people go out of their way to recreate it in bootstrap.
- gjvc 3y ago"Beautifully crafted" and "Atlassian" only belong in the same sentence with an odd number of nots.
- deliriumchn 3y agoThese components look pretty good and very neutral design-wise, no screaming style, which is important for someone who's looking for a components library.
- gjvc 3y ago37 points and flagged
- bilekas 3y agoMy god.. This is an interesting project and well done. But I can't help but feel that Altassian design might not have been the best source of inspiration! But maybe someone can "fix" the cesspool of Altassian with this!
- dinkleberg 3y agoI don’t think it is the UI design of atlassian that is bad, but rather the UX and the often slow and janky pages. Nothing wrong with the styling though IMO.
- hknmtt 3y agoI have been always using Foundation CSS over Bootstrap. But this looks good. Although I am now using Quasar which has its own style already. Though quite similar.
- littlecranky67 3y agoNice work! Is this a pure css theme and thus compatible with react-bootstrap?
- __natty__ 3y agoAtlassian design has been the ideal model for enterprise™ design for me. It's like promo videos with smiling people from stock. Look nice and clean but you just feel the rat race behind.
- trollied 3y agoComponents here: https://fastbootstrap.com/components/ https://fastbootstrap.com/components/
- smcleod 3y ago1) Atlassian is known for poor design, 2) There's no screenshots or examples, 3) See 1.
- visarga 3y agohttps://fastbootstrap.com/ https://fastbootstrap.com/
- rglullis 3y agoI don't understand why CSS developers go through all the difficult work (taking a design system, turn into a solid selection of components, implement it using SASS mixins with rules that can abstract browser quirks, variable definitions to make it easy for theme-ing) but then insist on putting all of that available through classes that require me to change all of my HTML and ignore separation of presentation and content. Just give me the SASS mixins!
- hk1337 3y agoIt’s in the src/scss directory but they’re not using that much except overriding bootstrap which has its own. You might find bourbon more useful. https://github.com/twbs/bootstrap/tree/main/scss https://github.com/twbs/bootstrap/tree/main/scss https://www.bourbon.io https://www.bourbon.io
- rglullis 3y agoLast I checked, Bourbon was a bit too low-level for what I wanted. It didn't have implement any type of design system but just gave some basic utilities for those that wanted to build one. What I want is more-or-less what I started doing on https://gitlab.com/mushroomlabs/zenstyles https://gitlab.com/mushroomlabs/zenstyles. I took some of the code from materialize.css and stripped it from anything that depended on javascript and anything that required a specific layout definition. Basically, I wanted something that could work as a "classless CSS" that used the basic building blocks from materialize.css, so that I could use with code that was based on headless-ui components. This approach let me, e.g, use my hub20 checkout component (vue.js) without any styling on its own and let people integrate whatever "theme" they wanted. I only got to implement 2 "zen styles" following this approach (the other is on https://github.com/mushroomlabs/hub20.frontend.app/tree/master/src/assets/sass/paper/mixins https://github.com/mushroomlabs/hub20.frontend.app/tree/mast..., and one day I will get to extract it out and move it to the "zen styles" repo) but it was enough to prove to me that this approach was not only possible but made my work a lot easier.
- dcveloper 3y agoSlightly off topic, I'm surprised why more tool or SaaS vendors don't run as Atlassian apps. It solves so many enterprise gatekeeping issues for most tools: 1. Usually integrated with the Enterprise IDP 2. apps/modules usually are part of the security boundary of Atlassian, meaning little compliance headaches if any. 3. Out of the box scaling of per user licenses since individual apps can't have their own independent user limits, they use the whole Atlassian user count. So, if your customer needs just 10 licenses but their Atlassian suite has 500 users, they must purchase at 500 user cal. 4. Atlassian Jira/Confluence are very sticky at the enterprise level. Yes, teams may move to Gitlab, but most customers prefer to stick to Jira/Confluence.
- _fat_santa 3y agoEasy answer: because you are then beholden to them, same with Salesforce apps or any other "app marketplace". If they decide to change their rules or go out of business, there goes your business with theirs. Not saying SaaS apps shouldn't go in that direction, but it should not be their first play IMHO.
- dcveloper 3y agoFor niche products, I think it makes sense. For example, we had a need for a tool to generate AWS/Azure diagrams automatically. There are a ton of SaaS options in this space, some of which just leverage opensource projects to generate the diagrams. In the gov space, I can't touch it if they aren't FedRAMP'ed. I've gone through that process as a CSP, and it's near a million dollar investment. Or the vendor can just release their product as an Atlassian App and avoid that headache. Yes, you'll never be the next billion dollar SaaS vendor but could you make a 7 figures? I'm confident you could. Rephrased, I think an agency or company that follows the AWS model of "borrowing" open source projects and converting them to a paid service would work would do well. Wrap a open source solution around an Atlassian or similar PaaS app/module.
- jakearmitage 3y agoWe need more of these non-React/Vue/WhateverIsPopularRightNow CSS frameworks. They are great.