<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Front-End on Resolver Engineering Blog</title>
    <link>https://engineering.resolvergroup.com/tags/front-end/</link>
    <description>Recent content in Front-End on Resolver Engineering Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>Copyright © 2026 Resolver Group</copyright>
    <lastBuildDate>Tue, 10 Aug 2021 17:43:04 +0100</lastBuildDate>
    <atom:link href="https://engineering.resolvergroup.com/tags/front-end/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Using Awesomplete for auto-complete inputs</title>
      <link>https://engineering.resolvergroup.com/2021/08/using-awesomplete-for-auto-complete-inputs/</link>
      <pubDate>Tue, 10 Aug 2021 17:43:04 +0100</pubDate>
      <guid>https://engineering.resolvergroup.com/2021/08/using-awesomplete-for-auto-complete-inputs/</guid>
      <description>&lt;p&gt;Awesomplete is a front-end autocomplete tool that compares a user’s input to a defined data list, and if it recognises the input will make suggestions for the user to choose from.&lt;/p&gt;
&lt;p&gt;We chose to use the Awesomplete tool in the Accord team while building the journey to enable users to create and submit their dispute. Awesomplete provided a neat solution to our problem of how to let the user choose the organisation they are raising a dispute against. The simplest solution would have been a dropdown list of all available organisations. However, as we will be working with ADR providers representing potentially hundreds or thousands of organisations, a dropdown list would not have been a feasible solution. Enter Awesomplete!&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
