[ADD] events: adding create events doc

[ksc-odoo]

PROJECT TASK: https://www.odoo.com/web#id=3888717&cids=3&menu_id=4720&action=333&active_id=3835&model=project.task&view_type=form

This brand new PR walks the user through how to create an event with Odoo Events, and will take a in-depth detailed look at all the fields, tabs, elements, and options involved in doing so.

[robodoo]

Pull request status dashboard.

[ksc-odoo]

Alrighty, @tiku-odoo this is ready for a Peer Review from you. Thanks!

[tiku-odoo]

@ksc-odoo

This is a great addition to the events documentation. Awesome job on really going through the event form. I've made some optional functional questions and made corrections to one or two misspellings (very minor). Feel free to implement the suggestions as you see fit. I'm approving this doc to move forward now.

Thanks,
Tim 👍

[ksc-odoo]

Thank you for the always helpful feedback, @tiku-odoo -- I made all your suggested edits, and believe this is now ready for a Final Review @StraubCreative -- whenever you get a chance. Thanks! 👍

[StraubCreative]

Hi @ksc-odoo

Awesome doc! So glad we'll have this in our repository 💪

Approving with comments. I have a number of items here, for you to consider, to help add depth or supporting context to the various features and fields of the event form as well as the larger event creation process.

• Please minimally address the items below labeled: ❗ Necessary change
• For everything else, I would consider addressing on a new PR (for an additional 2-3 pts 😉) since publishing this doc live is more important (and useful!) to our users than it would be sitting in review.

I hope you find the comments to be useful and informative in expanding the documentation. Please let me know if you have any questions.

Otherwise, great job and see you on the next review!

[StraubCreative]

I think this is misleading, albeit unintentionally, in that, the smart buttons are primarily used as logistical portals to perform actions for the event in specific ways for the organizer(s), and are secondarily useful as numeric displays.

The same way you might point to a Delivery or Manufacturing smart button on a Sales Order— it's not just to say "I have 1 Delivery Order," it's instead to invite action around specific and necessary activities through those buttons. The numeric value is surface-level, whereas the activities before and after, surrounding the smart buttons, matter more.

Further, when those figures are displayed, you can still click into the button and perform a variety of useful actions afterwards, specifically around reporting.

In this way, consider more strongly emphasizing the utility of the buttons so we communicate their operational relevance for the user.

[ksc-odoo]

Thanks for the in-depth feedback, @StraubCreative . I made all the necessary modifications, and some other supplemental ones along the way, and believe this one is now ready for Tech Review @samueljlieber 👍

[samueljlieber]

Hi @ksc-odoo! Thank you for all your hard work on this brand new Events doc! I think this new doc adds a lot of quality information for creating events. I also agree with ZST that there are a bunch of avenues that open up with publishing this doc, that can be documented in the near future!

I have a bunch of suggestions for you (sorry 😅) hopefully you find them constructive! Please let me know your thoughts on any that you may want to discuss. Tag me for another quick look after you have had a chance to work through these.

Thanks for your continued hard work here, almost there! 🙂

p.s. Please let me know if it would be easier for you if I made a second commit to your PR with all these changes (as I have them made locally)

[ksc-odoo]

Thanks for the incredibly helpful, super-detailed feedback, @samueljlieber -- I made ALL the suggested edits you left, and believe it's ready for another look from you, whenever you get a chance. Thanks! 👍

[samueljlieber]

Looks good to me @ksc-odoo! Nice work 👍
.....
@robodoo r+