-
Notifications
You must be signed in to change notification settings - Fork 394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add doc/user-guide/glossary
page
#2595
Conversation
d58df78
to
3804c90
Compare
{ | ||
"label": "What is DVC?", | ||
"slug": "what-is-dvc" | ||
}, | ||
{ | ||
"slug": "project-structure", | ||
"source": "user-guide/project-structure/index.md", | ||
"source": "project-structure/index.md", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed that this page and the page on line 143
had incorrect source
causing the "Edit on Github" link to take you to a 404 page. I went ahead and fixed them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting. Should the engine throw an error when building? Out of scope for this PR but could open an issue (or move the fix to another PR and we can decide there). Same for line 141
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure about the engine throwing an error, but I don't mind moving these fixes to a separate PR if needed!
content/docs/sidebar.json
Outdated
{ | ||
"label": "Glossary", | ||
"slug": "glossary", | ||
"source": "basic-concepts" | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
needs to be moved further down the sidebar, question is where? CC @iterative/docs
Personally I think "What is DVC?" and "Project Structure" are closely related to "Glossary" (compared to any other sidebar item) but don't know if that's enough justification to keep them near each other.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed, that we should move it down. Probably even to the bottom of the UG?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think Glossary can be the last section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I moved glossary to the bottom of user-guide for now.
3804c90
to
a3364a4
Compare
a3364a4
to
2d840b0
Compare
* add Documentation Markdown/Main and WithJSX components * add template for creating doc pages with jsx instead of markdown * add glossary page to pages directory
2d840b0
to
ca9c4fa
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good on the code end! I'll just give this a comment for now and let the docs team approve when the sidebar and any other requests are handled.
Nice work!
One thing - let's try to generate 3rd or 2nd level titles? This way items will have links? @iterative/docs WDYT? |
Nice work @julieg18 Thank you. If I open the glossary link directly, it's like this: Link is: https://dvc-org-add-glossary-pa-jxqnju.herokuapp.com/doc/user-guide/glossary if I navigate the page from the sidebar, it's like this: This is with Firefox 89 on macOS 11.4 In the first version, there is a sudden collapse after loading the page. |
All entries already have One work-around may be to make them titles indeed, but of a new class where they appear inline (no need to separate title & description with a newline) |
Hyperlink is now added to heading(and can be added to any other headings on the page if we decide to do so) and all the glossary elements should be rendering properly! |
yes please (as in hovering on a term will show a link icon 🔗 on the left of it) |
Do we want to convert the terms' names into h2s or try to mimic a headers link behavior while keeping the terms how they look now? |
The "look" should be the same as now. Whether internally they are somehow h2s without line breaks or (probably easier) mimic link behaviour is up to you. |
The terms' names are now hyperlinks, acting like Header hyperlinks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
awesome
I never noticed the Codeclimate check failing in docs repo PRs. Is it an issue? |
{ | ||
"label": "Glossary", | ||
"slug": "glossary", | ||
"source": "basic-concepts" | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What would it take to reduce this sidebar entry to just "glossary"
? Moving the basic-concepts/
folder?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if I'm understanding your question 🤔 Are you referring to deleting source
or renaming the source
value to glossary
? The source
is used to build the "Edit on Github" button. If you're asking about deleting the source, we don't have a /content/docs/user-guide/glossary.md
so deleting the source would end up creating a 404 link. I linked the basic-concepts
folder, since that is where we're currently holding all of our tooltip data. If you're asking about renaming the source
to glossary
, I suppose we could do that by renaming the basic-concepts
folder to glossary
😃
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What would it take to reduce this sidebar entry to just
"glossary"
? Moving thebasic-concepts/
folder?
I think by "sidebar entry" you meant page URL slug?
The sidebar entry is "Glossary," and the page URL slug is "glossary." The "source" folder is only used for the "Edit on GH" button.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reduce this sidebar entry to just "glossary"
I was referring to this:
{ | |
"label": "Glossary", | |
"slug": "glossary", | |
"source": "basic-concepts" | |
} | |
"glossary" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you're asking about renaming the source to glossary, I suppose we could do that by renaming the basic-concepts folder to glossary
Right. Should we do that? But again... #550 (see #2595 (review) below).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we'd be able to do that(replacing the whole object with "glossary") since the "Edit on Github" link would default to https://github.com/iterative/dvc.org/blob/master/content/docs/user-guide/glossary.md which doesn't exist.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just noticed this. Hmm so it's a special/hardcoded nav entry then. Not sure I love that but oh well, this is merged!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wait no I see. I think it could default to /content/docs/user-guide/glossary/index.md too? Again, this is merged so np but I was thinking what does it take to decouple it completely from basic-concepts/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
confusion related to #2595 (comment)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://dvc-org-add-glossary-pa-jxqnju.herokuapp.com/doc/user-guide/glossary looks is great, thanks @julieg18! I'm just unsure where should it go in the nav but that's easy to change later.
I'm slightly worried that we won't have a good index for the actual Basic Concepts section (#550) per #1395 (comment). Are we sure we're not going to want to move this into there? Because that would require a permanent redirect at that point. Cc @casperdcl @shcheklein @iesahin
Other than that, I'm curious about the significant code changes but I'll leave that for @rogermparent perhaps since I'm unable to determine exactly how they relate to the Glossary page. Specifically:
src/components/Documentation/Markdown/inde/Main/
folder was created with 2 pre-existing files but unfortunately GH didn't pick up the move, so it's hard to tell what changed.- What is src/components/Documentation/WithJSX/AutoLinkElement/ ? (index.tsx:67 looks fun)
- Same for src/templates/doc-jsx.tsx . Where is
IJSXDocPageProps
used?
Thanks
@jorgeorpinel
We have a
Whoops, that's a typo. I'll delete the
I don't think so. Looking at the CodeClimate review, correcting any of the issues mentioned would only create unnecessarily complex code. But if you think something could be better with the code, feel free to mention it! |
I don't understand. Is this related to this confusion? |
Thanks for the explanations @julieg18! Seems like the code has been peer reviewed so 👌
It's related to the naming somewhat, yes @casperdcl. But there's a reason we have glossary tests in I'll mention it in tomorrow's meeting. |
Are we good to merge this, or is there more to discuss? |
I still don't know what @jorgeorpinel means by "redirect" (i.e. redirect what to what?) but I suspect by "redirect" he is referring to people bookmarking the "edit on GH" URL rather than any dvc.org URL.
I also don't know what @jorgeorpinel means by "index" but I suspect that once again he means where in source code does a different issue (#550) get addressed, and the answer as repeatedly stated in both issues & meetings is in the same folder. The yml/md source files each will contain 2 keys (short & long descriptions: the short ones are rendered to Glossary, the long ones to BC #550). Definite immediate merge to me unless @jorgeorpinel is envisioning a different source layout. |
I'm not blocking the merge. @casperdcl you're a bit confused: By redirect I mean https://github.com/iterative/dvc.org/blob/master/redirects-list.json i.e. an actual HTTP 301/303 redirect.
Exactly. I'm trying to prevent it from changing and redirecting if we have to move the By index I mean |
UPDATE: OK, we discussed this in a meeting (cc @shcheklein and @iesahin) and we agreed to keep the glossary page where it is since it may take a while to get to #550 anyway. Also we can use it initially as the "Basic Concepts index" if we only have a few BCs (e.g. #2453) by linking them from this glossary page. If it needs a redirect in the future, so be it. |
Thanks again @julieg18 ! 🎉 |
But neither
completely lost
And none of the above 3 things will ever exist. |
doc-jsx.jsx
for creating documentation pages with jsx instead of markdowndoc/user-guide/glossary
page that lists all tooltip data in this format:Fixes #1395
@jorgeorpinel @casperdcl @iesahin