Great question! Let’s break down the reasoning behind this choice, especially compared to the more simplified workshop examples:

• Separation of concerns: Targeting vs. styling

  • The id="map" is non-negotiable for OpenLayers itself—this is how the library identifies the exact DOM element to mount the map instance. IDs are unique by definition, so there’s no risk of the library picking the wrong element.
  • The class="ol-map" is for reusable, pre-built CSS styles from OpenLayers. This class handles default layout rules like setting dimensions, hiding overflow, and ensuring the map renders correctly. Using a class here means you can apply the same base styles to multiple map containers later if needed, without duplicating CSS.

• Teaching core concepts to beginners

  • The quickstart is tailored for first-time users. By showing both selectors, it explicitly teaches two critical skills:
    • How to connect the map object to a DOM element (via ID)
    • How to leverage OpenLayers’ default styling (via the pre-defined class)
  • Workshop examples assume you already understand these fundamentals, so they streamline the code to focus only on the essential ID for targeting.

• Following CSS best practices

  • Even in simple apps, using classes for styling aligns with standards like the Airbnb CSS guide you referenced. It keeps your styles modular—if you later want to customize map appearance, you can modify the class styles without touching the JavaScript that targets the ID. This separation makes the code easier to maintain as your app scales.

• Consistency with library conventions

  • OpenLayers has used the ol-map class for default styles for years. Including it in the quickstart ensures consistency with older codebases and makes it smoother to transition to more complex setups where you might extend or override those default styles.

内容的提问来源于stack exchange，提问作者Kit Macleod