Welcome to djangodb.org: the place to share your Django data models. With the popularity of django on the rise, we felt that a way to share the data model - the foundation of a django application - would be a worthwhile contribution.
Whilst the functionality that you wish to develop in your app may be completely unique, your base data model may be exactly the same as countless others - so why not share yours, or use existing code?
By reusing an existing data model, you not only save time, you also will encourage a level of cross application compatibility. I mean, how many times has the Company/Employee data model been written? (I have posted my own basic one on this site to get us started!). What if the common datamodels were already defined - and were known to work with other django apps?
Then you'd have a big building block in the ecosystem in place. (mixed metaphor anyone?)
djangodb is dedicated to creating this type of ecosystem for the django community. If you are seeking whole applets, or snippets of code, then there are better places than here (such as James Bennett's excellent djangosnippets or Bryan Veloso's djangopluggables). But if you want to share your data model, see how others may have solved your problem, or just learn... this is the place.
As contributed data models mature, we will introduce a a versioning system and a compatibility test that will ensure your app is compliant to "version x" of a data model. This should ensure that apps that share models do so in a non-disruptive way.
Shortly we will be introducing a easier way to submit models too; rather than the current hand pasting them method we are considering an an alternative submission process where your models are more simply posted and then formatted nicely.
(Oh yes- apologies for hosting this site in php - we hope to change this soon!)
Whilst the functionality that you wish to develop in your app may be completely unique, your base data model may be exactly the same as countless others - so why not share yours, or use existing code?
By reusing an existing data model, you not only save time, you also will encourage a level of cross application compatibility. I mean, how many times has the Company/Employee data model been written? (I have posted my own basic one on this site to get us started!). What if the common datamodels were already defined - and were known to work with other django apps?
Then you'd have a big building block in the ecosystem in place. (mixed metaphor anyone?)
djangodb is dedicated to creating this type of ecosystem for the django community. If you are seeking whole applets, or snippets of code, then there are better places than here (such as James Bennett's excellent djangosnippets or Bryan Veloso's djangopluggables). But if you want to share your data model, see how others may have solved your problem, or just learn... this is the place.
As contributed data models mature, we will introduce a a versioning system and a compatibility test that will ensure your app is compliant to "version x" of a data model. This should ensure that apps that share models do so in a non-disruptive way.
Shortly we will be introducing a easier way to submit models too; rather than the current hand pasting them method we are considering an an alternative submission process where your models are more simply posted and then formatted nicely.
(Oh yes- apologies for hosting this site in php - we hope to change this soon!)
Enough: on with the show...

