-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automatically add scss file and documentation when generating a component #40
Comments
I understand but I'm not sure it's a good idea. First of all because with the linter, an empty file is not possible, that's why I used a comment in the tikui.scss file. And also because the CSS is the thing that people will make using the tool but the html is the thing used to document, so, it may not be a problem to have a structure for the documentation but not for the CSS. Don't hesitate to answer this ;) |
Hum I answer on the bad issue for the previous comment. But I think it's not easy to understand the structure the users want to add the componentDoc or templateDoc. |
ideas:
Otherwise, I think using Tikui for the first time is a bit tricky |
I let you suggest a PR for the simplest option you see (if you have an idea) . But you need to keep in mind that it's not because the generation is using an atomic design structure that people are forced to use this structure (if they don't want/need). |
yes even if tikui-cli is already generating an atomic design structure 😛 |
For instance, when creating
buttom
insrc/atom
, is there any reason not to add:include:componentDoc(height=55) button/button.md
insrc/atom/atom.pug
@import 'button/button';
insrc/atom/_atom.scss
?
This would speed up development and help newbies :)
The text was updated successfully, but these errors were encountered: