-
Notifications
You must be signed in to change notification settings - Fork 399
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
docs: concept focused nav #2302
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2302 +/- ##
=======================================
Coverage 92.48% 92.48%
=======================================
Files 36 36
Lines 7466 7466
Branches 651 651
=======================================
Hits 6905 6905
Misses 553 553
Partials 8 8 ☔ View full report in Codecov by Sentry. |
docs/content/concepts/assistant.md
Outdated
@@ -0,0 +1,186 @@ | |||
--- |
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.
Grabbing this from other PR so I can display Assistant in Nav
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 we can merge this change ealier than the assistant page PR, removing this from this PR, merging this PR without assistant page, and then adjusting the assistant page PR to be compatible with this new structure may be smoother
@@ -9,11 +9,7 @@ lang: ja-jp | |||
|
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.
@seratch I tried combining the Socket Mode and HTTP versions. Can you read it to make sure I did so properly?
.tabs-container { | ||
border: 2px solid var(--ifm-hr-background-color); /* Adjust the color and thickness as needed */ | ||
border-radius: 5px; /* To give rounded corners */ | ||
padding: 0.5em; /* To add spacing inside the tab */ | ||
} |
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 adds an outline around the tabs container so you can tell when the tabbed section ends
label: "Bolt for JavaScript", | ||
className: "sidebar-title", | ||
}, | ||
"getting-started", |
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 the sidebar organization
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.
Thank you for working on this so quickly!
docs/content/concepts/assistant.md
Outdated
@@ -0,0 +1,186 @@ | |||
--- |
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 we can merge this change ealier than the assistant page PR, removing this from this PR, merging this PR without assistant page, and then adjusting the assistant page PR to be compatible with this new structure may be smoother
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.
Left my first round of comments! Thanks for doing this, I think it's a big improvement.
@@ -4,7 +4,7 @@ lang: en | |||
slug: /concepts/event-listening | |||
--- | |||
|
|||
You can listen to [any Events API event](https://api.slack.com/events) using the `event()` method after subscribing to it in your app configuration. This allows your app to take action when something happens in Slack, like a user reacting to a message or joining a channel. |
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 know this isn't exactly part of your PR here but figured I'd mention it: the <detail>
at the bottom of this page calls out a specific thing about the message()
event listening. Perhaps we should move that to the message-listening.md
page instead? I also think we can start 'unfurling' these <detail>
blocks, since the pages now are much shorter and more focussed. Often, when interacting with devs about various topics, I find I have to explicitly point them to docs content nested inside these folded-up <detail>
sections for content relevant to their issue or question.
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.
Makes sense to me!
docs/sidebars.js
Outdated
}, | ||
{ | ||
type: "category", | ||
label: "Interactivity & Shortcuts", |
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 unsure if this label is descriptive or broad enough; will developers understand the breadth of UI surfaces and features this category contains? Buttons, dropdown menus, modal UIs, shortcuts, slash commands... there's a lot here! What about "App UI & Interactivity"? I think that's slightly broader, and then if we can make sure there are descriptions of each of these UIs/features in each sub-page as an intro blurb, I think that would work well. What do you think?
docs/content/concepts/acknowledge.md
Outdated
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 one thing we should call out in this document is that, while these interactivity and shortcut-related app features do require acknowledgement of Slack events, the Events API handlers do not because Bolt automatically acknowledges them. Perhaps this particular convenience/magic needs reinforcement on this page and possibly also on the 'listening to messages' and 'listening to events' pages?
docs/content/concepts/commands.md
Outdated
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.
Is there some end-user or api.slack.com document we can link to for Slash Commands?
@@ -12,7 +12,7 @@ You’ll notice in all `action()` examples, `ack()` is used. It is required to c | |||
|
|||
:::info | |||
|
|||
Since v2, message shortcuts (previously message actions) now use the `shortcut()` method instead of the `action()` method. View the [migration guide for V2](/tutorial/migration-v2) to learn about the changes. | |||
Since v2, message shortcuts (previously message actions) now use the `shortcut()` method instead of the `action()` method. View the [migration guide for V2](/migration/migration-v2) to learn about the changes. |
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.
Let's just get rid of this callout; we're on v4 now. No need to link or call out things specific about a version that was last released 4 years ago.
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.
For the shortcuts and commands pages, we combine both listening and responding into one doc. Maybe we could do the same for actions? I.e. combine action-listening.md
and action-respond.md
?
docs/content/concepts/options.md
Outdated
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'd like to change the title of this document so it's a bit more obvious what it's about. "Options" on its own lacks context. It's about dynamic rendering of dropdown select menu options - I'd like to make that more clear in this document as well as in the sidebar.
docs/sidebars.js
Outdated
'advanced/logging', | ||
'advanced/custom-routes', | ||
'advanced/receiver', | ||
"concepts/authorization", |
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'd put the authorization article after the authenticating-with-OAuth one, since the latter is a pre-req for using the former.
Co-authored-by: Kazuhiro Sera <seratch@gmail.com>
Summary
Applies to both English and Japanese sites.
The huge file count and lines is because I updated the folder structure to more accurately reflect the new docs organization
Requirements (place an
x
in each[ ]
)