Hello Tim

Yes, at the moment only 2 fonts are built into the plugin.

You can only use the following CSS rule on the page between style tags that will overwrite font from our plugin.

<style>
.amelia-app-booking input[type="text"], 
.am-modal.am-in-body input[type="text"], 
.amelia-app-booking input[type="email"], 
.am-modal.am-in-body input[type="email"], 
.amelia-app-booking input[type="tel"], 
.am-modal.am-in-body input[type="tel"], 
.amelia-app-booking input[type="url"], 
.am-modal.am-in-body input[type="url"], 
.amelia-app-booking textarea, 
.am-modal.am-in-body textarea, 
.amelia-app-booking select, 
.am-modal.am-in-body select, 
.amelia-app-booking .form-control, 
.am-modal.am-in-body .form-control, 
.amelia-app-booking .am-stripe-card, 
.am-modal.am-in-body .am-stripe-card,
.amelia-app-booking h1, 
.am-modal.am-in-body h1, 
.amelia-app-booking h2, 
.am-modal.am-in-body h2, 
.amelia-app-booking h3, 
.am-modal.am-in-body h3, 
.amelia-app-booking h4, 
.am-modal.am-in-body h4, 
.amelia-app-booking p, 
.am-modal.am-in-body p, 
.amelia-app-booking span, 
.am-modal.am-in-body span, 
.amelia-app-booking div, 
.am-modal.am-in-body div, 
.amelia-app-booking section, 
.am-modal.am-in-body section, 
.amelia-app-booking ul, 
.am-modal.am-in-body ul, 
.amelia-app-booking li, 
.am-modal.am-in-body li, 
.amelia-app-booking a, 
.am-modal.am-in-body a {font-family:fantasy !important;}
</style>

We added font fantasy just for example, but you will replace the font that you need.

Our team is currently working on a new Customize feature, so more fonts will be added in the future.

Hi again Tim

You can go to ../wp-content/plugins/ameliabooking/assets/less/frontend/_variables.less and remove these two imports. Then, you should go to the Customize page and simply save it again, and that should do it.

Please note, though, that you will need to do this after every update.

Hi again Tim

I'm sorry for the delays, but our priorities change depending on multiple factors. For example, this time last year we completely changed our priorities due to COVID-19. For example, we included Zoom integration out of the blue since the global situation demanded that meetings and appointments are held online (where that was possible). Another reason is customer requests, added on this page. Features are pushed up on our "to-do" list when there are a lot of customers requesting those features.

The customize feature was planned for the spring of 2020, but it was delayed partly because of the reasons explained above, and partly because it requires a lot of changes in the plugin. A simple example is CSS selectors - they need to be changed completely for customization options to reflect the booking form, but still not break any existing forms our users have. The userbase consists of thousands of users, so big changes like this require a lot of planning and modifications.

Our next update will not include the new Customization feature, but if no major issues arise in the meantime, it should be included in the update after that. The first version is pretty much done, we're just testing it, and modifying stuff if we encounter bugs or issues with other segments of the plugin.

In this first version of the Customize feature, we will not include all options we plan to include. The main focus at this time is changing colors, rearranging fields, making string modifications for labels in the booking form. If I'm not mistaken a few more fonts will also be included in the first version, but more will be added in time.

Sorry for the long text, but we do appreciate all our customers, and we try to make the plugin function flawlessly for all of you. The differences between requests and use cases and the number of those requests are causing delays in some features, unfortunately, but that's always going to happen.

You're welcome, Tim.

I hope they are implemented soon also!