labbydev

On branch feature/SUB-5309-test-webform-builder-role
Your branch is up to date with 'origin/feature/SUB-5309-test-webform-builder-role'.

All conflicts fixed but you are still merging.
  (use "git commit" to conclude merge)

Changes to be committed:
        deleted:    .drush-use
        modified:   .editorconfig
        modified:   .gitattributes

labbydev

```
vagrant@d8-local-help:/var/www/pin_help/docroot/profiles/contrib/pin$ npm run start

> pin@8.2.1 start /var/www/pin_help/docroot/profiles/contrib/pin
> gulp

[17:21:46] Using gulpfile /var/www/pin_help/docroot/profiles/contrib/pin/gulpfile.js
[17:21:46] Starting 'default'...
[17:21:46] Starting 'compile'...
[17:21:46] Starting 'clean'...

labbydev

11:40:20 AM awn on  develop [!] took 7m 10s fin blt drupal:sync -vvv
[debug] Drupal VM is not initialized.
> source:build:composer
[Exec] Running export COMPOSER_EXIT_ON_PATCH_FAILURE=1; composer install --ansi --no-interaction in /var/www
Gathering patches for root package.
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Nothing to install or update
Generating autoload files
PHP CodeSniffer Config installed_paths set to ../../drupal/coder/coder_sniffer/

labbydev

FRIEDA Session 3

Search solutions

• Currently is search by location
• Would like to make it more of a directory
• View by alpha, more like a directory in the future (in page search, possibly)
  • Low use case and we don't really want people searching by location
  • in page search (basically replication Command+F)
• potentially search by ID
• potentially search by name
  • remove search by code/ID (and do not display that information)

labbydev

Layout Builder Spike

Ticket Branch

Goals

• Enable Layout builder
• Turn it on for a news article page
• Theme the page
  • We're going to be working on the Press Release template because that content type has fields.
• Without being able to create a custom layout I'm pretty much blocked on this.

labbydev

Styleguide Throwdown - Part 1

Ticket

Notes

Large goals of style guide:

"Platform agnostic enough” (to be useful to other teams) To make our development process easier Developers report that the current SG2 approach is not furthering those goals. In particular, there are complaints about having to do double work, and the fragility of our build and deploy process.

labbydev

  Problem 1
    - drupal/console 0.11.3 requires stecman/symfony-console-completion ^0.5.1 -> satisfiable by stecman/symfony-console-completion[0.5.1].
    - Conclusion: don't install symfony/console v3.2.13
    - Conclusion: don't install symfony/console v2.8.27
    - Conclusion: don't install symfony/console v2.8.26
    - Conclusion: don't install symfony/console v3.2.12
    - Conclusion: don't install symfony/console v2.8.25
    - Conclusion: don't install symfony/console v2.8.24
    - Conclusion: don't install symfony/console v3.2.11

labbydev

oblem 1
    - palantirnet/the-build 1.0.0 requires continuousphp/phing-drush-task dev-master -> satisfiable by continuousphp/phing-drush-task[dev-master].
    - palantirnet/the-build 1.0.0-alpha requires continuousphp/phing-drush-task dev-master -> satisfiable by continuousphp/phing-drush-task[dev-master].
    - palantirnet/the-build 1.0.0-alpha2 requires continuousphp/phing-drush-task dev-master -> satisfiable by continuousphp/phing-drush-task[dev-master].
    - palantirnet/the-build 1.0.1 requires continuousphp/phing-drush-task dev-master -> satisfiable by continuousphp/phing-drush-task[dev-master].
    - palantirnet/the-build 1.1.0 requires continuousphp/phing-drush-task dev-master -> satisfiable by continuousphp/phing-drush-task[dev-master].
    - palantirnet/the-build 1.2.0 requires continuousphp/phing-drush-task dev-master -> satisfiable by continuousphp/phing-drush-task[dev-master].
    - palantirnet/the-build 1.3.0 requires continuousphp/phing-drush-task dev-master -> satisfiable by continuousphp/phin

labbydev

{
    $rteElements = [];

    // Hours section.
    foreach ($hours as $index => $hour) {
      $entity = $hour->entity;

      if (!method_exists($entity, 'hasField')) {
        return FALSE;
      }

labbydev

<!DOCTYPE html>
<html>
	<head>
		<title>chart created with amCharts | amCharts</title>
		<meta name="description" content="chart created using amCharts live editor" />
		
		<!-- amCharts javascript sources -->
		<script type="text/javascript" src="https://www.amcharts.com/lib/3/amcharts.js"></script>
		<script type="text/javascript" src="https://www.amcharts.com/lib/3/serial.js"></script>