You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each component has some intrinsic features and behaviours.
In special cases or in combination with certain other components it's likely that layout, measurements and other stuff may change.
Concrete examples are the mobile menu (which triggers an unrelated DOM tree from within another component) or the various variations of the footer.
Those intrinsic features and behaviours are reflected by code, either as html, in css or through js. So I don't think that we need to document the related stuff in all code, but we need to find an easy way to do it and make it parseable.
Each component has some intrinsic features and behaviours.
In special cases or in combination with certain other components it's likely that layout, measurements and other stuff may change.
Concrete examples are the mobile menu (which triggers an unrelated DOM tree from within another component) or the various variations of the footer.
Those intrinsic features and behaviours are reflected by code, either as
html
, incss
or throughjs
. So I don't think that we need to document the related stuff in all code, but we need to find an easy way to do it and make it parseable.Regarding JS i would use awesome
@JSdoc
doclets.And for SCSS I would use awesome
@sassdoc
docletsThe text was updated successfully, but these errors were encountered: