Create a design file to share the elemental-bromine tips page proposition and share to stakeholders for feedback

We are starting an epic task to update Elemental Selenium content.
Tips should be validated, and its content reviewed to fit the new tips headers, considering inclusive language.
Code snippets also need to be validated.

• Create a new folder under updated-content named with the new tip number and title using kebab-case. You should follow the folder example: 0-template
• Inside of the folder, a markdown file named as the programing language validated should be created. Example: python.md
• The file should follow the tips template
• Delete the equivalent folder under non-updated-tips folder
• Add a review tag, such as: Last review Day Month Year
• In the case you cannot validate/ run the code snippet, add a tag, something like: Code needs validation

Tips Code Validation

• Tip 24
• Tip 25
• Tip 27
• Tip 28
• Tip 29
• Tip 30
• Tip 32
• Tip 33
• Tip 34
• Tip 38
  (10 tips total)

Tips Content Validation

• Tip 24
• Tip 25
• Tip 27
• Tip 28
• Tip 29
• Tip 30
• Tip 32
• Tip 33
• Tip 34
• Tip 38
  (10 tips total)

• Deploy elemental-next Netlify

Blocked by #100

Description

Create a design file to share the elemental-bromine landpage proposition and share to stakeholders for feedback

Criteria

• Content is decided upon for the cards
• Cards are designed
• Footer is designed/laid out
• Header links and titles are designed
• Button for email CTA is designed
• Need headshot for Dave Haefner https://testautomationu.applitools.com/dave.jpeg

Tip 30 Issue - Outdated information (PR #190)

• Information is outdated (Dave himself also states as much on the page)
• Many broken links need replacing, if content is updated

Tested JavaScript code snippet, failed twice

Django to put together submissions from the team for the moodboard assignment from Marija together with his own work and annotate it into a moodboard to present both to the team and also to the stakeholders to give them an idea of direction.

Design team to create moodboard based on competitor & industry analysis. Moodboard will cover aesthetic and interface inspiration.

Acceptance criteria:

• Moodboard 1: Internal use, larger, more in depth
• Moodboard 2: Concrete, smaller amount of data, only hits the points that we're concrete on to be presented to stakeholders
• Sixteen entries
• 8x Aesthetic/Visual inspiration
• 8x Interface inspiration

A former Sauce Labs created a new tip that was never published!
The tip can be found here: Tip 73 Open a New Window or Tab – Selenium 4

• Create a new tip following the new tip template
• Add it to Elemental-Next

Implement the following features on the Tips page mockup:

• tip component
• menu
• header

This is complete when:

• Users are able to navigate to the tips page from the home page
• All design elements are complete (above) as done in the mockup

Validate code snippets, and update copy content.

Remember to:

• Create a new folder under updated-content (example: 0-template)
• Inside of the folder, a markdown file named as the programing language validated should be created. (example: python.md)
• In the case you cannot validate/run the code snippet, add a tag, something like: Code needs validation
• Delete the equivalent tip folder under non-updated-tips folder

Tips Code Validation

• Tip 1
• Tip 3
• Tip 5
• Tip 13
• Tip 45
• Tip 50
• Tip 51
• Tip 61
  (8 tips total)

Tips Content Validation (and new category)

• Tip 1 - remote, fundamentals
• Tip 3 - fundamentals
• Tip 5 - fundamentals
• Tip 13 - troubleshooting
• Tip 45 - fundamentals
• Tip 50 - fundamentals
• Tip 51 - fundamentals, tools
• Tip 61 - fundamentals
  (8 tips total)

#Description
Create a Google Docs template to update the current tips. This template should consider the content audit previously done by Team Elemental.

##Context (why we are doing this)
Having a template will help with the content update maintaining consistency.

• Change content template file name so it's clear to contributors what it is.
• Change content template instructions to be clear and specific about how to contribute.
• Add template markdown file to Elemental Next
• Create how-to-contribute.md explaining how to use the content template.

Tip27 Issue - Unable to get parallel tests to run (PR #163 )

• Escalating to @diemol for expert attention

We are starting an epic task to update Elemental Selenium content.
Tips should be validated, and its content reviewed to fit the new tips headers, consdering inclusive language.
Code snipets also need to be validated.

• Create a new folder under updated-content named with the new tip number and title using kebab-case. You should follow the folder example: 0-template
• Inside of the folder, a markdown file named as the programing languaged validated should be created. Example: python.md
• The file should follow the tips template
• Delete the equivalent folder under non-updated-tips folder
• Add a review tag, such as: Last review Day Month Year
• In the case you cannot validate/ run the code snippet, add a tag, something like: Code needs validation

Tips Code Validation

• Tip 1
• Tip 3

Tips Content Validation

• Tip 1
• Tip 3

Create a march update newsletter for Elemental Selenium users.
It should contain the following:

• a peak at a new tip #11 (talk with @Roseywinter to validate it)
• a reminder about SeleniumConf discount code
• Promote the team: meet the felloes in the Sauce Labs Community Blog

• Align and space all text blocks properly
• Test possibility of image header to enforce a slowdown for content access
• Prototype tabs for code
• Get marija's approval

Implement a searchbar component in elemental-bromine

• Add a searchbar component in the Menu to be accessible across all the pages

When running npm run build in the frontend directory, the following warnings are thrown:

9:38:01 AM: [WARNING] Duplicate routes found!
9:38:01 AM: - Attempting to create page at /docs/updated-tips/download-a-file/2-download-a-file, but a page already exists at this route.
9:38:01 AM: - Attempting to create page at /docs/updated-tips/how-to-access-basic-auth/13-work-with-basic-auth, but a page already exists at this route.
9:38:01 AM: - Attempting to create page at /docs/updated-tips/how-to-access-basic-auth/13-work-with-basic-auth, but a page already exists at this route.
9:38:01 AM: - Attempting to create page at /docs/updated-tips/how-to-press-keyboard-keys/61-keyboard-keys, but a page already exists at this route.
9:38:01 AM: - Attempting to create page at /docs/updated-tips/how-to-press-keyboard-keys/61-keyboard-keys, but a page already exists at this route.
9:38:01 AM: - Attempting to create page at /docs/updated-tips/how-to-test-checkboxes/45-checkboxes, but a page already exists at this route.
9:38:01 AM: - Attempting to create page at /docs/updated-tips/how-to-test-checkboxes/45-checkboxes, but a page already exists at this route.
9:38:01 AM: - Attempting to create page at /docs/updated-tips/how-to-test-checkboxes/45-checkboxes, but a page already exists at this route.
9:38:01 AM: - Attempting to create page at /docs/updated-tips/how-to-test-checkboxes/45-checkboxes, but a page already exists at this route.
9:38:01 AM: - Attempting to create page at /docs/updated-tips/how-to-upload-a-file/1-upload-a-file, but a page already exists at this route.
9:38:01 AM: - Attempting to create page at /docs/updated-tips/how-to-work-with-hovers/50-hovers, but a page already exists at this route.
9:38:01 AM: - Attempting to create page at /docs/updated-tips/how-to-work-with-hovers/50-hovers, but a page already exists at this route.
9:38:01 AM: - Attempting to create page at /docs/updated-tips/how-to-work-with-javascript-alerts/51-javascript-alerts, but a page already exists at this route.
9:38:01 AM: - Attempting to create page at /docs/updated-tips/how-to-work-with-javascript-alerts/51-javascript-alerts, but a page already exists at this route.
9:38:01 AM: - Attempting to create page at /docs/updated-tips/select-from-a-dropdown/5-select-from-a-dropdown, but a page already exists at this route.
9:38:01 AM: - Attempting to create page at /docs/updated-tips/select-from-a-dropdown/5-select-from-a-dropdown, but a page already exists at this route.
9:38:01 AM: - Attempting to create page at /docs/updated-tips/select-from-a-dropdown/5-select-from-a-dropdown, but a page already exists at this route.
9:38:01 AM: - Attempting to create page at /docs/updated-tips/select-from-a-dropdown/5-select-from-a-dropdown, but a page already exists at this route.
9:38:01 AM: - Attempting to create page at /docs/updated-tips/template/0-template, but a page already exists at this route.
9:38:01 AM: - Attempting to create page at /docs/updated-tips/template/0-template, but a page already exists at this route.
9:38:01 AM: - Attempting to create page at /docs/updated-tips/template/0-template, but a page already exists at this route.
9:38:01 AM: - Attempting to create page at /docs/updated-tips/work-with-frames/3-work-with-frames, but a page already exists at this route.
9:38:01 AM: - Attempting to create page at /docs/updated-tips/work-with-frames/3-work-with-frames, but a page already exists at this route.
9:38:01 AM: - Attempting to create page at /docs/updated-tips/work-with-frames/3-work-with-frames, but a page already exists at this route.
9:38:01 AM: - Attempting to create page at /docs/updated-tips/work-with-frames/3-work-with-frames, but a page already exists at this route.
9:38:01 AM: This could lead to non-deterministic routing behavior.
9:38:01 AM: [info] [webpackbar] Compiling Client
9:38:01 AM: [info] [webpackbar] Compiling Server
9:38:36 AM: [success] [webpackbar] Client: Compiled successfully in 34.50s
9:38:41 AM: [ERROR] Docusaurus server-side rendering could not render static page with path /docs/non-updated-tips/oop/37-oop.
9:38:42 AM: [ERROR] Docusaurus server-side rendering could not render static page with path /docs/non-updated-tips/web-consistency-testing/62-web-consistency-testing.
9:38:44 AM: [success] [webpackbar] Server: Compiled with some errors in 42.63s
9:38:44 AM: Error: Minified React error #62; visit https://reactjs.org/docs/error-decoder.html?invariant=62 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
9:38:44 AM: Error: Minified React error #62; visit https://reactjs.org/docs/error-decoder.html?invariant=62 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
9:38:44 AM: [ERROR] Unable to build website for locale en.
9:38:44 AM: [ERROR] Error: Failed to compile with errors.
9:38:44 AM:     at /opt/build/repo/frontend/node_modules/@docusaurus/core/lib/webpack/utils.js:180:24
9:38:44 AM:     at /opt/build/repo/frontend/node_modules/webpack/lib/MultiCompiler.js:554:14
9:38:44 AM:     at processQueueWorker (/opt/build/repo/frontend/node_modules/webpack/lib/MultiCompiler.js:491:6)
9:38:44 AM:     at processTicksAndRejections (node:internal/process/task_queues:78:11)
9:38:44 AM: [INFO] Docusaurus version: 2.3.1
9:38:44 AM: Node version: v16.19.1
9:38:44 AM: ​
9:38:44 AM:   "build.command" failed                                        
9:38:44 AM: ────────────────────────────────────────────────────────────────
9:38:44 AM: ​
9:38:44 AM:   Error message
9:38:44 AM:   Command failed with exit code 1: npm run build (https://ntl.fyi/exit-code-1)
9:38:44 AM: ​
9:38:44 AM:   Error location
9:38:44 AM:   In Build command from Netlify app:
9:38:44 AM:   npm run build
9:38:44 AM: ​
9:38:44 AM:   Resolved config
9:38:44 AM:   build:
9:38:44 AM:     base: /opt/build/repo/frontend
9:38:44 AM:     command: npm run build
9:38:44 AM:     commandOrigin: ui
9:38:44 AM:     environment:
9:38:44 AM:       - NO_INDEX
9:38:44 AM:       - TARGET_URL
9:38:44 AM:     publish: /opt/build/repo/frontend
9:38:44 AM:     publishOrigin: default
9:38:45 AM: Caching artifacts
9:38:45 AM: Failed during stage 'building site': Build script returned non-zero exit code: 2 (https://ntl.fyi/exit-code-2)

Resolves #103

Tip28 Issue - Outdated content; unsure if need (PR #186 )

Since the different languages of markdown files are being updated by multiple people, there are different changes being made within the copy content of different language markdown files.

For example, Tip 3 Intro section for javascript.md and Tip 3 Intro section for ruby.md might be worded completely different.

We need to go through the updated folder and pull requests to standardize verbiage among these markdown files and their respective language files.

• check markdown files in updated tips folder, in each tip folder, to make sure copy matches (javascript.md, ruby.md)
• check any pull requests coming through to make sure markdown copy matches among the same tips.

We are starting an epic task to update Elemental Selenium content.
Tips should be validated, and its content reviewed to fit the new tips headers, consdering inclusive language.
Code snipets also need to be validated.

• Create a new folder under updated-content named with the new tip number and title using kebab-case. You should follow the folder example: 0-template
• Inside of the folder, a markdown file named as the programing languaged validated should be created. Example: python.md
• The file should follow the tips template
• Delete the equivalent folder under non-updated-tips folder
• Add a review tag, such as: Last review Day Month Year
• In the case you cannot validate/ run the code snippet, add a tag, something like: Code needs validation

Tips Code Validation

• Tip 1
• Tip 3
• Tip 5
• Tip 13
• Tip 18
• Tip 20
• Tip 21
• Tip 22
• Tip 26
• Tip 31
• Tip 35
• Tip 36
• Tip 45
• Tip 50
• Tip 51
• Tip 57
• Tip 58
• Tip 61
• Tip 69

Tips Content Validation

• Tip 1
• Tip 3
• Tip 5
• Tip 13
• Tip 18
• Tip 20
• Tip 21
• Tip 22
• Tip 26
• Tip 31
• Tip 35
• Tip 36
• Tip 45
• Tip 50
• Tip 51
• Tip 57
• Tip 58
• Tip 61
• Tip 69

Instructions are deprecated and need to be updated to reflect new site structure

Broken links and broken images need updating after new site created

Escalating to @diemol

Tip29 Issue - unable to connect to Selenium Remote (PR #178 )

• Issue with very last code block (connecting with Selenium Remote); unsure how to change syntax to make it work.

This tip contains resources and instructions that are deprecated

Broken links and images need replacing if/when newer resource is found, and page is updated

Escalating to @diemol

We are starting an epic task to update Elemental Selenium content.
Tips should be validated, and its content reviewed to fit the new tips headers, considering inclusive language.
Code snippets also need to be validated.

• Create a new folder under updated-content named with the new tip number and title using kebab-case. You should follow the folder example: 0-template
• Inside of the folder, a markdown file named as the programing language validated should be created. Example: python.md
• The file should follow the tips template
• Delete the equivalent folder under non-updated-tips folder
• Add a review tag, such as: Last review Day Month Year
• In the case you cannot validate/ run the code snippet, add a tag, something like: Code needs validation

Tips Code Validation

• Tip 2
• Tip 4
• Tip 7
• Tip 8
• Tip 10
• Tip 11
• Tip 12
• Tip 16
• Tip 19
• Tip 23
  (10 tips total)

Tips Content Validation

• Tip 2
• Tip 4
• Tip 7
• Tip 8
• Tip 10
• Tip 11
• Tip 12
• Tip 16
• Tip 19
• Tip 23
  (10 tips total)

Our current service Drip do not allow us to dynamically get content from a GitHub repos and send it into a newsletter workflow.
Without this feature, it is not possible to automate the newsletter, and specially, to have new contributions added to the newsletter process.

• Find a vendor that allows this feature
• If not, plan how could we build this automation process

Need a Mac user to validate Ruby Tip69 "How To Use Safari" (link). (Related to issue #60 "Validated Beginner Tips in Ruby")

• Technical content validated
• Copy content validated
• New directory and markdown file uploaded to updated tips folder
• Old directory and markdown file deleted from nonupdated tips folder

We are starting an epic task to update Elemental Selenium content.
Tips should be validated, and its content reviewed to fit the new tips headers, considering inclusive language.
Code snippets also need to be validated.

• Create a new folder under updated-content named with the new tip number and title using kebab-case. You should follow the folder example: 0-template
• Inside of the folder, a markdown file named as the programing language validated should be created. Example: python.md
• The file should follow the tips template
• Delete the equivalent folder under non-updated-tips folder
• Add a review tag, such as: Last review Day Month Year
• In the case you cannot validate/ run the code snippet, add a tag, something like: Code needs validation

Tips Code Validation

• Tip 55
• Tip 59
• Tip 62
• Tip 63
• Tip 65
• Tip 70
• Tip 71
• Tip 72
  (8 tips total)

Tips Content Validation

• Tip 55
• Tip 59
• Tip 62
• Tip 63
• Tip 65
• Tip 70
• Tip 71
• Tip 72
  (8 tips total)

A bug is currently affecting how sidebar is auto-generated.
Please check documentation to understand if this bug can be prevened by fixing the front matter.
front matter documentation
Docs tag

Relates to #100

We are starting an epic task to update Elemental Selenium content.
Tips should be validated, and its content reviewed to fit the new tips headers, consdering inclusive language.
Code snipets also need to be validated.

• Create a new folder under updated-content named with the new tip number and title using kebab-case. You should follow the folder example: 0-template
• Inside of the folder, a markdown file named as the programing languaged validated should be created. Example: python.md
• The file should follow the tips template
• Delete the equivalent folder under non-updated-tips folder
• Add a review tag, such as: Last review Day Month Year
• In the case you cannot validate/ run the code snippet, add a tag, something like: Code needs validation

Typs Code Validation

• Tip 1
• Tip 2
• Tip 3
• Tip 4
• Tip 5
• Tip 13
• Tip 45
• Tip 50
• Tip 51
• Tip 61

Typs Content Validation

• Tip 1
• Tip 2
• Tip 3
• Tip 4
• Tip 5
• Tip 13
• Tip 45
• Tip 50
• Tip 51
• Tip 61

We are starting an epic task to update Elemental Selenium content.
Tips should be validated, and its content reviewed to fit the new tips headers, considering inclusive language.
Code snippets also need to be validated.

• Create a new folder under updated-content named with the new tip number and title using kebab-case. You should follow the folder example: 0-template
• Inside of the folder, a markdown file named as the programing language validated should be created. Example: python.md
• The file should follow the tips template
• Delete the equivalent folder under non-updated-tips folder
• Add a review tag, such as: Last review Day Month Year
• In the case you cannot validate/ run the code snippet, add a tag, something like: Code needs validation

Tips Code Validation

• Tip 4
• Tip 8
• Tip 12
• Tip 16
• Tip 25
• Tip 29
• Tip 51
• Tip 53
• Tip 63
• Tip 65

Tips Content Validation

• Tip 4
• Tip 8
• Tip 12
• Tip 16
• Tip 25
• Tip 29
• Tip 51
• Tip 53
• Tip 63
• Tip 65

• depracated

#this is just practice. will delete #166

We are starting an epic task to update Elemental Selenium content.
Tips should be validated, and its content reviewed to fit the new tips headers, considering inclusive language.
Code snippets also need to be validated.

• Create a new folder under updated-content named with the new tip number and title using kebab-case. You should follow the folder example: 0-template
• Inside of the folder, a markdown file named as the programing language validated should be created. Example: python.md
• The file should follow the tips template
• Delete the equivalent folder under non-updated-tips folder
• Add a review tag, such as: Last review Day Month Year
• In the case you cannot validate/ run the code snippet, add a tag, something like: Code needs validation

Tips Code Validation

• Tip 1
• Tip 3
• Tip 5
• Tip 13
• Tip 45
• Tip 50
• Tip 51
• Tip 61*

Tips Content Validation

• Tip 1
• Tip 3
• Tip 5
• Tip 13
• Tip 45
• Tip 50
• Tip 51
• Tip 61

• depracated

Resources and links for tip 20 need to be validated and updated.

• Broken links fixed (or deleted/replaced as necessary)
• New community links to Selenium resources added
• Create new folder and markdown file for Tip 20 in updated tips folder
• Delete old Tip 20 folder from nonupdated tips

Tip32 Issue - Outdated Sauce Labs test results (PR #199)

• Tip contains links to expired Sauce Labs test results, that are no longer available

Tip2 Issue (PR #146)

• Broken code; unable to validate
• Code and instructions need updating (possible deprecated profile syntax)
• Unable to fix code myself; creating Issue and escalating to Diego

Code in this tip is deprecated

Unable to validate any code

Able to validate copy content, except for instructions related to deprecated code

Escalating to @diemol

Tip7 Escalating for expert attention (PR #149)

• Unable to validate code
• Will create Issue and escalate to @diemol for expert attention

Different then Elemental Selenium, which only displays ruby code on the frontend, Elemental Bromine should display all the different language examples.

• Create a page to each tip
• This should be a reusable component, automatically created when a new tip is created
• The titles list displayed on the landing page should be a link to the tip page
• The tip page should allow the user to, without changing the page, switch the code example. Check Selenium page for a very good example. Another good example is WebdriverIO

Carried over from #28

Description

Build the first iteration of the figma mock-ups. Content to be changed BUT content present in the mock-up. UI to be evolved, but present in the mock up

Criteria

• Information Architecture workshopped and mapped
• Tip List Page #8
• Individual Tip page #64
• Colors selected
• Text updated
• Components laid out
• Landing Page #9
• Community Page #225
• External Resources page #224
• Talk to Marija about illustrative graphics available from Sauce(?)
• All buttons/interactive components are at least prototyped for five states

• Tip 8
• Tip 12
• Tip 16
• Tip 25
• Tip 40
• Tip 52
• Tip 53
• Tip 63
• Tip 65

User interview, last one scheduled for Tuesday.

7:00pm UTC
Django facilitating

Users should see a comprehensive title on the sidebar, reflecting each tip's different languages.

Currently, it is not possible to know to which language it refers.

Another option is to add tabs instead of replicating the files, such as showed in this example

In this case, when the example is missing, a button/ call to action is added to allow users to easily contribute.

• Fix markdow to display it correctly (check in documentation how)
• Update contributor guideline with this information

Tip24 Issue - Hypothetical tip with fake website (PR #154)

• Example contains hypothetical code and fake website
• Unable to validate code in real-world capacity
• Escalating to @diemol for expert attention

User should be able to filter tips by difficulty level.
Fetch difficulty label from markdown file and display it in frontend.

• Create a page to list tips
• Enable user to filter the tips by difficulty

We are starting an epic task to update Elemental Selenium content.
Tips should be validated, and its content reviewed to fit the new tips headers, considering inclusive language.
Code snippets also need to be validated.

• Create a new folder under updated-content named with the new tip number and title using kebab-case. You should follow the folder example: 0-template
• Inside of the folder, a markdown file named as the programing language validated should be created. Example: python.md
• The file should follow the tips template
• Delete the equivalent folder under non-updated-tips folder
• Add a review tag, such as: Last review Day Month Year
• In the case you cannot validate/ run the code snippet, add a tag, something like: Code needs validation

Tips Code Validation

• Tip 39
• Tip 40
• Tip 41
• Tip 42
• Tip 43
• Tip 44
• Tip 46
• Tip 47
• Tip 52
• Tip 53
  (10 tips total)

Tips Content Validation

• Tip 39
• Tip 40
• Tip 41
• Tip 42
• Tip 43
• Tip 44
• Tip 46
• Tip 47
• Tip 52
• Tip 53
  (10 tips total)