I reverted Casemon's edit here. As the rollback feature doesn't allow me to enter an explanation, I'll do so here. The page differentiates between .NET plugins and native code plugins. The former kind can be used in web players and the latter can't.
--NCarter 02:50, 14 February 2009 (PST)
Do .NET plugins work for the webplayer too? --AnomalousUnderdog 21:14, 1 April 2010 (PDT)
Retro fit with tabs
I'll be adding a slight retro fit to this page to include tabs like the Scripts page. It will contain 3 tabs ...
Containing the existing .net/native plugins content.
Extension Methods tab
Will contain links to pages that contain extension method code. This section is intended to aggregate all of the extension methods in one place and I think fits in with the "Extensions" link of the navigation side bar for the UnifyCommunity site.
I feel placing extension methods inline within one of the tabs on the Scripts page is not the right fit as "Scripts" infers scripting/game related logic or editor tool functionality and not necessarily specific to extending functionality of a specific type like a extension method does. This will provide a centralized place for listing links to pages containing extension methods. (Even though it initially appears there are only about 5 extension methods QQ)
The Scripts pages, given there current layout, are a decent but can be difficult to find what you are looking for as it feels like reading a big wall of text. tldr
The packages tab intends to provide links to *.unitypackage downloads from across the web that are not available in the unity asset store. I frequently come across blogs that provide free .unitypackage files for download but are not available on the asset store either because the author did not submit them, or the nature of the package would not satisfy acceptance to the unity asset store by the unity team.
This will provide a place for the community to link to packages out on the web that otherwise would not get discovered. Not everyone who provides a package for download on there blog or website will make the effort to post or link to there package here on the unify community.
To get the ball rolling I have included a link to my CBX.GeneralTools page containing a package download link and placed it under the "Editor Extensions" section mirroring that of the unity asset stores main categories. As additional packages are added they too should be organized under the unity asset store category structure to maintain familiarity and consistency for users to search through.