[ADD] Events: Create multi slots page#17935
Conversation
|
Hi @theRealThagomizer, got a PR ready for review when you have a moment - thank you! |
theRealThagomizer
left a comment
There was a problem hiding this comment.
Hey, @stepperpig! The new doc looks good. I just had two notes for you to chew on, then I think this is ready to move forward. Thanks!
| The process of registering for a slot as an attendee is similar to :doc:`registering for regular | ||
| events<../promote_monetize/sell_tickets>` via the *Website* app. |
There was a problem hiding this comment.
I feel like the highlighted text doesn't quite align with what the reader might expect when clicking it. "registering for regular events" makes me think that it'll tell me how to register as a user, but the page seems to be about configuring tickets for sale. Maybe the sentence could be something like, "The setup required for attendees to registering for slots at an event is similar to the process for selling event tickets"? Just a thought.
There was a problem hiding this comment.
Good point... I had the intention of linking to the specific section of the doc about registering for tickets on the website but there was no RST internal cross-reference link. I'm going to leave this in here for the moment until I add the cross-ref links in that article.
960d270 to
99f9773
Compare
|
Thanks for the review, @theRealThagomizer! |
Felicious
left a comment
There was a problem hiding this comment.
Great work with documenting this brand new feature, @stepperpig ! 😊
I just had some minor suggestions
@robodoo delegate+
| Creating slots | ||
| ============== | ||
|
|
||
| .. tabs:: |
There was a problem hiding this comment.
really cool idea seeing you provide different instructions to perform actions through different views using the tabs! 😊
just leaving a thought here for you to consider in future articles!
I think your tab method of information architecture works especially well in this article because the actions are conceptually the same, just performed through different views.
However, sometimes these alternative workflows would be better separated into different subheadings instead of tabs. That approach can work well when the workflows are meaningfully different and users may intentionally jump to one method through the TOC (navigation bar on the right of the doc). (Example: different planning views in Erin's doc!)
In your case though, since these are simply different views within the same Events workflow, I think tabs are actually the cleaner and more skimmable choice! 😊 It keeps the article compact and avoids overloading the TOC with near-duplicate sections.
Co-authored-by: theRealThagomizer <96515928+theRealThagomizer@users.noreply.github.com> Co-authored-by: Felicia Kuan <freakyotaku@gmail.com>
3980a29 to
9629f10
Compare
|
@robodoo r+ |

This PR creates a new page for the Events multi-slots feature in 19.0.
Task card
Changelog
Version Scope
This 19.0 PR should be FWP up to master.
An additional PR will be opened to address minor changes introduced in 19.2.