# Getting a package adopted... or how to market a package?

**URL:** <https://forum.djangoproject.com/t/getting-a-package-adopted-or-how-to-market-a-package/43222>\
**Category:** Packages\
**Created:** [October 20, 2025, 7:56am UTC](https://forum.djangoproject.com/t/getting-a-package-adopted-or-how-to-market-a-package/43222 "2025-10-20T07:56:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![nanorepublica](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/nanorepublica/32/14211_2.png) [@nanorepublica](https://forum.djangoproject.com/u/nanorepublica)\
**Post date:** [October 20, 2025, 7:56am UTC](https://forum.djangoproject.com/t/getting-a-package-adopted-or-how-to-market-a-package/43222/1 "2025-10-20T07:56:34Z")

</div>

In my bid to get django-prodserver adopted by more people in the community (with the hopeful eventual goal of a merge into core), I started tracking potential marketing tasks as well as development issues.

I have this project to track the marketing side of things: [django-prodserver marketing · GitHub](https://github.com/users/nanorepublica/projects/2)

I’m sharing for few reasons:

1. I haven’t seen this really discussed much in an explicit manner
2. Have I missed any good ideas in my project?
3. Perhaps we as community can produce a bit of a playbook for marketing a package? Not that a playbook would guarantee success, but it would likely lighten the load for future package creators/maintainers.

---

<div class="post-metadata">

**Author:** ![CodenameTim](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/codenametim/32/31507_2.png) [@CodenameTim](https://forum.djangoproject.com/u/CodenameTim)\
**Post date:** [October 20, 2025, 1:58pm UTC](https://forum.djangoproject.com/t/getting-a-package-adopted-or-how-to-market-a-package/43222/2 "2025-10-20T13:58:29Z")

</div>

I don’t have any other marketing ideas at the moment, but I’m definitely in support of a playbook.

---

<div class="post-metadata">

**Author:** ![thibaudcolas](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/thibaudcolas/32/3956_2.png) [@thibaudcolas](https://forum.djangoproject.com/u/thibaudcolas)\
**Post date:** [October 28, 2025, 12:51am UTC](https://forum.djangoproject.com/t/getting-a-package-adopted-or-how-to-market-a-package/43222/3 "2025-10-28T00:51:10Z")

</div>

Things I recommend:

- **A memorable name**
- Good-looking docs. Instantly bumps the trust factor of the package.
- A strong associated emoji. For example Wagtail 🐦, Django 🦄, React ⚛, Python 🐍, Postgres 🐘, etc
- Screenshot in the README. Even for something not particularly visual. It’s just way more memorable. Alternative: a logo of some kind.
- List at least 2-3 prominent / early users in the README, ideally with a link to the project in question
- Social media posts for significant releases (you define significant)
- 2-3 blog posts about the package in action

And last but not least… I wish more packages came with a ready to use demo. Not necessarily as in it has to be live/online, just a `demo` app in the package repo. Where in 2-3 min I can clone; venv; install; manage.py and see something that works, without having to set up the package myself on a project (I’m lazy!)