<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>reactjs</title><description/><link>https://kevinquillen.com</link><language>en</language><item><title>How to wire ReactJS app to a Drupal 8 controller</title><link>https://kevinquillen.com/how-wire-reactjs-app-drupal-8-controller</link><guid isPermaLink="false">320 at https://kevinquillen.com</guid><description>
&lt;span property=&quot;schema:name&quot;&gt;How to wire ReactJS app to a Drupal 8 controller&lt;/span&gt;

            &lt;div property=&quot;schema:text&quot; class=&quot;text-content clearfix field field--name-body field--type-text-with-summary field--label-hidden field__item&quot;&gt;&lt;p&gt;On most of the projects I work on these days, I typically have requirements at a certain point where data from the application has to meet ReactJS in the frontend at the theme layer.&lt;/p&gt;

&lt;p&gt;We have a very good system in place for working with the theme layer, the backend, and frontend components powered by ReactJS. One example of this is a site search. At its basic level, a site search is comprised of a single text input field (typically a fulltext search field), one or more facets (taxonomy, search modifiers), and a sidebar of promotional content or &apos;best bet&apos; style result.&lt;/p&gt;&lt;/div&gt;
      
&lt;span rel=&quot;schema:author&quot;&gt;&lt;span lang about=&quot;https://kevinquillen.com/user/1&quot; typeof=&quot;schema:Person&quot; property=&quot;schema:name&quot; datatype&gt;Kevin&lt;/span&gt;&lt;/span&gt;

&lt;span property=&quot;schema:dateCreated&quot; content=&quot;2019-07-18T13:00:00+00:00&quot;&gt;&lt;time datetime=&quot;2019-07-18T09:00:00-04:00&quot; title=&quot;Thursday, July 18, 2019 - 09:00&quot;&gt;July 18th, 2019&lt;/time&gt;
&lt;/span&gt;
</description><pubDate>Thu, 18 Jul 2019 13:00:00 GMT</pubDate><dc:creator>Kevin</dc:creator></item><item><title>Routing Client Requests from Javascript to Drupal 8 to Remote Services</title><link>https://kevinquillen.com/routing-client-requests-javascript-drupal-8-remote-services</link><guid isPermaLink="false">273 at https://kevinquillen.com</guid><description>
&lt;span property=&quot;schema:name&quot;&gt;Routing Client Requests from Javascript to Drupal 8 to Remote Services&lt;/span&gt;

            &lt;div property=&quot;schema:text&quot; class=&quot;text-content clearfix field field--name-body field--type-text-with-summary field--label-hidden field__item&quot;&gt;&lt;p&gt;On a recent project that was built on Drupal 8, we had a requirement to integrate with three different search platforms.&lt;/p&gt;

&lt;p&gt;One of them was private access only, requiring a whitelisted IP to talk to it. On the front end, we designed and built the search form and result list logic as a ReactJS component. The component did it all, making the request and listing the results back from the response.&lt;/p&gt;&lt;/div&gt;
      
&lt;span rel=&quot;schema:author&quot;&gt;&lt;span lang about=&quot;https://kevinquillen.com/user/1&quot; typeof=&quot;schema:Person&quot; property=&quot;schema:name&quot; datatype&gt;Kevin&lt;/span&gt;&lt;/span&gt;

&lt;span property=&quot;schema:dateCreated&quot; content=&quot;2018-08-18T12:00:00+00:00&quot;&gt;&lt;time datetime=&quot;2018-08-18T08:00:00-04:00&quot; title=&quot;Saturday, August 18, 2018 - 08:00&quot;&gt;August 18th, 2018&lt;/time&gt;
&lt;/span&gt;
</description><pubDate>Sat, 18 Aug 2018 12:00:00 GMT</pubDate><dc:creator>Kevin</dc:creator></item></channel></rss>