- AdvSearch
- cookieJar
- getYoutube
- aliasid
- AddHeaderfiles
- AjaxUpload
- amazonSES mailing list
- Analytics
- Archivist
- Articles
- Babel
- BannerX
- BannerY
- Batcher
- bdListings
- boilerX
- BreadCrumb
- Breadcrumbs
- BxrExtra
- cachebuster
- CamperManagement
- Church Events Calendar
- Cliche
- ClientConfig
- CMPGenerator
- Collections
- ContextRouter
- CookieList
- CronManager
- cssSweet
- CustomUrls
- Databackup
- Discuss
- DitsNews
- Eletters
- EventManager
- eventsCalendar2
- EventsX
- ExerPlan
- fastField
- FileDownload R
- FileLister
- FirstChildRedirect
- Flexibility
- ForcedPasswdChange
- FormIt
- FormIt2db
- FormitFastPack
- FormSave
- FoundationX
- FX2themebase
- Gallery
- GatewayManager
- gCal
- getDate
- getFeed
- getPage
- getRelated
- getResourceField
- getResources
- getUrlParam
- getRTImages
- getVimeo
- GoogleSiteMap
- GridClassKey
- HandyMan
- Hits
- HitsPage
- HybridAuth
- If
- Image+
- imageHERE
- ImageStyles
- ImportX
- LexRating
- Lingua
- Login
- Loginza
- mChimpX
- MetaX
- mhPayPal
-
MIGX
- MIGX.Backend-Usage
- MIGX.Data-Entry
- MIGX.Frontend-Usage
-
MIGX.Tutorials
- MIGX.Fancybox-images with seperate placeholders in Richtext-Content
- MIGX.Simple opening hours table
- Using resource-specific mediasource and multifile-uploader with MIGX
- MIGX.Varying layout-boxes
- Creating Selectable and Sortable lists for MIGX
- MIGX.sortable resourcelist
- Using resource-specific mediasource and multifile-uploader with MIGX
- MIGX.Using Grid Inline Editing
- MIGXdb
- MinifyX
- miniShop
- modActiveDirectory
- ModDef
- modExtra
- modMobile
- modSwiftMailer
- mxCalendar
- mxExtendedMenu
- mxFormBuilder
- mxHasTvs
- MoneyBird
- ObfuscateEmail-Revo
- PackMan
- PageBreaker
- Peoples
- PHP Tidy (plugin)
- phpThumbOf
- Polls
- POI Manager
- QuickCrumbs
- Quip
- Rampart
- Redirector
- renderResources
- ResourceWatcher
- RezImgCrop
- Rowboat
- sekFancyBox
- sekFormTools
- sekSiteTools
-
sekUserGalleries
- sekUserGalleries.album.items.helper
- sekUserGalleries.album.items.manage
- sekUserGalleries.album.manage
- sekUserGalleries.album.view
- sekUserGalleries.browse.galleries
- sekUserGalleries.directory
- sekUserGalleries.image.information
- sekUserGalleries.search
- sekUserGalleries.users.gallery.manage
- sekUserGalleries.users.gallery.view
- selfLink
- Shopkeeper
- siblingNav
- SimpleSearch
- SiteEditor
- sitemapFriend
- Slideshow Manager
- sLink
- SmartOptimizer
- SmartTag
- StatCache
- SocialLogin
- SocialSuite
- spieFeed
- StaticSaver
- StoreLocator
- SubscribeMe
- SyntaxChecker
- Tagger
- TaggingAtoZ
- tagLister
- TinyMCE
- Upload to Users CMP
- VersionX
- virtuNewsletter
- VisionCart
- Wayfinder
- xFPC
Discuss.Contributing
This is a user-contributed Extra. If you find issues or would like more info or help, please contact the author.
Discuss is maintained on Github, at http://github.com/modxcms/Discuss.
Branching Strategy
Discuss follows the general guidelines of MODX 'A GitHub-based branching strategy for collaborative development'
When contributing to Discuss, please keep the following branching strategy in mind:
- The main branch to work against is the develop branch.
- The main branch for the MODX forums and its custom theme is theme-modx
- Specific new features or bugfixes should be developed in a feature branch (eg feature-livechat or bug-3532), and merged to develop when done and tested.
It is important to differentiate between the core of discuss, and themes. All discuss core changes should always be done against the develop branch and never against release, theme, or master branches; this changed on 16th of July 2013. Basically every theme branch should be a fork of the core (release) branch and be updated with that regularly through a merge.
Suggest an edit to this page on GitHub (Requires GitHub account. Opens a new window/tab).