Replies: 2 comments
-
Data from the current Introduction page that would make a good start to an Architecture page:
Then explain that all of those would be rows in the Package table.
This is great info for the Platforms page #911 Maybe #911 would make a good subpage for this page? This info on Grids would be great for an Architecture page, too. And the explanation would benefit from some examples -- a lot of the data on the site is stable enough that I think you could use live links in your docs to illustrate your point, if you wanted to. |
Beta Was this translation helpful? Give feedback.
-
@williln just noting that I moved the docs issues to discussions to free up some mental space. When I scan open issues it feels like bugs vs. improvements, but I plan to keep working on these. |
Beta Was this translation helpful? Give feedback.
-
Is your feature request related to a problem? Please describe.
Django Packages depends mainly on the relationship between Packages and Grids, if I am interpreting our conversations correctly @jefftriplett:
So I think it would be a good idea to collect the explanation of these core concepts in its own section of the docs. Especially since the kinds of contributions you tend to receive, and seek, are contributions that deal a lot with these models.
Describe the solution you'd like
Something similar to (but probably much simpler than) how Wagtail goes into their Page model:
That's a core concept that everyone who works with Wagtail will need to deal with, so they spend extra time making sure it's clear how that works. Something similar for how Packages and Grids work would be good.
Describe alternatives you've considered
None yet.
Additional context
None yet.
Beta Was this translation helpful? Give feedback.
All reactions