Yes, we have the Plugin repository, but we don’t always need to use a plugin for menial tasks. What would be great is tapping into a script repository for simple installations of scripts to be used. WordPress already comes bundled with plenty, although I am talking more about those cool scripts you find on sites like CodePen, JSFiddle, and Codrops.
Imagine a plugin and script repository working side by side.
Read-only archive: https://petitions.classicpress.net/posts/143/a-secondary-repository-for-open-source-scripts
Author: Damian Baker
Vote count: 11
Thanks for your feedback on this petition. I agree that open-source scripts should be kept as that and not pluginified. It also gives script authors a chance to promote their scripts, maybe even earn some income for their premium editions.
I am all for it.
~ posted by Damian Baker
Do you mean a repository or a directory? I ask because, although I use a ton of open source scripts and never use a plugin (if there is one) that claims to WP-ify them, I find that almost all the ones I use need significant modification. Sometimes this is because they are old; sometimes it’s because they have a bug; sometimes it’s because they don’t cater for accessibility requirements.
I’d be reluctant to see CP maintaining a repository of scripts, because a repo (to me, at least) implies some degree of vetting, and such scripts should never be allowed in. A directory, on the other hand, simply provides an easy means of locating scripts that might be useful. I could get behind that – but that isn’t a repo.
~ posted by Tim Kaye
This is a great idea.
@Tim Kaye, I hope I’m not rude in saying I don’t agree with your definition of repository, althogh I understand what you mean. According to WikiPedia ( What is a Repository? | Webopedia)…Generically refers to a central place where data is stored and maintained. A repository can be a place where multiple databases or files are located for distribution over a network, or a repository can be a location that is directly accessible to the user without having to travel across a network.
So “repository” would/should be the correct name, but with your form of configuring that repo.
~ posted by hyperclock
Either repository or directory would do. The concept I think would be like creating a subdirectory within ClassicPress Research Github where open source scripts could be published that can be used for CP, like script to send email using SMTP to use an external email server rather using own server, change email from email and from name, limit access to admin/dashboard for particular roles, create a custom post type, example use cases for $wpdb. I know there are a lot of it found in the web. But a directory within CP, that I would definitely use and hopefully help improve as well.
~ posted by Raymund
Why wouldn’t these just be written as small, focused plugins?
Edit: also, if you’re modifying the site’s code, this should be done by modifying the site’s code. The existing plugin and theme editors are the bane of developers everywhere, and I wish we could delete them rather than expanding them even further.
~ posted by James Nylen
I was using a lot of plugins before. Then, I converted most of them to scripts on my own mu-plugin to have same funtionalities but not using a lot of plugins, mostly so I am aware of the exact scripts running, and avoid vulnerabilities from third party plugins. Also, make the app more lightweight.
~ posted by Raymund
Then, I converted most of them to scripts on my own mu-plugin
Yes, this is also a good approach. I don’t understand what a script repository would gain over having small plugins or incorporating the code you want into a mu-plugin.
If you’re just looking for the code snippets themselves, then it’s pretty hard to beat
https://wordpress.stackexchange.com/. It’s got code, discussion, and reviews of each potential answer.
~ posted by James Nylen
Is the idea here is create a categorized, moderately-vetted list of snippets where people could go to copy code that they would otherwise have to find elsewhere? If so, I can see some value in that versus searching stackexchange/gist/etc. But if it’s not categorized, attributed, and at least somewhat vetted, I don’t see the point.
Also, +1 for deleting the plugin and theme editors.
~ posted by Wells
When using CP for informational or brochure type sites, no problems using plugins. But when creating web applications that gathers names, addresses or other user info, code snippets would be better, especially low-code. This is so the developer implementing can do code review and make his own changes without having to browse the entire lines of the plugin. Just a simple functionality per code snippet.
~ posted by Raymund
I have done something along these lines with Classic Commerce snippets here,
Snippets – Classic Commerce ; I decided to use gist for storing the code.
I would class this as a “categorized, moderately-vetted list” since I have tested them all with Classic Commerce. I do think that having them presented in some form of list or index makes them much more accessible.
~ posted by Alan Coggins
Update to the above
@ozfiddler has done a brilliant job of creating a “library” of code snippets specifically for Classic Commerce (link above). Since the above petition was created, the library has expanded to nearly 100 snippets.
In addition, we now have a
Classic Code Snippets research plugin which builds on the SC Display Code plugin originally created by ozfiddler. All being well, this will become an official ClassicPress plugin in the not too distant future.
Downvote from me.
For those who prefer to not install traditional plugins and would instead prefer installing random scripts as mu-plugins or utility plugins, the right path (IMO) is maintaining such a list oneself. Or, better yet, put together a site (like what CC did) and list them there as a user-managed community resource.
This petition is moving to “planned” status because
we are working on implementing a snippet repository, which will be part of the main directory.
This petition will be marked completed and closed, the work on the snippet library is underway.
Originally published at:
Plugin/Theme Directory Moving to ClassicPress | ClassicPress
As we transition to the new leadership, we are beginning to work on improving our infrastructure. That includes the plugin/theme directory. The current directory was built using Laravel, a great PHP framework. It served its purpose of allowing us to begin accepting plugins. Unfortunately, we don’t have anyone with Laravel experience to continue improving and…
This topic was automatically closed after 3 days. New replies are no longer allowed.