Just what it says.

• #14
• #19
• Switch origin in outer CDN

"Your" is misspelled on the Github Bot success page. https://www.hlx.live/tools/bot/setup

i think there are a few blocks that can appear above the fold eg. here:
https://main--helix-website--adobe.hlx3.page/docs/indexing-reference

i think it would be great to remove the CLS impacts for those blocks, i am not sure what the best strategy, for the gists it could be that a the height might be fixed.

Again from business-website.

Expected Behaviour

It would be nice to have a way for the community to submit blocks, code snippets etc.. that can help turbocharge development of Franklin sites for others. The criteria to get a block into the existing boilerplate / block collection is high and we still need a way to share and re-use blocks built by the community rather than re-inventing the wheel every project.

Actual Behaviour

Currently need to search in github.com/hlxsites for similar blocks to then leverage in our own projects

In the form https://main--helix-website--adobe.hlx.live/tools/bot/register there are two issues with the checkbox

1. It is not accessible by keyboard. Tab keys do not reach the checkbox.
2. Without selecting the checkbox if someone tries to submit the form, no error is shown to the user.

Expected Behaviour

1. One should be able to access the checkbox by keyboard
2. Error should be displayed

Actual Behaviour

None of the things mentioned happen

Reproduce Scenario (including but not limited to)

Navigate to https://main--helix-website--adobe.hlx.live/tools/bot/register and perform the steps mentioned below

Steps to Reproduce

1. Enter Data in Github Username field and press tab. The checkbox should be focused but that doesn't happen.
2. Do not select the checkbox and try to submit the form. The Form doesn't get submitted and no error is displayed.

Platform and Version

Google Chrome (Version 110.0.5481.177)

Sample Code that illustrates the problem

Logs taken while reproducing problem

Extend columns styling to support the redesign

The copy block uses innerHTML with unsanitized user input:

div.innerHTML = `<span>${config[key]}</span>`;

New block to support redesign, used on the Documentation Listing page

Migrate https://main--helix-tutorial--auniverseaway.hlx.live/ to helix-pages/tutorial

There are mechanics to load a template from a meta tag and add it as body class. We do have a precedence for this, but never had a templates folder at the root. So my question is: do we really need this, or could we lump it into styles.css? My assumption is that such global styles should probably be loaded as quickly as possible.

The feature also hides the body until the template CSS is applied to avoid CLS, but this may also impact FCP and LCP.

Given the exemplary nature of the Helix website itself, we should be really diligent about the best practices we set forth...

The following are not addressed in either indexing or sitemap:

• helix-sitemap sheet feature in query-index.xlsx
• default hreflang feature in query-sitemap.yaml

In scripts.js, there's a selector block config with paths, script and style filenames. It allows loading a block for any element matching the selector, and avoids loading non-existent files (e.g. if a block only consists of a CSS file).

But it also adds complexity, reduces modularity (blocks need to be registered in scripts.js), which requires a trade-off.

For users who already have the sidekick extension installed, the generator page (/tools/sidekick/) could be instrumented to simplify adding (and removing) a project.

The search is currently looking inside the title and the content (https://github.com/adobe/helix-website/blob/main/blocks/header/gnav-search.js#L75). It should:

1. search in title, description and content
2. prioritise search results: on top of the result list, search results where term is in title, then in description and finally in content

I know we don't have a good consensus on how to handle docs > svgs. This isn't to tackle that.

@augurone had the great suggestion that we should be injecting the SVGs instead of using an image tag. This is definitely better for colorizing and animating... likely more things.

Developers should know when they're pushing code that won't pass tests or linting.

Currently located at https://main--helix-home--adobe.hlx.page/docs/setup-indexing.html, the indexing documentation needs to be updated to Helix 3 and ideally brought to helix-pages/docs.

New block, can use cards block as a jumping off point

Expected Behaviour

Clicking the Go button on https://www.hlx.live/tools/sidekick/ should successfully add the project.

Actual Behaviour

The go button does not seem to do anything. Instead you can click the Sidekick Configurator button above the form, which gives you a message "Your Sidekick is not configured for this project yet" but then clicking add project also does not seem to do anything.

Reproduce Scenario (including but not limited to)

Steps to Reproduce

1. new browser, google chrome on Mac OS, sidekick plugin installed but no projects configured.
2. navigate to https://www.hlx.live/tools/sidekick/
3. enter a repository url, e.g https://github.com/hlxsites/uhg-surest and click "go"
4. nothing happens

Notes and Thoughts

• I was looking at trying to fix this via PR, but to be honest the full expected flow for this page is somewhat confusing to me, so thought I'd start with an issue.
• I think the sidekick configurator button should not be a button but instead just a headline
• I think ideally that repository url input could also accept an hlx.live or hlx.page url, and just parse out the gh url from there

Platform and Version

google chrome on Mac OS

../docs/feed.md needs to be updated to Helix 3 (once implemented 😉)

Add the search field + ability to search to the Side Navigation block.

Searching in this field should also update the query params in the url so that a search is easily shareable

Extend the current footer to acommodate the redesign

Create a new document /new-footer

Note that the region selector is not required since the site is only one lang for now.

Document how to structure content for a multi language website (/en/apage, /fr/apage)...

Pull in the tbx-olympus logo wall block as a base & reskin

https://www.hlx.live/docs/faq#q68 won't scroll the selected question into view or highlight it.

New template styling for documentation pages to accommodate they layout with the side navigation

CSS should follow the same indenting rules as JS.

Document page naming best practices for authors in https://www.hlx.live/docs/authoring

From @ kptdobe:

In gdrive / sharepoint, it is recommended to use filenames in lowercase, without spaces (dashes instead) and with only latin characters. Dynamic Quotes should become dynamic-quotes. While both works, the recommended version is better to educate authors to maintain clean urls and have a. clear mapping between url and filename.
If you name you document This Is A crazy Name with àccent, spaces & extra fancy.?-things .docx there is no way you can guess the url or the filename from the url

• Fallback font settings in styles.css (Helkix Font Fallback extension)
• Font styles in styles.css (Importer UI > eyedropper)
• Best way to load custom fonts in lazy-styles.css

Looks like GitHub has updated their "Use this template" button to be a dropdown. The tutorial and video on https://www.hlx.live/developer/tutorial need to be updated to reflect the change.

Expected Behaviour

Tutorial should document all steps exactly as they are required

Actual Behaviour

Tutorial is missing a step which is confusing to a novice

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Browse to https://www.hlx.live/developer/tutorial
Follow the steps to "Use this template"
Missing step: Choose "Create a new repository" in the dropdown that appears

Platform and Version

MacOS 13.3.1(a) on Chrome 114

Use the existing Z Pattern block as a base, add additional content areas to match the redesign

In the training and sample content, multiple references to fstab.yaml are made, but none of them define exactly WHERE in the GDrive it should go. The sample content does not contain an example fstab.yaml for us to view/modify, so it's very confusing. It's also unclear if there's a special format for it, if we need to do anything special, put URLs in quotes, etc.

Updates to:

• Typography
• Color variables
• Spacing variables

Align on:

• Use of media queries and breakpoints

Extend the existing header block to accommodate the redesign

Create a new document /new-nav to be used in place of the existing nav

Extend the existing helix tabs block to accommodate the redesign

https://www.hlx.live/developer/tutorial

Expected Behaviour

Webpage should scroll smoothly and not get stuck

Actual Behaviour

Webpage gets "stuck" and does not allow me to scroll higher

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Browse to https://www.hlx.live/developer/tutorial
Scroll down past the first video and image
Scroll back up slowly from the second image
Browser looks like it wants to scroll up but code seems to keep kicking the page back down again
Scrolling fast enough can get you past the issue, but it's still easily reproducible afterward

Platform and Version

MacOS 13.3.1(a) on Chrome 114

Sample Code that illustrates the problem

N/A

Logs taken while reproducing problem

N/A

Screen recording

Should be able to port this into the documentation listing page and all documentation pages

• Search functionality ported over from current website (search query should also appear in the URL so search can easily be shared)

Create a new page for the contact form.

Use a standard helix form, i.e. a spreadsheet defines the form and takes the form submissions. Adobe can then hook up automation for form submissions.

Form field TBC.

https://www.hlx.live/docs/setup-customer-sharepoint should be added to https://www.hlx.live/docs/ overview

Port from business-website

Cards that appear at the bottom of the documentation detail pages for navigation

I think we should keep robots out initially in order to lower the discoverability.

New block to support redesign