174 results found
-
make it possible to publish html source at README
right now if i post an HTML source, even with #HTML on top of it it parses it instead of publishing it
3 votes -
write a documentation for the possible markup for README files
i would love to have a documentation for the possible markups i could use for README.rm and how it would look at the forge
2 votes -
make it possible to download dependancy build
I suggest that it would be possible to download a build containing the JS classes the plugin is dependent on.
so for example, if my plugin is dependent on Element, Fx.Tweem and Request.JSON, i can download a file that contains just them and their dependencies.
i know this is probably quite hard, but it's gonna be ultra cool if this was possible7 votesIn da works!
-
fix that i cant post my screenshots
i've uploaded 2 plugins with a readme.md by the same format that is specified in the docs. they both have a screenshot, and both show them at github, but non work at the forge - they both show no screenshot.
the README.md locaions:
http://github.com/arieh/ThumbsSlides/blob/master/README.mdhttp://github.com/arieh/MooTreeAcordion/blob/master/README.md
and the projects URL (accordingly):
http://mootools.net/forge/p/thumbsslides
http://mootools.net/forge/p/mootreeacordion0 votes -
Implement Disqus on single plugin page
It shouldn't take more than 20 minutes
54 votesWill add `reviews` instead of comments, similar to the Apple store. Reviews will support comments as well.
-
Fix IE6 errors
On the forge main page:
Line 9: Expected identifier, string or number
Line 213 : Object doesn’t support this property or method
3 votes -
Alert dev that don't have github issues enabled
Github "issues" is toggleable so repos may not have them. If a repo doesn't have them PluginsKit should let them know or else the "issues" link in the plugin repo is broken.
1 vote -
Make having a working demo mandatory for plugins
To help users understand the implementation of the plugins I would have thought that having a working demo (eg in mooshell) ought to be mandatory.
4 votesWe’re integrating mooshell to make adding demos much easier.
-
Add powered by PluginsKit
You should put a badge that says powered by PluginsKit so devs know what powers this awesome repo http://github.com/Guille/PluginsKit
1 vote -
refresh after update
I noticed in the video after the dev updates his plugin from gist, he had to press F5 to refresh the page. You might have the page auto refresh after the upload, and parsing is done, or turn that into an ajax call to do so.
5 votesWill do automatic refresh or display a link.
-
Recommend similar plugins
By measuring user-downloads and grouping the downloads, it should be possible to show similar plugins (since users tend to download multiple plugins to solve one problem). A approach with better results would be a i-use-this/watch-this implementation, but resultsets from downloads should be ok.
I can help with the implementation, similar implementations I did brought awesome results on even small data sets (based on I-like-this voting)
13 votes -
Links between plugins
Since plugin names are unique, mentions in documentation could be linked. Like "It implements dbug notice wrong usage" … dbug would link to the plugin page. Or "works great with FancyUpload to preview images" … etc. Makes a more seamless browsing experience.
2 votesWill implement.
-
Code-focussed Github integration
Consists of 2 parts:
1) Simple: RSS feed for commits and tickets integrated into the plugin-site.
2) Connected: Connect your github account to the forge and fork/watch a plugin-repository with one click in the forge UI.
2 votesExcellent suggestions
-
Add "date added" and "last updated" to the plugin details
It's good to know how active the development on a plugin is. A date on each release would also be great.
21 votesWill add
- Don't see your idea?