-
Notifications
You must be signed in to change notification settings - Fork 86
Closed
Labels
Description
A scaffolded plugin contains a bunch of Grunt tasks which I think are unnecessary and can be removed or replaced.
addtextdomain
Note sure if that one is really needed. There was quite a discussion about that feature in the i18n-command repo. If anything, this could be awp i18n addtextdomaincommand. (See Command to add text domains to i18n functions i18n-command#25)makepot
People can just usewp i18n make-potto generate POT files.wp_readme_to_markdown
I don't see the point in this. If you host your plugin on WordPress.org, you need to adhere to the very specific format forreadme.txt. If you host or develop your plugin on GitHub, you usually have notes for developers, information about the build status, etc. IMHO it makes more sense to have two separate files —readme.txtandreadme.mdwith different information.
Finally, I don't see why Grunt is needed for these simple tasks. Why can't these just be simple scripts in package.json (e.g. "makepot": "wp i18n make-pot ." would be one such script)? One dependency less to worry about.