Improve custom paging

I think it’ll be nice to change

        dots: true,
        appendDots: ,
        dotsClass: ,
        customPaging: ,

to

        dots: true,
        appendDots: //'.slider',
        dotsClass: // 'ul.dots',
        dotsItemClass: //'li.dots-item',
        dotsItemActiveClass: //'active',
        customPaging: ///...

Custom paging is ok as of now, but it is not quite there. We still have to target ‘li’ and ‘li.slick-active’ and above changes would allow to be a bit less tied to slick css for custom pagination.

I do use slick exclusive classes like

.slider.slick-initialized .slick-slide {
    display: block;
}

as event hooks to prevent FOUC, which is fine.

[certainlyakey]

I follow this. Maybe we shouldn’t add the paging li classes as a separate option, but it could be resolved instead with allowing us to customize the <li>'s via the customPaging option as well. Currently customPaging allows to customize only the tags inside each li (buttons).

[leggomuhgreggo]

I can see the way in which that adds some sanity, but I’m hesitant to add options on those grounds alone re:bloat/comprehensibility, but if there’s more clammer for it the option is still open. Thanks.