[Django] #33615: Add RestApi and Graphql Section in Django Docs
Django
-------------------------------------+-------------------------------------
Reporter: Nasir | Owner: nobody
Iqbal |
Type: | Status: assigned
Cleanup/optimization |
Component: | Version: 4.0
Documentation |
Severity: Normal | Keywords: docs drf,api,
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 1 |
-------------------------------------+-------------------------------------
I feel like the web has come a long way from just being static HTML pages
that we can manipulate using serverside languages and frameworks like
Python and Django. nowadays most of the projects are single-page
applications that consist of a separate frontend (ReactJS, VueJs, etc) and
a backend (Django, FastApi, Flask, etc) but the main Django project is
still focused on Server-side rendering of HTML .so why my proposal is that
we should mention djangorestframework.org and other packages like drf on
the main Django documentation so it is easy for beginners to get started
with Django to make awesome Apis and the same goes graphql with Django
using Graphene
--
Ticket URL: <https://code.djangoproject.com/ticket/33615>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
-------------------------------------+-------------------------------------
Type: | Status: assigned
Cleanup/optimization |
Component: Documentation | Version: 4.0
Severity: Normal | Resolution:
Keywords: docs drf,api, | Triage Stage:
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 1
-------------------------------------+-------------------------------------
Old description:
> I feel like the web has come a long way from just being static HTML pages
> that we can manipulate using serverside languages and frameworks like
> Python and Django. nowadays most of the projects are single-page
> applications that consist of a separate frontend (ReactJS, VueJs, etc)
> and a backend (Django, FastApi, Flask, etc) but the main Django project
> is still focused on Server-side rendering of HTML .so why my proposal is
> that we should mention djangorestframework.org and other packages like
> drf on the main Django documentation so it is easy for beginners to get
> started with Django to make awesome Apis and the same goes graphql with
> Django using Graphene
New description:
I feel like the web has come a long way from just being static HTML pages
that we can manipulate using serverside languages and frameworks like
Python and Django. nowadays most of the projects are single-page
applications that consist of a separate frontend (ReactJS, VueJs, etc) and
a backend (Django, FastApi, Flask, etc) but the main Django project is
still focused on Server-side rendering of HTML .so why my proposal is that
we should mention djangorestframework.org and other packages like DRF on
the main Django documentation so it is easy for beginners to get started
with Django to make awesome Apis and the same goes Graphql with Django
using Graphene . I would love to hear your guys' opinions on it and would
love to contribute to it as well Thanks.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/33615#comment:1>
Django
-------------------------------------+-------------------------------------
Reporter: Nasir Iqbal | Owner: nobody
Cleanup/optimization |
Component: Documentation | Version: 4.0
Keywords: docs drf,api, | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: assigned => closed
* ui_ux: 1 => 0
* resolution: => duplicate
* easy: 1 => 0
Comment:
IMO, it's a duplicate of #30296.
--
Ticket URL: <https://code.djangoproject.com/ticket/33615#comment:2>