# Extends existed module? **URL:** \ **Category:** Questions & Answers\ **Created:** [July 2, 2022, 8:08am UTC](https://racket.discourse.group/t/extends-existed-module/1117 "2022-07-02T08:08:02Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![simonls](https://yyz2.discourse-cdn.com/free1/user_avatar/racket.discourse.group/simonls/32/170_2.png) [@simonls](https://racket.discourse.group/u/simonls)\ **Post date:** [July 2, 2022, 12:56pm UTC](https://racket.discourse.group/t/extends-existed-module/1117/4 "2022-07-02T12:56:17Z")
I think a single collection package would work too, if you use `syntax` as collection and then just have a file `a.rkt` in that package. Single/Multi-Collection is orthogonal to Single/Multi-Package, this comment goes into more detail: > [@How to Organize Your Racket Library \[blog\]](https://racket.discourse.group/t/how-to-organize-your-racket-library-blog/717/4): > > I like your post a lot, I think starting out with racket it would have helped me to get up to speed in understanding that package organization strategy. The only thing I would like to state explicitly — because I am unsure that it is conveyed 100% to the reader — is that single-collection vs multi-collection is orthogonal to single-package vs multi-package. You can use them in any combination you like, e.g. in my [define-attributes](https://github.com/SimonLSchlee/define-attributes) package I use single-collection with multiple-package. Sometime… --- _[View the full topic](https://racket.discourse.group/t/extends-existed-module/1117)._