django-jedminson
Opinionated JSON Schema form field for Django admin, powered by Jedison.
For configuration that lives in a JSONField, Jedminson gives you an admin form
with familiar controls and collapsible fieldsets. Define the data with JSON Schema,
choose a layout if you need one, and let Python validate what gets submitted.
Installation
Requires Python 3.10+ and Django 5.2+.
python -m pip install django-jedminson
Add jedminson to INSTALLED_APPS alongside your Django admin apps. Serve its
static files through your usual setup, including collectstatic for deployment.
JavaScript and CSS are included in the release archives; no frontend build is
needed to use the package.
Quick start
Here's a configuration with a URL and an enabled flag. Start with a normal model
JSONField in your app's models.py:
from django.db import models
class Integration(models.Model):
name = models.CharField(max_length=100)
config = models.JSONField(default=dict, blank=True)
def __str__(self):
return self.name
Give it a schema in forms.py:
from jedminson.forms import JSONSchemaField, JedminsonModelForm
from .models import Integration
class IntegrationForm(JedminsonModelForm):
config = JSONSchemaField(schema={
'type': 'object',
'properties': {
'url': {'type': 'string', 'title': 'URL', 'minLength': 1},
'enabled': {'type': 'boolean', 'title': 'Enabled', 'default': True},
},
'required': ['url'],
})
class Meta:
model = Integration
fields = ['name', 'config']
Then register the form in admin.py:
from django.contrib import admin
from .forms import IntegrationForm
from .models import Integration
@admin.register(Integration)
class IntegrationAdmin(admin.ModelAdmin):
form = IntegrationForm
Use JedminsonModelForm so the widget receives bound values and validation errors.
Keep blank=True on the model field so empty JSON containers reach schema
validation. Your schema decides whether they're valid; model constraints still
apply.
Controlling the layout
display is optional. Leave it out and fields follow the schema's property order.
To group the two fields above, add this argument to JSONSchemaField:
display=[{
'type': 'fieldset',
'title': 'Connection',
'collapsible': 'open',
'fields': [{'path': '/url'}, {'path': '/enabled'}],
}]
The schema describes the data and its validation. display controls where the
fields go, without changing that schema.
Current scope
Version 0.1.0 is Beta and supports stock Django admin. It handles scalar fields, objects, nested arrays and conditional fields.
Not every valid JSON Schema can be rendered. Avoid unusual property names for now:
Jedison has known path and HTML-ID collisions with names such as a/b, a.b and
empty strings, which can affect editing, error placement and focus.
Metadata
Release files for django-jedminson 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| django_jedminson-0.1.0.tar.gz | 90.7 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_jedminson-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 152.8 kB
Release files / django_jedminson-0.1.0.tar.gz
| Download URL | django_jedminson-0.1.0.tar.gz |
|---|---|
| Size | 90.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
48016ae316b83730f7c3cb229eda28a9ca55e8bca0391185b2e278c3014a4e11
|
|
BLAKE2b-256 checksum How to use checksums |
59726cd363e001f470fa68c3b69cea7b75037760ee6e8b63f3e26d4bed80147e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.
Transparency logRelease files / django_jedminson-0.1.0-py3-none-any.whl
| Download URL | django_jedminson-0.1.0-py3-none-any.whl |
|---|---|
| Size | 62.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
04b6760f4351a48dbac05c1416ef9cf9ec4ccef3a34f8a6a6a86454f27546a90
|
|
BLAKE2b-256 checksum How to use checksums |
b011e107b4d429475259a21a809e21290aeae862301163400d84f34810d83065
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.
Transparency logSecurity for django-jedminson 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for django_jedminson-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.