doc: update synopsis, toc, other nits#6167
Conversation
|
LGTM |
|
Hmm, looks like I wasn't quite accurate with those shots. The lines do have the same relative margin on both sides in the sidebar. |
|
👍 |
doc/api/_toc.markdown
Outdated
There was a problem hiding this comment.
I'm not sure about that
- That file is not a synopsis of anything.
- Example doesn't really describe much.
What about "Hello World" or "Usage" or something like that?
|
Two nits, generally LGTM |
doc/template.html
Outdated
There was a problem hiding this comment.
It would be more appropriate to be NODE(1).
There was a problem hiding this comment.
nm. wasn't paying attention to what file this was located in. our man page should be NODE(1), but this looks good.
There was a problem hiding this comment.
Our man page is NODE(1) since I rewrote it. :P
e561107 to
2953a06
Compare
|
@benjamingr Updated, ptal. @bengl have time to take a look? |
|
As a note, I didn't rename the filename for |
doc/api/synopsis.markdown
Outdated
There was a problem hiding this comment.
The title being different from the filename is potentially concerning, as mentioned already in a comment.
Could the filename be changed, and then a redirect added in synopsis.html to preserve links?
7da4fd4 to
c7066fb
Compare
|
@nodejs/documentation could we get some more opinions here about the file name/title thing? |
|
Also, if we can leave that for a later PR, that would be great; I'd really like to get some of this merged. |
2953a06 to
b70e5d6
Compare
doc/api/synopsis.md
Outdated
There was a problem hiding this comment.
I'd prefer Hello World or "Hello World!" or nothing at all.
|
LGTM w/ nits. |
b70e5d6 to
ec46ff1
Compare
|
Updated, |
|
👍 done deal then. |
|
LGTM |
doc/api/synopsis.md
Outdated
There was a problem hiding this comment.
Maybe better as node example.js?
There was a problem hiding this comment.
Nvm, that's on the lines below
ec46ff1 to
a4c4e58
Compare
nodejs#6167 Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Robert Jefe Lindstädt <robert.lindstaedt@gmail.com>
Node.js(1) does not make sense. Node(1) would, but this isn’t a `man` page. nodejs#6167 Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Robert Jefe Lindstädt <robert.lindstaedt@gmail.com>
|
looks like this relies on some changes not in v4.x @Fishrock123 please feel free to send a pr if you want to backport this |
|
@thealphanerd This lands cleanly for me on |
PR-URL: #6167 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Robert Jefe Lindstädt <robert.lindstaedt@gmail.com>
Node.js(1) does not make sense. Node(1) would, but this isn’t a `man` page. PR-URL: #6167 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Robert Jefe Lindstädt <robert.lindstaedt@gmail.com>
PR-URL: #6167 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Robert Jefe Lindstädt <robert.lindstaedt@gmail.com>
|
@Fishrock123 must have caught the missing bits in other backports yesterday. thanks for checking |
PR-URL: #6167 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Robert Jefe Lindstädt <robert.lindstaedt@gmail.com>
Node.js(1) does not make sense. Node(1) would, but this isn’t a `man` page. PR-URL: #6167 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Robert Jefe Lindstädt <robert.lindstaedt@gmail.com>
PR-URL: #6167 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Robert Jefe Lindstädt <robert.lindstaedt@gmail.com>
PR-URL: #6167 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Robert Jefe Lindstädt <robert.lindstaedt@gmail.com>
Node.js(1) does not make sense. Node(1) would, but this isn’t a `man` page. PR-URL: #6167 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Robert Jefe Lindstädt <robert.lindstaedt@gmail.com>
PR-URL: #6167 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Robert Jefe Lindstädt <robert.lindstaedt@gmail.com>
PR-URL: #6167 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Robert Jefe Lindstädt <robert.lindstaedt@gmail.com>
Node.js(1) does not make sense. Node(1) would, but this isn’t a `man` page. PR-URL: #6167 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Robert Jefe Lindstädt <robert.lindstaedt@gmail.com>
PR-URL: #6167 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Robert Jefe Lindstädt <robert.lindstaedt@gmail.com>


Checklist
Affected core subsystem(s)
doc
Description of change
There are a few things here:
SynopsistoUsage & ExampleNode.js(1)in the TOC is nowNode.jssince the former does not make sense in any contextcc @nodejs/documentation