List of build/website-related things we're involved with

# List of build/website-related things we're involved with (Not including bot because I don't know about that) :thumbsup: = we should keep owning this :question: = not sure :thumbsdown: = consider transferring ownership (I = Elizabeth probably) --------------------------------------------- ## Open source ### Just (task orchestration) :question: https://github.com/microsoft/just (who owns maintenance, especially responding to issues?) (note that other teams and potential external people use this) ### Beachball (publishing) :question: https://github.com/microsoft/beachball ### frontend-bootcamp (training) :thumbsdown: https://github.com/microsoft/frontend-bootcamp This is the material for a workshop Ken and Micah put together (and I helped) for CXE and Office non-web-devs last year. Despite being meant as a companion for in-person training and not really being suitable as standalone tutorials, it gained much more attention than we expected online. Micah pointed out recently that it's probably out of date now given how quickly web stuff moves (also won't reference our new fluent packages) and so we should potentially just archive the repo for now and reopen it later if there's demand for us to do a training again. ### riceburn (codemods) :thumbsdown: https://github.com/kenotron/riceburn Listing mainly just for awareness (I don't think we're expected to maintain this one). The existing `packages/migration` depends on this package for codemods, but in the future it sounds more likely that we'd use `ts-morph`. --------------------------------------------- ## Non-public build/infra/support ### Fabric ISS project :thumbsdown: https://dev.azure.com/uifabric/iss ### Custom ADO agent pool :question: Template code: https://dev.azure.com/uifabric/UI%20Fabric/_git/agent-pool Deployment job: https://dev.azure.com/uifabric/UI%20Fabric/_build?definitionId=145&_a=summary Ken set this up before the repo merge so that we could migrate former-stardust's build from circleci and merge the two without making the build terribly slow. For some reason, the machine's in ADO's default hosted agent pool are extremely slow compared to circleci, and apparently you can't even pay for faster managed agents. Downside of this approach is as Ken put it, we're pretending to be ops, which means more time spent putting out random fires. This *may* be reduced once we've worked out initial kinks, but it's hard to say. If it turns out to be too much of a pain, we may need to move most builds back to circleci (some may stay in ADO for security reasons) unless we can find an option for a paid ADO plan with faster hosted agents. ### Fabric CDN --------------------------------------------- ## Fabric repo build elements ### Custom scripts (note that a handful of other repos copy our scripts; would ideally like to publish reusable parts properly for consumption as a package) ### API Extractor integration ### Size auditor part of source: https://onedrive.visualstudio.com/OneDrive%20Service/_git/OneDrive.LightRail ### Screener integration :thumbsup: Obviously need to keep this. No additional work needed right now as far as I know, but it does break sometimes for various reasons. ### PR deploy site :thumbsup: ### Update release notes script https://github.com/OfficeDev/office-ui-fabric-react/tree/master/scripts/updateReleaseNotes Uses CHANGELOG.json (generated by beachball) to create [GitHub releases](https://github.com/OfficeDev/office-ui-fabric-react/releases) with correct release notes. Should possibly be integrated into beachball. ### Custom build tasks https://dev.azure.com/uifabric/UI%20Fabric/_git/azure-devops-tasks ### ??? --------------------------------------------- ## Website ### Public site code obviously ### Public site release process ### Public site manifests, bundles, and assets ### UHF Contacts Private repo with bootstrapping code (homepage.htm) ### aka.ms/fabricdemo :thumbsup: Front end: https://dev.azure.com/uifabric/UI%20Fabric/_git/fabric-demo Back end: https://fabricweb.scm.azurewebsites.net:443/fabricweb.git The demo page (including ability to view demos from other versions) continues to be very useful and makes sense for our team to maintain. One open question is if/when/how it should be converted to use Storybook instead of example-app-base. #### Google search console for requesting incorrect phishing warnings be removed... ### `@uifabric/example-app-base` Legacy demo app platform still used for legacy demo apps within our repo, by ODSP, and possibly by a couple other partners. (Also used for parts of the current website.) More or less superceded by storybook for demo app purposes, so we should deprecate that type of usage. The parts that are currently used in the website will probably no longer be necessary after the new website is done (though the API reference table implementation may be interesting to preserve or at least reference in new code). ### HIG (awareness only) :thumbsdown: ### Editorial board effort ### Live example editor (`@uifabric/tsx-editor`) :question: https://github.com/OfficeDev/office-ui-fabric-react/tree/master/packages/tsx-editor  ### Unfinished website tests https://dev.azure.com/uifabric/UI%20Fabric/_git/fabric-website-tests --------------------------------------------- ## Other ### Assorted work supporting build for other teams This was mostly Ken, so he'd have to add specifics and whether there's anything he plans to hand off. ### Fabric icons tool ### Fabric CDN repo (actually hosted on a SharePoint CDN) ### docs.microsoft.com integration https://github.com/MicrosoftDocs/oufr-dev-docs ### TS validation build https://github.com/Microsoft/ui-fabric-ts-validation Not sure where the pipeline is. It's been broken since January or earlier. ### ODSP Fabric bundle https://dev.azure.com/uifabric/UI%20Fabric/_git/odsp-fabric-bundle ### Aquerium (github query chrome extension) :thumbsdown: https://dev.azure.com/uifabric/UI%20Fabric/_git/aquerium This was an intern project in summer 2019. Probably doesn't need to be maintained (I'm not sure it even released), just listing for awareness. ### b-link :thumbsdown: https://dev.azure.com/uifabric/UI%20Fabric/_git/b-link Not sure why this is in our ADO instance since it's used only by ODSP, and we certainly don't need to maintain it. (Cliff wrote this and I heavily modified it when we were in ODSP. Not sure if this is the original or a mirror) Multi-repo linking tool Cliff wrote and I heavily modified when we were in ODSP. Not sure why it's in our ADO instance (or if this is just a mirror for some reason). Certainly not something we need to maintain--if it's the real version, we should migrate it to ODSP's ADO, or if it's a mirror, we can delete it. --------------------------------------------- ## Website open issues - huge bunde size - uses hash routing which is bad for SEO--you can't even bing/google an individual fabric component right now! (UHF team says we could switch to non-hash routing even while remaining on their host but not sure how this would be set up) - ongoing fights with CSS frameworks in UHF host - current setup requires examples and source to be published with fabric package - way too much boilerplate to add new pages --------------------------------------------- ## Short-term build items (goes somewhere else but dumping here for now) - migrate to eslint -