…rag and drop

Add a preprocessor to exclude certain CSS-targed HTML from the rendered
page before indexing occurs.

Enable the preprocessor and set it to .visually-hidden by default

Debugging search_api led me to a TextNode object that seems to be
created by Stemmer.  The instructions say that a much better experience
is had if you enable the tokenizer first, which we did not have.  So
stripping the HTML with the tokenizer results in proper search occuring.

Before this change, not only could you search for breadcrumb, but any
menu item, such as home, about, and more.  You'll still be able to
search those pages from their title, but not every page needs to be
returned because they have a top menu item of home.

…sition and subtitle fields

… 1:1 profile images

…icky at top of lists, and autoentity label

… tool sorting

… and icons for contact info and directory list to block picker

…alesites-project into YALB-1478--view-displays

…to head

For more senior developers, this allows an at a glance look on the
requirements to have set up, while allowing a deeper dive into the
document to find specifics.

Attempt to rearrange steps so that if you were to go through the list
one by one you would have prerequisites to execute the next
requirement.

Give a list overview of the repos used to produce the yalesites project
with links to each.

* Change to requirements and setup
* Add node version max requirement since we've determined nodejs >= 11
  does not work
* Mention the name of the environment variable to hold the personal
  access token for github packages

Add more to the repo descriptions to show how they tie together to help
the platform function.

In the github portion, we specify that they need a SSH key, but we were
more verbose in terminus.  Now both are treated similarly.

* Split github into sub-bullet points
* Use proper spacing for numbered list continuation

* Node needs to also be less than version 11
* From tests, it looks as if you could forego composer and use lando to
  do all composer-related things.  This could deter the use of xdebug
      however?

* Add personal access token specifics in this document to save having to
  visit a whole other repo for it.
* Refer to what Yale-managed packages include so they know why they care
  about the statements made.

Co-authored-by: @codechefmarc
Co-authored-by: @myvaughn

Clone is the proper term for what we're doing.

For completeness, add how to clone the project.

We can always look inside of the setup script if we need to do this
manually, and it was brought up that keeping this in sync with the file
over time could become problematic.

Now that we don't have two different setup methods, there's no reason to
specify that the subheading is a script version.

I attempted to prune some of the scripts that I personally don't use as
much.

Properly describe that the repository actually *is* a custom upstream,
not that it contains it.

…rrectly set specific styling for profile lists

…or favicon preview

…alesites-project into YALB-1478--view-displays

…templates

…alesites-project into YALB-1478--view-displays

…text for profile to include instructions

…rides

…rides

…others

…o meet passing contrast ratio

YALB-1495: Branding: Customized favicon

The current issue is that when a view is accessed that was previously
created using the Drupal autocomplete results in a truthy value (a 1)
being placed for the ID, so that taxononmy term is used for all views
matching this.  This fix properly evaluates whether the term is an
object (the Drupal autocomplete) or an id (the chosen autocomplete) and
has been extracted to its own private method to start to separate
concerns.

* fix: updating to latest atomic

* hotfix: downgrade captcha module

* hotfix: remove view/argument warnings

* fix: Adds checks to certain views basic variables to prevent errors in logs

* fix: don't return boolean, instead return actual operator value

* fix: Change to null coalescing operator

* fix: fix incorrect target ID for filtering

* fix: Account for backwards compatibility with older stored values prior to chosen

* fix: Check if terms arrays are arrays first

* fix: Additional checks to prevent errors in logs

* revert(chosen): remove composer-merge-plugin

Due to an issue with Pantheon and the now deprecated use of
composer-merge-plugin, we are removing references to it's use in order
to provide another fix for this.

References:
- https://www.drupal.org/node/3069730
- https://git.drupalcode.org/project/chosen/-/blob/4.0.x/README.txt

* fix(chosen): use installer-plugin to place chosenJS

In order for chosen to work in Drupal, it must reside in
./web/libraries/chosen.  This allows composer to utilize the
installer-paths to accomplish this.

Co-authoried-by: @vinmassaro

---------

Co-authored-by: Jim Vomero <[email protected]>
Co-authored-by: nJim <[email protected]>
Co-authored-by: Marc Berger <[email protected]>
Co-authored-by: David Blankenship <[email protected]>
Co-authored-by: David Blankenship <[email protected]>

… the other fields

…ooter-branding