On #2148255: [meta] Make better D8 api.d.o landing page, linked to high-level overview topics, and put it in Core api.php files, we made a patch that included a stub Topic page for api.drupal.org (i.e., a @defgroup) titled:
Typed Data API
This can be found in file core/modules/system/core.api.php where it says
@defgroup typed_data
The documentation to go on this page needs to be written. The idea is:
a) Write a few paragraphs about the topic.
b) Link to more detailed documentation on
https://drupal.org/developing/api/8
c) If the more detailed documentation does not yet exist, create stub page(s), link to the stub pages, and add a note to this issue stating that the stub pages need to be filled out.
d) If the topic has related classes, interfaces, and functions -- appropriate for an overview -- add
@ingroup typed_data
to their documentation headers. That will make these classes etc. show up on the Topic page on api.drupal.org. Only include classes/functions that are appropriate for an overview page please!
For more info -- documentation standards for @defgroup/@ingroup:
https://drupal.org/coding-standards/docs#defgroup
Comment | File | Size | Author |
---|---|---|---|
#6 | interdiff-4-6.txt | 4.66 KB | jhodgdon |
#6 | interdiff-2-6.txt | 5.23 KB | jhodgdon |
#6 | 2216553-typed-data-docs-6.patch | 13.38 KB | jhodgdon |
#4 | d8_typed_data.patch | 13.43 KB | fago |
#2 | 2216553-typed-data-docs-v1.patch | 8.72 KB | jhodgdon |
Comments
Comment #1
jhodgdonI'm going to give this a shot...
Comment #2
jhodgdonHere's a first pass. The drupal.org page on this is https://drupal.org/node/1794140 .. . I borrowed from that page where I could, but it is fairly sketchy, so I made a lot of stuff up. I hope it's right.
When we get this patch finalized and approved by people who actually know what's going on, it should go into https://drupal.org/node/1794140 (and maybe expanded a little there). This version is supposed to be fairly concise and give an overview only, not all the details.
Comment #3
jhodgdonOne thing (self-review):
This section should have a link to the plugin API topic and the annotation topic. "For more information about plugins, ..." etc.
Comment #4
fagoThanks for the start, I worked over it and adapted it as I think it makes sense. Once we've that finished, I think we should update the docu page based upon it. Updated patch attached.
Comment #5
jhodgdonCan you explain why you made the changes you did to the patch?
For instance, why take out the "... provides a useful starting point" links to the base classes? I think those are useful? And I'm not sure why the list of classes you put @ingroup on has changed so much?
And it needs proofreading... I can do that but I'm not really in favor of many of the changes you made
Comment #6
jhodgdonI read through both proposed patches again, and made a new patch (also rerolled for PSR-4 and other updates, and added links for #3. I think I took the best parts from both patches, and made it even more concise than either previous patch.
I've attached interdiffs -- just for the core.api.php (topic) hunk -- between my patch in #2 and fago's patch in #4 and this new patch.
Comment #7
webchickWhile this has not been formally "signed off" on by the subsystem maintainer yet, a) this is one of the most critical pieces of missing API docs, b) it's been at "needs review" for > 2 weeks, and c) incorporates at least the first round of feedback. Given the above, and the fact that as a docs patch it can't possibly "break" anything, I'm inclined to get this in and do further refinements in follow-up patches.
Committed and pushed to 8.x. Thanks!