pimoore
pimoore

@manton Is there a way to add the version number to display for each installed plugin on the directory page? Right now verifying the version requires going into Design and Custom Themes, clicking on the plugin itself, and then opening the plugin.json file.

|
Embed
manton
manton

@pimoore Good idea, I'll add that.

|
Embed
pimoore
pimoore

@manton πŸŽ‰ πŸ‘πŸ»

|
Embed
sod
sod

@manton @pimoore Love this! Another thing I've noticed for my plug-ins is that people miss there's documentation available over at GitHub. Which I don't blame them for. 😊

What if developers could add additional links below the plug-in description? Like "installation instructions", "documentation", or "support". Something like this:

Screenshot of plug-in card with additional links: Source Code and User Guide.

|
Embed
pimoore
pimoore

@sod @manton +1 to this idea!

|
Embed
manton
manton

@sod @pimoore That would be great! Maybe an extra field in plugin.json? I like your mockup.

|
Embed
skoobz
skoobz

@sod I support this idea.

|
Embed
amit
amit

@manton @sod @pimoore +1 Exactly what I was thinking today. Just checking, would it be too difficult to display the README contents on the individual plugin page?

|
Embed
manton
manton

@amit @sod @pimoore Yeah, I was thinking about displaying the README when I added the plug-in "detail" pages recently. Could still do that.

|
Embed
sod
sod

@amit @manton @pimoore I don't know if it's easy or not, but I do like the idea. 😊 It's a common pattern to use files like README.md, CHANGELOG.md, and INSTALL.md and show them in user-facing directories. Nova Extensions is one example, Atom Packages another.

|
Embed
pimoore
pimoore

@manton @sod @amit Perhaps it’s best to leave it to only display if clicked on, otherwise it would make scrolling the plugin directory cumbersome?

|
Embed
amit
amit

@pimoore I was suggesting on the details page, not on the directory. I agree, the later won't be useful.

|
Embed