terryupton

The first-party WordCount plugin is already included in Craft’s CKEditor plugin. It can show word and/or character counts and include logic on what should happen as you type (e.g. when you get near or over the limit). If you toggle “Show word count” in the CKEditor field’s setting, you get the word count shown underneath the field. To turn on character count, go to CKEditor Config used by that field and add the following under “Config Options”:

"wordCount": {
    "displayCharacters": true,
    "displayWords": true
}

terryupton

<h3 class="font-semibold mb-3 text-xl">
  {{- 'Status History'|t -}}
</h3>
<ol class="space-y-5 text-sm">
  {% for history in order.histories %}
    <li>
      <h5 class="mb-1 inline-block uppercase text-11 border px-1 py-0.5 leading-none text-{{ history.newStatus.color }}-500 border-{{ history.newStatus.color }}-500">
        {{- history.newStatus -}}
      </h5>
      <div class="ml-2">

terryupton

<IfModule mod_rewrite.c>
# ------------------------------------------------------------------------------
# | Exclude directories from the rewrite rules                                 |
# ------------------------------------------------------------------------------
# RewriteRule ^eShots - [L]

# ------------------------------------------------------------------------------
# | Rewrite engine                                                             |
# ------------------------------------------------------------------------------
# Turning on the rewrite engine and enabling the `FollowSymLinks` option is

terryupton

Updating vlucas/phpdotenv on 22 December 2021

Wow! So I never knew this...and perhaps it's just me but thought I should put it out there....so I have upgraded to "vlucas/phpdotenv": "^5.4.0" as it seems all of my projects were still on ^2.4.0. What I never realised is that we should also be maintaining the index.php file and the craft files too. As these don't fall into the regular craft updates.

So today, I have just updated the index.php added the new bootstrap.php file and also updated the craft file too - so these all work with "vlucas/phpdotenv": "^5.4.0"

I must ensure I look out for updates on these files in the future. Perhaps everyone already knows this, but I never did until now. 😳

terryupton

{% set checkboxFieldClasses =
  "form-checkbox w-5 h-5 text-green-500" %}
  
{% if field.type == "checkbox_group" %}
{% set fieldClass = checkboxFieldClasses %}

<div class="mb-2">
  {% include 'forms/_default/_partials/_label.twig' %}

  {{ field.oneLine ? '<div class="flex flex-wrap">'|raw }}

terryupton

<section x-data="{showModal: false, showLoading: false, html: ''}">

<button
  @click="html='loading...'; showLoading = true; showModal = !showModal; 
    fetch('{{ entry.url }}', {
      method: 'GET',
      headers: {
      'X-Requested-With': 'XMLHttpRequest',
      },
    })

terryupton

<button
  @click="showModal = !showModal | fetch('{{ entry.url() }}', {
    headers: {
      'Content-Type': 'application/json',
      'X-Requested-With': 'XmlHttpRequest'
    },
  }).then(res => res.text()).then(text => { html = text })"
  class="flex justify-center animate-grow-on-hover--small"
>

terryupton

<perch:related id="faqs" collection="FAQ's" label="FAQ's" sort="custom" >
<details class="expandingBlock // application-notes__item">
  <summary class="expandingBlock__title // application-notes__title"><perch:content id="question" type="text" label="Question" required="true" title="true" /></summary>
    <div class="expandingBlock__content">
      <perch:template path="content/blocks/content-primary.html" />
    </div>
</details>
</perch:related>

terryupton

CraftHub

A collection of public github repos that are build with #craftcms. I find these useful to review best practices, architechure, template and module setup nd expose as well as general project stucture and approaches.

https://github.com/CityofOakland/oaklandca.gov
https://github.com/nystudio107/devmode

terryupton

So I am looking to inline certain JS functions and pieces of code for some third parties (sliders, light-boxes, galleries etc). The reason for this is so I can keep specific and relevant javascript together with the twig code for that specific module/component. Rather than splitting it over a twig file and a separate js file(s).

A good example and use-case of this is Swiper (https://swiperjs.com/).

Below is a basic setup on how this is structured and my ideal approach. Files have been numbered for clarity and order over explanation.

Concerns and Qustions: