I recently had a client whose project required putting a basic REST API in place to handle data-oriented requests. The target language was PHP for a LAMP deployment. Here is a basic PHP "Hello, World" REST API endpoint example that includes CORS with an allowed list.
Honey pot fields can and should also be checked on the server. This is in case the bot is going to the server directly, and bypassing the form. The honey pot value from the form is submitted to the server. It should be null when it arrives. If there is content, there is a bot.
A honey pot is a means to prevent bots from submitting forms. A seemingly valid input field is hidden by CSS. Bots will read the code, and put content into the field - humans will not. Validation checks for content in the field. If there is content, then a bot is using the form.
I am not sure if this is considered old-school or modern, but you can also use span elements to control wrapping with a good degree of precision. Toggle from display: inline to display: block as needed at media query break points. This also works well in i18n situations.
If you want to emphasize to the browser where to best break/wrap text, you can use the special character ​ or the <wbr> element. Useful for breaking at sentences - especially on mobile viewports. Also consider text-wrap, overflow-wrap, hyphens and word-break.
AI in action today as I am building sales assets from existing video demonstrations. Upload video to S3. Create an AWS Transcribe job that points to the video. Run transcription. Feed resulting transcript into ChatGPT for outline and sales demo script. Up next: build decks.