Manny Carrera
435 posts

Manny Carrera
@mcarrera4
Software Development Engineer @workday
Boulder, CO Katılım Eylül 2012
611 Takip Edilen164 Takipçiler

@marvelousmudd Ah yep! I think the problem we’re having is storybook is too feature rich and hard to maintain. I’ve heard of Ladle and it looks great!
English

@mcarrera4 Storybook. From what I can tell, it's still the best.
Uber released Ladle a while back, and while it still looks like it's being actively developed, it's nowhere near as feature-rich as Storybook.
github.com/tajo/ladle
English

This makes me miss my friends @jwage @ccovey14 @mcarrera4 @rishinaama. Let's throw things from high places again soon... and drink garage beers 🍻
English

@jwage Sadly I think it’s true. This has happened quite a bit since @mcarrera4 had his wreck. The “warranty fix” has always just been a bandaid 😆
English

@jwage I went on my first bike ride today in a long time… and then my bike broke. Had to walk all the way home. Womp womp 🤣🙃
English

@MetalHaze @docusaurus This is great insight! Appreciate the feedback!
English

@mcarrera4 @docusaurus But there is no “right way”. What works for one person may not work for somebody else so you really to take a look at the business how it operates and what ppl expect. Your coworkers are your users so you might want to send out a survey and do internal user research asking this
English

This is a long shot, curious if anyone has switched to using @docusaurus after developing/documenting in Storybook. Specifically when managing a mono repo or component library!
English

@donniedamato @docusaurus Yeah good point! Thanks for the input!!
English

@mcarrera4 @docusaurus Sure, but they also have the resources to put into custom docs sites. It's possible to customize Storybook to make finding info + code better too but then you're customizing again. For us, we want as much as we can in one place, not strewn across different platforms.
English

@donniedamato @docusaurus Fair point. It should feel integrated. I look at Material or Atlassian as examples and they have dev specific + design docs that feel congruent. The experience as well of finding the info + code blocks feels seamless.
English

@mcarrera4 @docusaurus How should a docs site feel?
English

@donniedamato @docusaurus Good point! Yeah SB and MDX have worked out for the most part except SB doesn't feel like a doc site!
English

@mcarrera4 @docusaurus We're winding it back. We've been using docusaurus with an attempt that the design org would also contribute but the config was not clear. If you lean into Storybook and MDX, I find it to be more approachable. But best case is file based routing Markdown.
English

@MetalHaze @docusaurus Gotcha! Do you find it hard to manage documentation in two different spots? I guess part of it is dev specific and the other part is a little more broad. Was curious about using docusaurus for a dev specific site without having two different repos.
English

@mcarrera4 @docusaurus Yah, so we don’t document guidance and best practices in SB. It doesn’t act great as an authoring platform. It’s only for technical docs and testing. We store the other documentation in Confluence and cross-reference. In your case it sounds like that would be Docusaurus.
English

@MetalHaze @docusaurus Hey Alex! We're running into an issue where documenting in SB isn't ideal. We also have an ecosystem where a lot of info gets lost. I think SB is great for developing in isolation, but we really need to combine code and docs better!
English

@mcarrera4 @docusaurus We use both in our company for different reasons. Depends what your goals are. Docusaurus doesn’t do many of the things SB offers. And while SB is great, it can be clunky and difficult to work with.
English

Hey @Ionicframework! I'm a design systems engineer at @Workday ! Any chance I can ask a few questions regarding your experience documenting with @docusaurus ?!
English



