Launch FAST

[EisenbergEffect]

An ordered checklist of what we need to do to launch FAST:

• Merge @radium-v's homepage/docs integration PR feat: fast-website #3311
• Merge @radium-v's content load timing fix PR fix: wait to initialize homepage components with dom dependencies #3367
• Merge @chrisdholt's site ui fixes chore: fix broken ui in fast-website, various content fixes, update to use new color vars #3324
• @awentzel to implement pipeline updates to deploy both www and explore sites chore: update action to build for www staging #3322
• Merge @awentzel path correction PR chore: update to correct path from www to static #3328
• Merge @awentzel's docs fixes PR chore: update to resolve documentation issues #3329
• Merge @radium-v's background dim PR chore: update to dim bg when page scrolls beyond hero #3333
• Merge @SamanthaAO 's site badge fix
• Merge @chrisdholt's internal part name PR fix: ensure all component internals have part names #3306
• Merge @chrisdholt's anchor style fixes fix: inherit font size and line height in hypertext styles #3320
• Merge @chrisdholt's ui regression fixes fix: outline button and anchor should use outline color recipes #3327
• Merge @chrisdholt's hyptertext fixes fix: remove hypertext styles from button #3319
• Merge @chrisdholt button height fix fix: ensure button control height matches wc root height #3340
• Merge @EisenbergEffect's missing elements export fix fix(fast-element): export missing elements filter helper #3331
• Merge @EisenbergEffect's style flexibility fix feat(fast-element): enable CSSStyleSheet and string to be used as styles #3345
• Merge @SethDonohue tabs fix fix: selected tab becoming undefined when tab slot pass anything except icon or text node #3350
• Merge @nicholasrice's upcoming docs PRs chore: fast-foundation API docs round 2 #3316 chore: add API docs for fast-components #3321
• Merge @nicholasrice's fast-components-msft API docs PR chore: adds tsdoc comments to fast-components-msft #3332
• Merge @nicholasrice 's color parsing export fix feat: export parseColorString from components and components-msft #3356
• Merge @nicholasrice's home page link fixes fix: fixing link to documentation #3362
• Merge @nicholasrice 's animation and colors API docs chore: adds API docs for fast-colors and fast-animation #3359
• Merge @janechu's PR for the logo chore: add the new logo and inline logo for FAST as the favicon and inline logo in Creator, Component Explorer and Tooling examples #3313
• Merge @janechu's upcoming PR for creating absolute paths in the guidance section chore: update to absolute paths when converting README files #3325
• Merge @EisenbergEffect's children directive fix and filter feature feat(fast-element): enable children and slotted filters #3323
• Merge @EisenbergEffect's event capture bug fix fix(fast-element): default event handler behavior should be no capture #3337
• Merge @EisenbergEffect's big docs PR docs: readme fixes, doc site content correction and additions #3315
• Merge @EisenbergEffect's grammar and style PR docs: grammar and style corrections #3354
• Merge @EisenbergEffect's faq header normalization PR docs(faq): make headers all the same level #3364
• Merge @nicholasrice's light mode logo and theme switcher for docs PR chore: default to dark mode and enable theme switcher in documentation #3380
• Merge @EisenbergEffect PR to update docs with new repo name chore: change all instances of fast-dna to fast #3381
• Rename the repo to "fast"
• Publish all web components packages
• Create Permanent Redirect from old site to new site for URLs that have changed.
• Publish the website
• Publish the Component Explorer

[EisenbergEffect]

Ping @awentzel. The homepage/docs integration PR is up. So, I believe you can proceed with the pipeline work.

[chrisdholt]

@EisenbergEffect I was rolling through this and noticed the following:

URLs pointing to external resources (non fast.design pages) should open in external window/tab via "_blank" attribute improved SEO and keeping people on our site.

I think we should scratch this in favor of providing the user the opportunity to open whatever external link they want either in the browser or outside of it. I have concerns about usurping their choice in favor of us prioritizing keeping our content open in a window. There's a ton of quick ways to navigate around the web and many users have preference on when and how they manage their tabs/windows. In certain cases this makes sense, such as when you have links as part of active forms or sites where editing is taking place. In those cases navigation could zero out changes being made and opening links in new tabs/windows makes sense. Outside of that though, I don't see a reason to shift from the default behavior of allowing users to open tabs however they prefer.

[EisenbergEffect]

I didn't add that particular line-item. So, no disagreement from me. Maybe @awentzel had some thoughts?
In terms of the Markdown, it's just a normal Markdown link. I didn't alter any behavior from the default.

[chrisdholt]

I didn't add that particular line-item. So, no disagreement from me. Maybe @awentzel had some thoughts?
In terms of the Markdown, it's just a normal Markdown link. I didn't alter any behavior from the default.

For now I've removed the following:

• URLs pointing to external resources (non fast.design pages) should open in external window/tab via "_blank" attribute improved SEO and keeping people on our site.

I'm open to discussing the above in an issue if people are passionate. For now, I don't think there is consensus on that functionality/behavior. I also don't think it's required for launch.

[EisenbergEffect]

@awentzel There's an item above labeled "Implement and merge review feedback from @awentzel from feature branch into master" Was that tracking your early feedback on the docs (already incorporated) or is that something else we still need to do?

[EisenbergEffect]

Ping @awentzel for feedback on the above.

[EisenbergEffect]

@chrisdholt Can you add any work items to this list that are still not done so we have a sense of what's left to get launched?

[chrisdholt]

@eisenbereffect Once we fill out the above, we are good to go. Site is ready for initial publish (yay continuous integration 😄). I believe the component explorer is ready. We can publish as needed. I think we have what we need to close this out!