SOME Forge Modules and Skins are in-fact searchable in the More Extensions feed. It is just hard to see which ones are store and forge (the icons differ, but the icons don't make sense). Also the updates for Forge modules in that feed don't work very well, you can't tell which version of a module is coming from the forge. EX: Search for Form and List and you'll find multiple listings, but good luck figuring out which is the latest one.

---

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions

While I agree that it would be helpful to indicate when extensions are broken or out-of-date, within the Forge, ideally the response would be to help fix it (since it's all OSS).  So, I don't know that hiding or removing it completely is the answer.

 The fact that the module is in the forge should indicate that it is somewhat open to contributions, right?  The reason we have a forge is to support open source.

---

Brian Dukes Engage Software St. Louis, MO 866-907-4002

DNN partner specializing in custom, enterprise DNN development.

What dictates whether a Forge module is shown in the Extensions Feed within DNN? I went searching, for example, for "Chat" and didn't find SignalRChat inside the DNN Extensions Feed

Having those results more mixed, and perhaps marking with color or shape/title to the listing to say whether it's from the Forge or the Store seems like a good idea.

And then for the store elements to the Forge and some Forge elements to the store, I wouldn't recommend necessarily combining the two together. I get the idea for keeping the Forge where it is and separate.

But it seems that both could benefit from some unification in style, layout and some basic features so that there would be a more uniform presentation to admin-level users who can be a crowd that doesn't spend the time to try out or figure out new things within the DNN sites as much. I think that keeping the presentation styles similar would help get them more familiar with the Forge. And I think that some features of how the Forge presents a uniform way of presenting the content of a module description with tabs could be useful for the Store where it's really the wild west of people putting up any variety of style of content.