I have been using version two of Google Recaptcha for a while and this month I thought I should update that to version 3. Little did I know that version 3 was now also yesterday's tech and today we have Google Recaptcha Enterprise. Is it any better? That I don't know but I do have the starting of an implementation of it to use in Sitefinity.
It is quite well documented how to customise Sitefinity's 'content widgets'. But customising the 'layout widgets', well, that's a little less talked about. It's easy to add your own layout widgets but these are static HTML files. Often I see a dozen options created for every scenario and/or instructions about adding speciality classes in the designer to achieve effects. This is not a good experience for the content editor.
Once I had used the Sitefinity CLI tool to upgrade a project I was hooked. This was way simpler than the manual process. Not only does it update your packages but it's smart enough to sort out and correct some misconfigurations. But there was something missing for me. There was no option to create a new project. The good news is that the Sitefinity team have this code as open-source meaning I could download and look to add that functionality myself. So, that is what I have done.
Its easy for users to create forms through Sitefinity. But the storage is a simple list and most people want some cool analytics and management of their form data such as provided by Salesforce or ActOn. In this post I look at an easy way to push our forms data to these third party services.
This is my third post of ideas to consider to help make your pages load and run faster. Some will help some projects while others may not be quite relevant. There will be some that contradict previous tips. But hopefully, you will find a few to improve your sites perfromance.
Sitefinity has added a security check named as the Signing Certificate. It is used to verify the issuer of the authentication token to enhance the safety of the site. But currently, the documentation is missing an important piece of configuration to allow this to work for Azure hosted sites.
Recently I came across (another) incorrect implementation of async code which has prompted me to write this post. Async methods are an encouraged code/design implementation but it is important to understand how it works and have some guidelines about using it. If you use it incorrectly, it will slow your application down rather than improving it.
Its not hard to spot a design that was created by a developer. Almost every Windows Form App up until 2010 suffered that horific left side brian effort. Thankfully today we often have a dedicated UI/UX designer sorting that out but even if you have no responsibity around what the front end pages look like you still have a major UX responsibility to ensure a successful project.