-
-
Notifications
You must be signed in to change notification settings - Fork 154
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
possibly some enhancements to the resource registry documentation #182
Conversation
on top of Plone. There are so many different kind of resources like widgets, design styles, | ||
behavior logic and single page apps. In order to organize them we are using two | ||
main standard technologies: require.js and less. | ||
Resources are JavaScript, CSS or LESS resources and their dependencies. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Resources are .... LESS resources" can this second resources be changed to something else? files maybe?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AFAIK, in the resource registry only JavaScript, CSS and LESS are managed at the moment. Plain files can still be referenced in CSS/LESS/JS via static or resource directories.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's possible to use references to folders for requirejs imports
Thanks @thet for reviewing the documentation ! |
ping. that's not fully merged. i think my other two commits make sense. |
What's up with this one here? ping @thet @svx @polyester |
Needs to be hand-merged, and please please please: use semantic linebreaks, do not break lines arbitrarily in the middle of a sentence. Ideally we should see if this enhances or contradicts what we are saying in other places:
I'm not qualified enough (yet) to check if we are using consistent terminology in all of these. I know this may sound pedantic, but now is the time to settle on a consistent terminology (even defining some of them in the glossary at https://raw.githubusercontent.com/plone/documentation/5.0/appendices/glossary.rst ) |
replaced by: #397 |
@bloodbare @svx