MSEdgeExplainers VS Bootstrap

The spec is a W3C CSS working group draft: https://drafts.csswg.org/css-anchor-position-1/

It looks like less of a Chrome thing and more of an Edge thing? The Intent to Prototype [1] links to an Edge explainer [2] with Microsoft authors. It doesn't look like anyone has asked Mozilla for a position yet [3] but I expect if they get positive signals from web developers (us!) that will be soon.

[1] https://groups.google.com/a/chromium.org/g/blink-dev/c/vsPdd...

[2] https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/...

[3] https://github.com/mozilla/standards-positions/issues?q=anch...

Read the explainer here

You can learn more about Focus Mode in this Edge explainer document.

For a spec about a browser feature, "getting it" can mean a few different things.

1. Understanding the purpose of the feature ("why/when would I use this?")

2. Understanding how to implement the feature

3. Understanding how to use the feature

4. Understanding the feature's "corner cases" (surprising implications, cases where it doesn't do what you'd expect, etc.)

5. Understanding why the feature works the way it does (instead of some other way)

Most of the web specs really only explain how to implement a feature, and even then, they're not great at that, because they do such a poor job at explaining the purpose of the feature.

Assuming that you, like most of us, aren't working on implementing a browser, that means that web specs are mostly unhelpful to you. It's almost completely beyond the purpose of a spec to teach you how to use a feature, what its corner cases would be (which are often unknown at the time a spec was written), and why the specification says what it says.

This is an area where the web spec community has made some improvements in recent years. Nowadays, it's understood that new proposed specifications shouldn't just provide a specification, but also a separate "explainer" document, whose purpose is to communicate #1 (the purpose of the feature), and also persuade the other browser vendors to implement the feature. ("This will be really cool, and here's why…")

At a minimum, specs nowadays often include a non-normative "Motivation" section, as the CSS Nesting spec does. https://www.w3.org/TR/css-nesting-1/ I you'll find that you can "get" that spec much better than you can the CSS OM spec https://www.w3.org/TR/cssom-1/ which is old enough to buy alcohol and doesn't include a "Motivation" section.

You can often find explainer docs linked off of https://chromestatus.com/ e.g. https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/... I think you'll find that explainers are 10000% better for learning features than specs are. (They typically even discuss #3, #4, and #5, as they typically discuss alternative rejected approaches.)

Transparent ads are enabled through ad providers joining the Transparent Ads Provider program. More info on the program and the requirements for providers here - https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/TransparentAds/Program-Overview.md

Not necessarily for a Swift project, but your experience makes me wonder about the current web API for highlighting spans of text.

https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/...

Complicated...

This article serves as your comprehensive guide to mastering the art of combining Bootstrap and React seamlessly. Dive in to uncover the tips, tricks, and best practices to elevate your UI design game effortlessly.

Bootstrap is already a popular framework among the web developers. And, these free templates makes it even more convenient to use Bootstrap in your projects.

Tailwind is great, but creating everything from scratch is annoying. A nice base of components which can be extended with tailwind would be great. There are a few tailwind frameworks like Flowbite, Daisy Ui, but I like Bulma, PicoCSS and Bootstrap.

In the JavaScript world, tread cautiously on this passionate topic. https://github.com/twbs/bootstrap/issues/3057

To effectively demonstrate Secutio's capabilities for rapid web development, we've chosen the popular Bootstrap framework as a foundation. Bootstrap provides a robust and user-friendly interface, making it an ideal choice for building the project's base.

With all this preamble out of the way, we can finally focus on the app. To make it easier to build a not-awful-looking website, I installed the dash-bootstrap-components which give us access to a variety of components from the bootstrap frontend framework. This will make styling and building the app easier.

For CSS, Bootstrap is the go-to framework for many developers. But there are other popular ones too, like Angular, React, and Vue. You don't have to learn every single framework out there—just pick the ones that are most relevant to your projects and match current industry trends and your learning preferences.

For those unfamiliar with Tailwind CSS, it is a utility-first framework with pre-defined classes for you to create custom designs. Before its creation, developers who wrote CSS were limited to two options: either writing custom CSS or using a toolkit like Bootstrap. However, both approaches came with drawbacks. Writing custom CSS was a lot of work, and using Bootstrap limited you in styling unless you added custom CSS on top.

bootstrap - toolkit for styling websites. Has lots of themes and capabilities. docs

To make the demo more interesting, we will use the Bootstrap framework and Flask as the backend.