Ok well, that is a bit closer to what i would hope for.. It addresses some, but not all issues, however, all things being relative, it's a start.
"..not taken the time to test out the calendar"
In actuality, i put far more time into this plugin than pretty much any other plugin that produced initially unsatisfactory results, and finally was not satisfied with the cost benefit i.e. time to result ratio overall. And to correct some apparent ongoing misconception on how software (in this case a plugin) is supposed to work for people, the testing (and documentation) is to be done by the developer, not the users or community at large. We are users/administrators not beta testers. (Our time is valuable too).
It does appear you have cajoled the plugin appropriately to obtain the simplest and least demanding result which i feel should have been effortless to obtain, and directly (initially) forthcoming.
"..depending on what shortcodes you use and in what order.."
..And the exact official documentation on how to directly accomplish this result is.. Where? The plugin author's note to me on how to achieve this result is.. Where? Not even you have directly indicated how to *simply* achieve this nominally straightforward result. But i do grant you kudos for having gotten the initially expected output, after how much effort?
However, The effect you have managed to create is not a far cry of difference from creating a custom sidebar widget that links to predesignated pages with details. It certainly saves no steps, from that as an alternative, and has no apparent benefit other than what we will call an "overview" list of all events which can be done with any category display shortcode for a category named "events".
Further issues not addressed:
1) Upcoming events displayed in graphical sidebar calendar supplied WP or in theme, in my case; Easel do not appear, even on your site.
2) Secondary "confirmation" of event administrative page is extra work and serves no real apparent purpose.
3) The claim that events can be directly administrated from post, that would forgo the former (#2) above mentioned secondary "confirmation of event being an event" page, is a false or misleading claim at best.
4) It is not intuitive, has an administrative UX leaving much to be desired, and is poorly documented (thus your need for "testing" in the first place, otherwise it would be known directly as "effective deployment" since the "how to" was already a given, not a variable).
The only real benefit i have seen, as i had achieved part 1 and 3 of what you did, is the expiration of events, which for all the time and effort, might as well be manually accomplished anyway.
I am seriously glad you got what you were looking for, but on an intuitive, easy to use, and does what it says scale it weighs weakly compared to most other preferred plugins obtained for any other purpose. After all, a computer is inherently a calendar/time machine, more than mos any other purpose. I do not understand why this plugin or any other calendar would be so frustrating or initially difficult to implement.
"..i tryed many others and found them to be too dificult and too many options to input lots of data and get the desired output.."
Likewise, i agree with you. The whole state of internet software development saddens me deeply- that this is as far as we have have gotten over a decade into the 21st century, and the best we can hope for to date. It seems like we are shying away from progress eternally in favor of reprimanding users and their requests for improvements that would make more sense out-of-the-box; such as: obvious clarity, intuitive design, pleasant UX from end to end, documentation and streamlined deployment as well as simplifying administration overall.
I am sorry, to be fair: in my opinion the plugin author has done a fine job starting on something that could one day be a fantastic plugin..