> For the complete documentation index, see [llms.txt](https://jared-gibb.gitbook.io/fullcalendar-plugin-suite/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jared-gibb.gitbook.io/fullcalendar-plugin-suite/elements/calendar/actions/advanced-use.md).

# Advanced Use

* The use case for this would be a super duper smooth calendar experience. 
* When you make a change in the backend, the calendar will rerender. This is fine in a  lot of cases but can cause issue. If you find that to be the case use this action
* Here, you would load data once, then manipulate events using the following actions:

{% content-ref url="/pages/-MdqIRBKXUx\_a89w\_UTe" %}
[Create Single Event](/fullcalendar-plugin-suite/elements/calendar/actions/advanced-use/create-single-event.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MdqIUm642uLd12xKp6Q" %}
[Update Single Event](/fullcalendar-plugin-suite/elements/calendar/actions/advanced-use/update-single-event.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MdqIbsNh52EhIXKsksO" %}
[Delete Single Event](/fullcalendar-plugin-suite/elements/calendar/actions/advanced-use/delete-single-event.md)
{% endcontent-ref %}