Repository navigation
build(aio) + docs: miscellaneous updates to the doc-gen - #24000
petebacondarwin wants to merge 21 commits into
Conversation
|
|
|
|
|
You can preview af721ca at https://pr24000-af721ca.ngbuilds.io/. |
gkalpak
left a comment
There was a problem hiding this comment.
Good stuff 💯
(Only some minor comments.)
There was a problem hiding this comment.
While you are at it: Missing period at the end 😁
There was a problem hiding this comment.
This line right below an example sounds weird. Maybe move it above all examples (and change "an example" to "some examples")?
There was a problem hiding this comment.
Having an empty section at the same level as the next one seems odd. Maybe remove this from here (and append "example" in the titles of the sections below)?
There was a problem hiding this comment.
Ohh 😲
(There are files below - e.g. packages/core/src/metadata/di.ts - that use See. Just sayin'... 😛)
There was a problem hiding this comment.
I have updated the others to use @see as well.
There was a problem hiding this comment.
I have unindented the section tag which should now solve this problem.
There was a problem hiding this comment.
The headings for the properties table also uses H3 here.
I guess we could avoid both and use appropriate changes to CSS.
There was a problem hiding this comment.
Actually thinking about this again, I think we should keep H3s here. Although wrapped in a table (for rendering) the semantic meaning is that the name of the option/property is the heading for this section, which describes this option/property.
There was a problem hiding this comment.
Correct. It is not needed. We agreed that the options table was a better representation of decorator doc types.
There was a problem hiding this comment.
Does this need the .no-anchor class (as in decorator.template.html)?
There was a problem hiding this comment.
I think you are right.
There was a problem hiding this comment.
Actually I think that Usage Notes here should perhaps be a H4 since the main heading for this table is the H3 property name.
There was a problem hiding this comment.
Even further I decided that there should be no heading at all in this case!
There was a problem hiding this comment.
And the same for the decorator case.
af721ca to
704ab82
Compare
|
OK I fixed up commits based on all those lovely comments. Thanks @gkalpak
I suggest that we get this merged and fix those in subsequent PRs. |
|
You can preview 704ab82 at https://pr24000-704ab82.ngbuilds.io/. |
|
You can preview d6d73eb at https://pr24000-d6d73eb.ngbuilds.io/. |
|
|
|
I have cleaned up this PR and added commits for the items that Igor requested above. |
|
You can preview 9842371 at https://pr24000-9842371.ngbuilds.io/. |
There was a problem hiding this comment.
Are .api-section and .api-table used anywhere? I couldn't find any occurrences 😕
There was a problem hiding this comment.
weird me neither...
There was a problem hiding this comment.
I'm going to delete this and rename the file to styles/2-layout/_api-pages.scss file
There was a problem hiding this comment.
- There is no test for this conditional 😱
- Under what circumstances can a
dochave no correspondingmoduleDoc? Do you have an example?
There was a problem hiding this comment.
when it is a module? I'll add a test
There was a problem hiding this comment.
page-actions might not be a descriptive name any more 😁
There was a problem hiding this comment.
renamed to github-links
|
You can preview c065871 at https://pr24000-c065871.ngbuilds.io/. |
|
@gkalpak do you have any suggestions for better styling of the GH links on methods and options? |
|
I'm no designer 😛 But I would definitely start at centering them vertically: And I would try out different colors (a dark-ish gray maybe, to make them stand out less): @sjtrimble will definitely have more useful insights than me 😁 |
|
Sounds reasonable. I'll create a new PR after this has merged to try out those ideas. |
|
Coming late to the party - is the thought that the main page source and edit would still be there in addition to the 'individual option' ones? I like @gkalpak idea of having the buttons be more subtle. Would be nice if they turned blue on hover (but without the rounded box border of the current page icons). Aligning the card header content vertically is as intended in the original design - so that's a go from my perspective :) |
Yes that is correct. The "individual option" ones link to the source for those specific items (e.g. the method), whereas the top level on is for the export as a whole (e.g. the class). I have centred and coloured the links as suggested. PTAL |
c065871 to
1b5959c
Compare
|
You can preview 1b5959c at https://pr24000-1b5959c.ngbuilds.io/. |
* Code anchors should inherit the font size from their container * Table headings should align with content PR Close #24000
We should not include the package path in the inherited from heading for decorator API docs PR Close #24000
This change adds Github edit and view links to methods and decorator options. It is possible to add these to properties also but the UI is rather tight as these are displayed in a table. PR Close #24000
This would cause dangling links since the target, being internal, would not exist in the docs. PR Close #24000
This was erroneously committed into master, when it was really only supposed to demo what the pages might look like. PR Close #24000
This commit adds new link disambiguators that mean that more code links can be generated automatically in a sensible way. The best example is the use of properties within class, interface and enum documentation. PR Close #24000
The overview of the decorator options is now a table. The detailed description of each option is now a full section. PR Close #24000
This heading is too high for the section because the method name is a H3 but it cannot be a H4 because usage notes may contain H4 headings. PR Close #24000
* Code anchors should inherit the font size from their container * Table headings should align with content PR Close #24000
We should not include the package path in the inherited from heading for decorator API docs PR Close #24000
This change adds Github edit and view links to methods and decorator options. It is possible to add these to properties also but the UI is rather tight as these are displayed in a table. PR Close #24000
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |



There are quite a lot of commits here but each is fairly self-contained and intuitive.