-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
feat: extract /plugins
#11464
feat: extract /plugins
#11464
Conversation
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.
💖 This is awesome! resolve-nav-data
looks way cleaner and simpler, and I'm really liking the new organization on the /plugins
route.
Reviewed the diff and also pulled the branch down locally and checked things out, and I think you're good to go ahead and delete all the crufty now-commented-out code in resolve-nav-data
💯 Apart from that, and the index.mdx
page (which we likely need Packer team help filling it), this feels nearly ready to ship, IMO!
website/content/plugins/index.mdx
Outdated
page_title: Plugins FIXME | ||
--- | ||
|
||
# Plugins FIX ME |
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.
💖 Love that this is stubbed out
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.
@azr would you be able to add some text here? Or tag someone else? 🙏
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.
Yes !
Co-authored-by: Zachary Shilton <[email protected]>
Co-authored-by: Zachary Shilton <[email protected]>
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.
This is super dope, I added content to the new plugin page, from an already existing plugin page. I think it makes sense there, but these pages sound a bit duplicate now.
Should just be about extending packer ? Or not even be here anymore 🤔
BTW, I found myself wanting to click on the version of a plugin, to sort's of go on the release page. If that's easy, that'd be nice :D
Is there a documentation somewhere on how to test documentation rendering ?
Super nice work !!!!
Versioning for plugins is on our road map! We're aiming to handle that shortly after the core versioned-docs rollout.
Yea. These nested "Overview" pages are generated from nested Ex.
I do agree though that the "Overview"s should be merged into a top-level one. We'll likely need a more solidified pattern to handle this.
@azr are you referring to manual testing? Or unit/integration testing? Or something else? |
@azr Unfortunately we don't have a super smooth workflow at present for testing rendering documentation from work-in-progress in remote plugin repos. I think @sylviamoss set up a workflow involving local |
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.
@thiskevinwang Realized one missing piece here might be redirects - I think we'll want to generate redirects for any external plugins. For example, I think we want to redirect from /docs/datasources/hashicups/coffees to /plugins/datasources/hashicups/coffees.
Seems like a high-level docs/datasource/* >> plugins/datasources/*
redirect would conflict with any built-in plugins... so my hot take is I think we'll need to go a level down and do eg /docs/datasources/hashicups/* >> /plugins/datasources/hashicups/*
redirects. But very open to other approaches 🙇♂️
Ah yea, thanks for catching this @zchsh. I'll get those sorted out. |
@zchsh Added redirects in efa2d0e
Quick smoke test: this works now |
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.
LGTM !!
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.
🙌🏽 🎉 🚀
* feat: extract `/plugins` Co-authored-by: Zachary Shilton <[email protected]> Co-authored-by: Adrien Delorme <[email protected]>
* feat: extract `/plugins` Co-authored-by: Zachary Shilton <[email protected]> Co-authored-by: Adrien Delorme <[email protected]>
* feat: extract `/plugins` Co-authored-by: Zachary Shilton <[email protected]> Co-authored-by: Adrien Delorme <[email protected]> Co-authored-by: Kevin Wang <[email protected]> Co-authored-by: Zachary Shilton <[email protected]> Co-authored-by: Adrien Delorme <[email protected]>
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Preview
Description
This moves external plugins to a new
/plugins
route.This is in support of unblocking versioned-docs (core docs).