Description

As a Developer, I want to see any issues with Analytics and the Data Layer as I am building the site, so that I can be warned if I missed anything needed to meet the requirements of the Data Layer. 

edited
 

Description

PannAs a bodiless core developer
I want to understand how to update package version dependencies
+So I can do it.+
{color:red}Red{color}
-Strike-
Sub
^Super^
??Citation??
{{Mono}}

link title

List 1

List 2

• Bullet 1
• Bullet 2

(/) (x)(!)

{noformat}
no further formatting is done here
{noformat}

{panel:title=My title}
Some text with a title
{panel}

Description

STR

1. migrate .co.uk
2. open homepage

Actual: header and main menu are not rendered
Expected: the flattened frontpage page looks the same as the frontpage on source site

Migration configs

{
  "url": "https://www..co.uk/",
  "crawler": {
    "maxDepth": 1,
    "maxConcurrency": 1,
    "ignoreRobotsTxt": true
  },
  "transformers": [
  ]
}

johnsonandjohnson#240

Description

Steps to reproduce:
1.

git clone -b feat/enhance-handling-non-existing https://github.com/dewen/Bodiless-JS.git

cd Bodiless-JS/

npm run setup

npm run sites:clone-local starter

npm run sites:update starter

cd sites/starter/

7. update migration-settings.json to the following:

{
  "url": "http://diarree.be/",
  "crawler": {
    "maxDepth": 100,
    "maxConcurrency": 1
  },
  "transformers": [
  ]
}

npm install

npm run migrate:full

Actual Results:

1. http://diarree.be/posterimage.jpg , http://diarree.be/contact/posterimage.jpg goes to /404 page but they are available in /static
   !Screen Shot 2020-03-10 at 2.29.03 PM.png|thumbnail!
2. ''Resource http://diarree.be/404 has been excluded from download'' message is in the logs.

Expected Results:
non-existing resource is not migrated

Attachments

Description

As a bodiless core developer
I want to understand how to update package version dependencies
+So I can do it.+
{color:red}Red{color}
-Strike-
Sub
^Super^
??Citation??
{{Mono}}

1. link title
2. List 1
3. List 2

• Bullet 1
• Bullet 2

(/) (x)(!)

{noformat}
no further formatting is done here
{noformat}

{panel:title=My title}
Some text with a title
{panel}

#22

Description

As a bodiless core developer
I want to understand how to update package version dependencies
+So I can do it.+
{color:red}Red{color}
-Strike-
Sub
^Super^
??Citation??
{{Mono}}

link title

List 1

List 2

• Bullet 1
• Bullet 2

(/) (x)(!)

{noformat}
no further formatting is done here
{noformat}

{panel:title=My title}
Some text with a title
{panel}

Description

Failed:

https://travis-ci.com/github/johnsonandjohnson/Bodiless-JS/builds/173776158

from pre-pack cmd:
@bodiless/cli: > rimraf lib && npm run build && oclif-dev manifest && oclif-dev readme
 

Attachments

Description

As a bodiless core developer
I want to understand how to update package version dependencies
So I can do it.

Description

Failed:

https://travis-ci.com/github/johnsonandjohnson/Bodiless-JS/builds/173776158

from pre-pack cmd:

@bodiless/cli: > rimraf lib && npm run build && oclif-dev manifest && oclif-dev readme```
 

## Attachments
<img title="Travis.CI.2020-07-01.00-02-38.png" src="https://user-images.githubusercontent.com/22957855/86950059-4d83fd80-c158-11ea-9244-08b906737e4d.png" width="200" />

Description

As a bodiless core developer
_ I want to understand how to update package version dependencies_

• So I can do it.+
  {color:red}Red{color}
  -Strike-
  Sub
  ^Super^
  ??Citation??
  {{Mono}}

link title

List 1

List 2

• Bullet 1
• Bullet 2

(/) (x)(!)

{noformat}
no further formatting is done here
{noformat}

{panel:title=My title}
Some text with a title
{panel}

Description

SPIKE

Build only in static app

• when the static site npm install is complete, build artifacts are placed on a shared volume and the edit app can receive the upates simply by copying the files
• when the edit app copies the files, it restarts only if necessary

Description

As a bodiless core developer
I want to understand how to update package version dependencies
+So I can do it.+
{color:red}Red{color}
-Strike-
Sub
^Super^
??Citation??
{{Mono}}

1. link title
2. List 1
3. List 2

• Bullet 1
• Bullet 2

(/) (x)(!)

{noformat}
no further formatting is done here
{noformat}

{panel:title=My title}
Some text with a title
{panel}

Description

Issues reported by flattening

1. The components do not convert to the right naming conventions as a result this needs to be done manually.
2. The pages have same component names across the site [live site] as a result it always generates a common component. As a result it shows the first component content across all the pages.
3. The cdn images do not download.
4. The cdn images are present for each resolution which will need to be downloaded manually.
5. The live site urls end with .list, after flattening it would have to be trimmed off.
6. The youtube iframes do not seem to flatten fine.
    
   Deliverables
7. provide a short-term solution for the issues
8. create tickets for long-term solution

Description

As a canvasx developer or product owner
I want to easily create a github issue for work on bodiless-js
So that I can give the community visibility into our work.

Acceptance Criteria

AC1.
There is a browser plugin or other automation
Which allows me to create an issue in the Bodiless-JS GitHub project
Based on the Jira issue I am currently viewing

AC2.
The Description and AC's are copied to the Github issue

AC3.
The GitHub issue is given a label indicating that it is an internal issue

AC4.
A link to the GitHub issue is added to the Jira issue

Description

As a team member
I want to understand the gaps in our existing edit experience
So I can remediate them

Results and videos:

Acceptance Criteria

Deliverables

• Deployment to publicly accessible location
• Testing by content editors from all 3 sectors
• Collection of feedback
• Creation of gap stories

Attachments

Description

As a developer or product owner
I want to easily create a github issue for work on bodiless-js
So that I can give the community visibility into our work.

Implementation Notes:

• Leverage the tamper Monkey existing script and enhance if possible 

QA notes:

Acceptance Criteria

AC1.
There is a browser plugin or other automation
Which allows me to create an issue in the Bodiless-JS GitHub project
Based on the Jira issue I am currently viewing

AC2.
The Title, Description, AC's and attachments are copied to the Github issue

(attachments is a nice to have)

AND

There is no reference of any Jira ticket # in the GitHub issue 

AC3. (nice to have)
A link to the GitHub issue is added to the Jira issue in the Description 

(does not have to delete the existing content, this can be done manually)

AC4.

If the Title of the Jira ticket is a duplicate in GITHub then there is no option to create the ticket

If the Title of the Jira ticket is not a duplicate in GitHub then there is an option to create the ticket in GIT

AC5.

When the "Create GitHub Issue" button is clicked it directs them to Git Hub ticket in a new tab and the data filled in

Description

Failed:

https://travis-ci.com/github/johnsonandjohnson/Bodiless-JS/builds/173776158

from pre-pack cmd:

@bodiless/cli: > rimraf lib && npm run build && oclif-dev manifest && oclif-dev readme```
 

## Attachments
<img title="Travis.CI.2020-07-01.00-02-38.png" src="https://user-images.githubusercontent.com/22957855/86937723-435a0300-c148-11ea-9fd2-962752c6143e.png" width="200" />

Description

Happened on v.0.0.34 release of packages.

STR

1. Create a PR on slate_gatsby repo
2. Check the triggered build's log

ER
Build ends with success.

AR
Build fails (form time to time) with an error:

W: packages/gatsby-theme-bodiless/__tests__/create-pages.test.ts:15:7
W: 15 const fs = require('fs');
W: ~~
W: 'fs' was also declared here.
W: packages/gatsby-theme-bodiless/__tests__/gatsby-node.test.ts:16:9 - error TS2451: Cannot redeclare block-scoped variable 'createPages'.
W: 
W: 16 const { createPages } = require('../gatsby-node');

Note: It doesn't happen locally.
Workaround for psh: just trigger rebuild.

Description

PannAs a bodiless core developer
I want to understand how to update package version dependencies
+So I can do it.+
{color:red}Red{color}
-Strike-
Sub
^Super^
??Citation??
{{Mono}}

link title

List 1

List 2

• Bullet 1
• Bullet 2

(/) (x)(!)

{noformat}
no further formatting is done here
{noformat}

{panel:title=My title}
Some text with a title
{panel}

Description

As a team member

I want to understand the gaps in our existing edit experience

So I can remediate them

Acceptance Criteria

Deliverables

• Deployment to publicly accessible location
• Testing by content editors from all 3 sectors
• Collection of feedback
• Creation of gap stories

Description

As a bodiless core developer
I want to understand how to update package version dependencies
+So I can do it.+
{color:red}Red{color}
-Strike-
Sub
^Super^
??Citation??
{{Mono}}

link title

List 1

List 2

• Bullet 1
• Bullet 2

(/) (x)(!)

{noformat}
no further formatting is done here
{noformat}

{panel:title=My title}
Some text with a title
{panel}

Description

Failed:

https://travis-ci.com/github/johnsonandjohnson/Bodiless-JS/builds/173776158

from pre-pack cmd:

@bodiless/cli: > rimraf lib && npm run build && oclif-dev manifest && oclif-dev readme

Attachments

User Story

• AS A [who are you? eg Developer, Content Editor, etc.]
• I WANT [what is the feature you want?]
• SO THAT [what will you be able to do once the feature is implemented?]

Background/Description

Acceptance Criteria

Implementation Notes

References