Open willbreitkreutz opened 6 months ago
Just thinking through documentation organization based on what you said, Will, this is what I'm envisioning:
<TiInfo />
(or whatever) that takes the disclaimer statement as the prop. This would probably be useful to have as a base component for non-disclaimer uses (with icon/color/size passed as props) as well.Yeah, I think we're on the same page:
- Would this be included on each component/hook page, or would we have a single page for "Disclaimers"?
I'd probably leave this open ended, let the consuming app decide, but reserve the right to be the final judge of if they do a good enough job. Ultimately it's PAO or someone who has that final say, but I feel like since we own the means of production, there should be some perks. (he said to the crowd of pitchforks)
I like the disclaimer / info component idea.
@adamscarberry @jbkolze I think it makes sense for us to build hooks/components for this kind of data, if we don't do it so others follow our lead, then they will just do it themselves in haphazard ways. This comes with a couple considerations though:
<TiInfo />
or other icon that pops up the disclaimer when clicked.Originally posted by @willbreitkreutz in https://github.com/USACE/groundwork/issues/49#issuecomment-2093326612
This issue to track a path forward on this conversation.