asiarheyeu / test_workflow_repo Goto Github PK

Description

As a content manager,  
I want to be able to insert or update content (including text, images, link targets and metadata - exact scope TBD) using a simple and intuitive inline interface,
So that I can make basic site updates without developer intervention.

• Support Flexible/Complex editing UI (advanced editing features UI, styling CSS etc)

UI: [https://jhdfdc.axshare.com/#g=1&p=generic_ui]

• Look and interaction of the Main (Context) Menu as well as the forms that come up from the menu when you interact with the buttons
• The form of a "component" ie. Link or Image will be covered as part of those component stories
• Patterns such as adding a title field to all forms is in scope 
• Needs:
  ** list of core editables.
  ** to "productionize" what we have now and conduct user testing to identify gaps and estiamte LOE for an MVP.
  ** to consider wysiwyg
  ** to consider RTL (https://jira.jnj.com/browse/AESQ-124)
  ** another round or two of user testing and feedback.
• Out of scope for P2 is Flexbox: [http://localhost:8005/flexbox/] - (In the menu the "+" ) including the component picker are P3

Requirement Notes:

• All the major functions displayed as icons in the menu should have labels not styles ie. 1,2 are styles
• New groupings of context on the menu are separated out by a bottom white line

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```
 

 

 

Test description

AC,
Ac1
Ac2

Description
Some important story

Artifacts:
Image

Description

As a Site Developer using the GDPR component on a Multilingual site, I want to associate a language with a UUID so that I can identify by language. 

Description

 Precondition:

[~asiarhey], [~hvanyo], [~abeliaye] are to confirm priority and target dates for flattening of EMEA sites

Scope:

The deliverable of this ticket is to do Root Cause Analysis and add comments in each bug found in scope of AESQ-2926.

Out of scope:

• Fixing of issues
• RCA of site specific issues for not prioritized sites.

Timebox:  TBD Hours. 

Description

As a content manager,  
I want to be able to insert or update content (including text, images, link targets and metadata - exact scope TBD) using a simple and intuitive inline interface,
So that I can make basic site updates without developer intervention.

• Support Flexible/Complex editing UI (advanced editing features UI, styling CSS etc)

UI: link

• Look and interaction of the Main (Context) Menu as well as the forms that come up from the menu when you interact with the buttons
• The form of a "component" ie. Link or Image will be covered as part of those component stories
• Patterns such as adding a title field to all forms is in scope 
• Needs:
  ** list of core editables.
  ** to "productionize" what we have now and conduct user testing to identify gaps and estiamte LOE for an MVP.
  ** to consider wysiwyg
  ** to consider RTL
  ** another round or two of user testing and feedback.
• Out of scope for P2 is Flexbox: [http://localhost:8005/flexbox/] - (In the menu the "+" ) including the component picker are P3

Requirement Notes:

• All the major functions displayed as icons in the menu should have labels not styles ie. 1,2 are styles
• New groupings of context on the menu are separated out by a bottom white line

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.

Implementation Notes:

• Leverae the tamper Monkey existing script and enhance if possible 
• https://sourcecode.jnj.com/projects/ASX-NBFP/repos/tampermonkey/browse

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

d some text

reply

Originally posted by @asiarheyeu in #2 (comment)

Description

Goal:

To enhance the performance of assets when a site is flattened using the Flattening Tool.

Request:

• This relates to request 
• Refer to requirements from the Adaptive Images features in CANVAS 
• Investigate options to optimize images, JS and CSS for flattened sites.
• CDN option brings additional costs, what are some other options?
• Evaluate flattened sites with poor performance, expectations (should be provided by EMEA team).
• Hypothesis is that optimization may give good results in case if original site content was not optimized

Deliverables:

• Analyze the options and provide a summary of solutions and LOE