THE RE­ACT FRAME­WORK

Maximum PC - - R&D -

Re­act is de­vel­oped to han­dle user in­ter­faces, so you should think of it as a part of your toolset, not the en­tire so­lu­tion.

To use Re­act, you may want to con­sider what logic you need to com­bine with it. Com­bin­ing Re­act with a CMS is one way to go, and there’s even a web­page ( https://re­act­for­dru­pal.com) for this pur­pose. Dru­pal is not the only choice, though. Word­Press has an API that makes de­vel­op­ing the in­ter­face straight­for­ward.

When you have npm in­stalled, you can look for pack­ages us­ing the built-in search. The re­sult is a long list of pack­ages, so be sure to choose “re­act­dom” for web­pages; “re­act-na­tive” is for na­tive en­vi­ron­ments. Pack­ages that use Re­act make an even longer list. In fact, the length alone should en­cour­age you to learn Re­act and con­sider us­ing it for your next project. If you think about how much it’s used in live in­stalls, you’ll be even more mo­ti­vated. Re­act is a ma­jor force in the move to­ward a head­less oper­a­tion that most CMSes are mov­ing to, and if you don’t want to use a CMS, you can still use it for your reg­u­lar ap­pli­ca­tion. It’s per­fect for one-page ap­pli­ca­tions, where the page be­haves more like an ap­pli­ca­tion than a web­page.

Newspapers in English

Newspapers from Australia

© PressReader. All rights reserved.