One area I'd love to see Tailwind tackle is better targeting for child elements. I understand the library is functional and the classes are atomic, but I think being able to chain and target arbitrary children elements would be quite powerful.
575 karma · joined October 26, 2015
One area I'd love to see Tailwind tackle is better targeting for child elements. I understand the library is functional and the classes are atomic, but I think being able to chain and target arbitrary children elements would be quite powerful.
SailPoint is the fastest-growing, independent identity and access management (IAM) provider, SailPoint helps hundreds of global organizations securely and effectively deliver and manage user access from any device to data and applications residing in the data center, on mobile devices, and in the cloud.
We are currently building out a brand new SaaS Analytics / Big Data product, and we need more UI engineers to help us build it out. This is a unique opportunity to build something from scratch but have the backing of an organization that has the muscle to take it to market quickly, with a very satisfied customer base.
Our Product Stack: AWS, ElasticSearch, DynamoDB, Java, Groovy, Scala, Flink, TypeScript, Angular (4), RxJS, NgRx, D3
More info on working @ SailPoint: https://www.sailpoint.com/company/careers/
UI Engineer Job Post: https://sailpoint.wd1.myworkdayjobs.com/en-US/SailPoint/job/...
You can apply from the Job Post linked above. You can email me nicholas.mitchell@sailpoint.com for any further inquiries. Thanks!
Why are people porting apps to a framework that is a few days old?
I find it very difficult to believe that your app, with it's 50% size decrease, has any more complexity than a todo app.
Just, why?
Could you elaborate on what extra things you'd like react to do for you?
Great work, this is super cool!
The tool does enforce and encourage atomic design architecture when it comes to HTML. At best, I'd describe Fabricator as a static-site/documentation generator. However, I wouldn't recommend using it Fabricator to generate documentation in the 'toolkit' way that's recommended in it the docs because it tightly couples that static site/documentation generation to UI library source. There are plenty of static site generators that work well for generating docs that I'd rather use (jekyll, hugo, etc).
I'd encourage developers considering Fabricator to proceed with caution. Although, it boasts ease of UI development based on atomic designs, the tool does not aide in code modularity or UI component re-usablity.
Is anyone else on iOS safari able use their nav?