Ask any web developer: the most neglected part of their site/app is likely its CSS. Unlike other parts of the stack, most CSS is messy, complex, and long overdue for a rewrite. But it doesn’t have to be. Break out of these bad patterns by applying an object oriented CSS framework (OOCSS).
This talk will step through the process of designing, building, and implementing a custom OOCSS framework for a mid-sized web application, outlining the basic methodology, best practices, and expected outcomes, which include significant gains in both front-end performance as well as developer productivity.
Written transcript:
http://blog.kate-travers.com/how-oo-design-saved-our-css-and-site-performance/
This reference is intended to help those familiar with the Bootstrap 3 CSS framework to quickly see how to write the classes properly. For a clickable index please visit:
https://bootstrapcreative.com/resources/bootstrap-3-css-classes-index/
This document provides an overview of Drupal, an open-source content management system (CMS). It describes what Drupal is, how to get started with it, and some key concepts. Drupal allows users to easily publish and organize various types of content. It treats most content as "nodes" that are stored and organized separately from the site menu/navigation system. The document also outlines Drupal's module-based architecture and recommends several popular modules, such as CCK for custom fields and Views for displaying content.
The document is notes from a Drupal training course. It introduces some core Drupal concepts like nodes, users, and modules. It then provides an example of a birthday module that allows users to save their birthday, displays it on their profile, and shows a happy birthday message on their birthday. The module utilizes hooks, forms, blocks, and other Drupal APIs.
This document provides a 15 step tutorial for finishing a basic website in Komodo Edit. It includes instructions for adding images, styling elements with CSS, creating a navigational menu linking to additional pages, and including contact information. Key steps include positioning elements relative to their parents for absolute positioning, styling links and menus, and using CSS to control layout and formatting of text. Completing the tutorial results in a finished first page of the website with a basic structure and styling setup to build additional pages.
Harnessing the power of blue foot for developersJohn Hughes
A talk covering how developers can add new content to BlueFoot CMS in Magento 2. More details available at: http://www.magetitans.it/discovering-bluefoot-john-hughes/
Harnessing the power of BlueFoot for developers (and agencies)John Hughes
This document provides an overview of how to build a new "List Builder" page builder block for the BlueFoot page builder module in Magento. It describes creating a new "List" and child "List Item" page builder block, with attributes and templates. It also covers creating a module to define the new block types and attributes in configuration files, install scripts to populate the database, and view files for templates and block classes. The goal is to demonstrate how to extend BlueFoot to add reusable custom page content types for developers and agencies.
This document provides an overview of Object Oriented CSS (OOCSS), HTML5, and web performance. It discusses what OOCSS is, how to implement it, and why it is useful. It also briefly covers some HTML5 forms and communication features. Finally, it examines how to improve website speed. The goal is to look at these topics and discuss elegant and lean CSS as opposed to "fat sack of crap" code.
OOCSS for Javascript pirates at jQueryPgh meetupBrian Cavalier
oocss for javascript pirates provides an overview of object-oriented CSS (OOCSS) principles and how they can be applied when developing with JavaScript. OOCSS focuses on separating container and content, structure and skin, and identity versus state. It emphasizes maximizing CSS reuse and creating maintainable, concise styles. JavaScript developers can benefit from OOCSS's loose coupling of components and separation of concerns between CSS/HTML and JavaScript code. The document demonstrates how to identify OOCSS objects and implement identity and state CSS classes to control visual states from JavaScript.
This document discusses accelerated CSS techniques using tools like CSS frameworks, JavaScript, and CSS preprocessors. It introduces concepts like nested rules, variables, mixins, extends, imports, and powerful functions in CSS preprocessors that allow generating complex CSS from simpler code. CSS frameworks like Blueprint and modules for CSS3 properties are demonstrated. Image sprites are also mentioned briefly.
The document discusses the problems with CSS at large scale, including code not being reused, increasing file sizes, code being easily broken, and difficulty for new team members. It proposes a solution called OOCSS, which breaks pages into reusable components/objects. Some advantages of OOCSS include smaller file sizes, faster development by reusing code, easy adaptation for teams, and more flexibility. The document provides examples of how to structure CSS in a base/modifier class pattern and use a grid, and offers tips for implementing OOCSS.
The document is a presentation about Object Oriented CSS (OOCSS). It discusses two major OOCSS principles: 1) Separating structure and skin and 2) Separating container and content. This allows websites to be built in a modular way using "Legos" of HTML, CSS, images and JavaScript that can be reused across a site. Following OOCSS principles results in faster sites with less CSS and happier users, developers, and clients. The presentation provides examples of OOCSS code and tips for implementation.
CSS (Cascading Style Sheets) is used to describe the presentation and styles of web pages, including layout, colors, fonts, borders, and paddings. CSS specifications are developed by the W3C and used by browsers, publishers, and developers. CSS can be embedded in HTML, added via internal <style> elements, or linked via external CSS files. The document discusses CSS selectors, properties for colors, sizes, fonts, text, boxes, padding/borders/margins, backgrounds, hyperlinks, positioning, lists, and layouts. It also covers floats, flex containers, media queries, and responsive design.
This document discusses object-oriented CSS (OOCSS) as an evolution of CSS that makes it more powerful. OOCSS involves creating reusable CSS objects rather than page-specific rules, setting good global defaults, abstracting reusable elements, separating container and content, and using multiple classes to simulate inheritance. This allows for more scalable, maintainable and performant CSS code. Some best practices of OOCSS include creating semantic object classes like .heading rather than styling specific elements directly. The document provides examples of OOCSS principles and their benefits.
The document discusses CSS architecture methodology called ITCSS (Inverted Triangle CSS). ITCSS involves visualizing CSS projects as a layered inverted triangle with the following properties: from generic to explicit styles, low specificity to high specificity, and far-reaching to localized selectors. This hierarchical structure is meant to improve scalability, maintainability, and reduce conflicts. The document also discusses object-oriented CSS methodology, separating structure from skin, avoiding location-dependent styles, and using classes, mixins, extends, and preprocessors to improve reusability.
The New UI - Staying Strong with Flexbox, SASS, and {{Mustache.js}}Eric Carlisle
The document discusses a presentation on using Flexbox, SASS, and Mustache templating for building user interfaces. The presentation covers general best practices, using SASS for variables, nesting, mixins and extends, Flexbox for responsive design, and Mustache templating. The presenter is Eric Carlisle, a UI/UX architect who will demonstrate coding techniques with these tools.
OOCSS for JavaScript Pirates jQcon BostonJohn Hann
OCSS is an approach to CSS that focuses on maximizing reuse through separation of concerns. It advocates separating container styles from content and structure styles from skin/presentation styles. OCSS objects consist of HTML, CSS rules, and JavaScript behavior associated via a class name. Classes can inherit styles and states from other classes. The approach aims to create loosely coupled, maintainable CSS through principles like reuse, separation of concerns, and object-oriented modeling of components.
Structuring your CSS for maintainability: rules and guile lines to write CSSSanjoy Kr. Paul
Structuring your CSS for maintainability: rules and guile lines to write CSS
As you start work on larger stylesheets and big projects with a team, you will discover that maintaining a huge CSS file can be challenging. So, we will go through some best practices for writing CSS that will help us to maintain the CSS project easily.
The document discusses steps for developing a CSS framework, including defining layout rules, framework files, resets, grids and units, forms, tables, and generic classes. The framework is designed to be easily reusable, have a short source code, increase productivity, and decrease bugs. Key steps involve defining the layout, grids and units, resets, typography, forms and tables, and generic classes through separate CSS files.
(1) The document outlines steps to develop a CSS framework, including defining layout, grids, resets, typography, forms, tables, generic classes, components, and a default theme.
(2) Key aspects are making the framework non-intrusive with classes instead of IDs, using a generic template, and separating files for concerns like layout, grids, and components.
(3) The framework is developed by first defining the overall layout, then grids and units, resets, typography, and later more specific aspects like forms, tables, generic classes, and common components.
The document outlines steps for developing a CSS framework, including defining layout rules, framework files, resets, typography, forms and tables, and generic classes. Key steps are to 1) define a non-intrusive layout using classes instead of IDs, 2) establish a grid and unit system, and 3) include resets, typography, forms/tables, and generic styles. The goal is to create a reusable, short, and productive framework that reduces bugs.
This document discusses using CSS preprocessors like LESS, Sass, and Stylus to build mobile web apps. It covers getting started with Sass and Compass, using variables, operations, nesting, mixins, and other Sass features. It also discusses object-oriented CSS techniques like separating structure and skin, and container and content. The goal is to speed up front-end workflows and make CSS reusable, modular, and scalable.
This document discusses using OOScss architecture for Rails applications. It proposes dividing CSS into components, modules, and layouts. Placeholder selectors from Sass can be used to create reusable CSS modules without code bloat. Examples show issues with directly using Bootstrap for complex designs. Following OOScss principles like identifying reusable objects, using semantic HTML, and separating styles from content can help build custom designs on top of frameworks like Bootstrap more effectively.
The document discusses responsive web design and some best practices. It notes that responsive design is more than just fluid grids, flexible images, and media queries - it also requires considering architecture, performance, font sizing, breakpoints, image optimization, and more. The document provides tips on using relative units like ems and rems for font sizing, organizing media queries, selecting classes, and testing responsive sites.
What’s up, dudes and dudettes! Get into the totally rad world of making your website tubular with themes! In this gnarly demo, Paul is going to structure your SCSS files to be able to swap out between themes quickly! Switch from a light theme to dark-o-rama. Get your accessibility game to the max by including a colorblind-friendly theme. He’ll also set up one fresh potential build process to let you swap your themes out! This session totally demos content from his wicked talk, “Variations on a Theme“.
This document outlines the remaining classes for a web design course, including grid layout, navigation, jQuery, forms, and more. It then provides details on creating layouts using the grid framework over two classes. The first layout will be relatively simple for inside pages, while the second for the front page will be more complex. Examples of grid layout are provided. Finally, instructions are given for an assignment due November 7th involving adding content to a two-column layout and creating a header image for the front page under 940px wide.
A simple Introduction to Algorithmic FairnessPaolo Missier
Algorithmic bias and its effect on Machine Learning models.
Simple fairness metrics and how to achieve them by fixing either the data, the model, or both
More Related Content
Similar to CSMess to OOCSS: Refactoring CSS with Object Oriented Design (20)
OOCSS for Javascript pirates at jQueryPgh meetupBrian Cavalier
oocss for javascript pirates provides an overview of object-oriented CSS (OOCSS) principles and how they can be applied when developing with JavaScript. OOCSS focuses on separating container and content, structure and skin, and identity versus state. It emphasizes maximizing CSS reuse and creating maintainable, concise styles. JavaScript developers can benefit from OOCSS's loose coupling of components and separation of concerns between CSS/HTML and JavaScript code. The document demonstrates how to identify OOCSS objects and implement identity and state CSS classes to control visual states from JavaScript.
This document discusses accelerated CSS techniques using tools like CSS frameworks, JavaScript, and CSS preprocessors. It introduces concepts like nested rules, variables, mixins, extends, imports, and powerful functions in CSS preprocessors that allow generating complex CSS from simpler code. CSS frameworks like Blueprint and modules for CSS3 properties are demonstrated. Image sprites are also mentioned briefly.
The document discusses the problems with CSS at large scale, including code not being reused, increasing file sizes, code being easily broken, and difficulty for new team members. It proposes a solution called OOCSS, which breaks pages into reusable components/objects. Some advantages of OOCSS include smaller file sizes, faster development by reusing code, easy adaptation for teams, and more flexibility. The document provides examples of how to structure CSS in a base/modifier class pattern and use a grid, and offers tips for implementing OOCSS.
The document is a presentation about Object Oriented CSS (OOCSS). It discusses two major OOCSS principles: 1) Separating structure and skin and 2) Separating container and content. This allows websites to be built in a modular way using "Legos" of HTML, CSS, images and JavaScript that can be reused across a site. Following OOCSS principles results in faster sites with less CSS and happier users, developers, and clients. The presentation provides examples of OOCSS code and tips for implementation.
CSS (Cascading Style Sheets) is used to describe the presentation and styles of web pages, including layout, colors, fonts, borders, and paddings. CSS specifications are developed by the W3C and used by browsers, publishers, and developers. CSS can be embedded in HTML, added via internal <style> elements, or linked via external CSS files. The document discusses CSS selectors, properties for colors, sizes, fonts, text, boxes, padding/borders/margins, backgrounds, hyperlinks, positioning, lists, and layouts. It also covers floats, flex containers, media queries, and responsive design.
This document discusses object-oriented CSS (OOCSS) as an evolution of CSS that makes it more powerful. OOCSS involves creating reusable CSS objects rather than page-specific rules, setting good global defaults, abstracting reusable elements, separating container and content, and using multiple classes to simulate inheritance. This allows for more scalable, maintainable and performant CSS code. Some best practices of OOCSS include creating semantic object classes like .heading rather than styling specific elements directly. The document provides examples of OOCSS principles and their benefits.
The document discusses CSS architecture methodology called ITCSS (Inverted Triangle CSS). ITCSS involves visualizing CSS projects as a layered inverted triangle with the following properties: from generic to explicit styles, low specificity to high specificity, and far-reaching to localized selectors. This hierarchical structure is meant to improve scalability, maintainability, and reduce conflicts. The document also discusses object-oriented CSS methodology, separating structure from skin, avoiding location-dependent styles, and using classes, mixins, extends, and preprocessors to improve reusability.
The New UI - Staying Strong with Flexbox, SASS, and {{Mustache.js}}Eric Carlisle
The document discusses a presentation on using Flexbox, SASS, and Mustache templating for building user interfaces. The presentation covers general best practices, using SASS for variables, nesting, mixins and extends, Flexbox for responsive design, and Mustache templating. The presenter is Eric Carlisle, a UI/UX architect who will demonstrate coding techniques with these tools.
OOCSS for JavaScript Pirates jQcon BostonJohn Hann
OCSS is an approach to CSS that focuses on maximizing reuse through separation of concerns. It advocates separating container styles from content and structure styles from skin/presentation styles. OCSS objects consist of HTML, CSS rules, and JavaScript behavior associated via a class name. Classes can inherit styles and states from other classes. The approach aims to create loosely coupled, maintainable CSS through principles like reuse, separation of concerns, and object-oriented modeling of components.
Structuring your CSS for maintainability: rules and guile lines to write CSSSanjoy Kr. Paul
Structuring your CSS for maintainability: rules and guile lines to write CSS
As you start work on larger stylesheets and big projects with a team, you will discover that maintaining a huge CSS file can be challenging. So, we will go through some best practices for writing CSS that will help us to maintain the CSS project easily.
The document discusses steps for developing a CSS framework, including defining layout rules, framework files, resets, grids and units, forms, tables, and generic classes. The framework is designed to be easily reusable, have a short source code, increase productivity, and decrease bugs. Key steps involve defining the layout, grids and units, resets, typography, forms and tables, and generic classes through separate CSS files.
(1) The document outlines steps to develop a CSS framework, including defining layout, grids, resets, typography, forms, tables, generic classes, components, and a default theme.
(2) Key aspects are making the framework non-intrusive with classes instead of IDs, using a generic template, and separating files for concerns like layout, grids, and components.
(3) The framework is developed by first defining the overall layout, then grids and units, resets, typography, and later more specific aspects like forms, tables, generic classes, and common components.
The document outlines steps for developing a CSS framework, including defining layout rules, framework files, resets, typography, forms and tables, and generic classes. Key steps are to 1) define a non-intrusive layout using classes instead of IDs, 2) establish a grid and unit system, and 3) include resets, typography, forms/tables, and generic styles. The goal is to create a reusable, short, and productive framework that reduces bugs.
This document discusses using CSS preprocessors like LESS, Sass, and Stylus to build mobile web apps. It covers getting started with Sass and Compass, using variables, operations, nesting, mixins, and other Sass features. It also discusses object-oriented CSS techniques like separating structure and skin, and container and content. The goal is to speed up front-end workflows and make CSS reusable, modular, and scalable.
This document discusses using OOScss architecture for Rails applications. It proposes dividing CSS into components, modules, and layouts. Placeholder selectors from Sass can be used to create reusable CSS modules without code bloat. Examples show issues with directly using Bootstrap for complex designs. Following OOScss principles like identifying reusable objects, using semantic HTML, and separating styles from content can help build custom designs on top of frameworks like Bootstrap more effectively.
The document discusses responsive web design and some best practices. It notes that responsive design is more than just fluid grids, flexible images, and media queries - it also requires considering architecture, performance, font sizing, breakpoints, image optimization, and more. The document provides tips on using relative units like ems and rems for font sizing, organizing media queries, selecting classes, and testing responsive sites.
What’s up, dudes and dudettes! Get into the totally rad world of making your website tubular with themes! In this gnarly demo, Paul is going to structure your SCSS files to be able to swap out between themes quickly! Switch from a light theme to dark-o-rama. Get your accessibility game to the max by including a colorblind-friendly theme. He’ll also set up one fresh potential build process to let you swap your themes out! This session totally demos content from his wicked talk, “Variations on a Theme“.
This document outlines the remaining classes for a web design course, including grid layout, navigation, jQuery, forms, and more. It then provides details on creating layouts using the grid framework over two classes. The first layout will be relatively simple for inside pages, while the second for the front page will be more complex. Examples of grid layout are provided. Finally, instructions are given for an assignment due November 7th involving adding content to a two-column layout and creating a header image for the front page under 940px wide.
A simple Introduction to Algorithmic FairnessPaolo Missier
Algorithmic bias and its effect on Machine Learning models.
Simple fairness metrics and how to achieve them by fixing either the data, the model, or both
"AI in the browser: predicting user actions in real time with TensorflowJS", ...Fwdays
With AI becoming increasingly present in our everyday lives, the latest advancements in the field now make it easier than ever to integrate it into our software projects. In this session, we’ll explore how machine learning models can be embedded directly into front-end applications. We'll walk through practical examples, including running basic models such as linear regression and random forest classifiers, all within the browser environment.
Once we grasp the fundamentals of running ML models on the client side, we’ll dive into real-world use cases for web applications—ranging from real-time data classification and interpolation to object tracking in the browser. We'll also introduce a novel approach: dynamically optimizing web applications by predicting user behavior in real time using a machine learning model. This opens the door to smarter, more adaptive user experiences and can significantly improve both performance and engagement.
In addition to the technical insights, we’ll also touch on best practices, potential challenges, and the tools that make browser-based machine learning development more accessible. Whether you're a developer looking to experiment with ML or someone aiming to bring more intelligence into your web apps, this session will offer practical takeaways and inspiration for your next project.
NVIDIA’s Enterprise AI Factory and Blueprints_ Paving the Way for Smart, Scal...derrickjswork
In a landmark step toward making autonomous AI agents practical and production-ready for enterprises, NVIDIA has launched the Enterprise AI Factory validated design and a set of AI Blueprints. This initiative is a critical leap in transitioning generative AI from experimental projects to business-critical infrastructure.
Designed for CIOs, developers, and AI strategists alike, these new offerings provide the architectural backbone and application templates necessary to build AI agents that are scalable, secure, and capable of complex reasoning — all while being deeply integrated with enterprise systems.
Is Your QA Team Still Working in Silos? Here's What to Do.marketing943205
Often, QA teams find themselves working in silos: the mobile team focused solely on app functionality, the web team on their portal, and API testers on their endpoints, with limited visibility into how these pieces truly connect. This separation can lead to missed integration bugs that only surface in production, causing frustrating customer experiences like order errors or payment failures. It can also mean duplicated efforts, communication gaps, and a slower overall release cycle for those innovative F&B features everyone is waiting for.
If this sounds familiar, you're in the right place! The carousel below, "Is Your QA Team Still Working in Silos?", visually explores these common pitfalls and their impact on F&B quality. More importantly, it introduces a collaborative, unified approach with Qyrus, showing how an all-in-one testing platform can help you break down these barriers, test end-to-end workflows seamlessly, and become a champion for comprehensive quality in your F&B projects. Dive in to see how you can help deliver a five-star digital experience, every time!
Annual (33 years) study of the Israeli Enterprise / public IT market. Covering sections on Israeli Economy, IT trends 2026-28, several surveys (AI, CDOs, OCIO, CTO, staffing cyber, operations and infra) plus rankings of 760 vendors on 160 markets (market sizes and trends) and comparison of products according to support and market penetration.
Four Principles for Physically Interpretable World ModelsIvan Ruchkin
Presented by:
- Jordan Peper and Ivan Ruchkin at ICRA 2025 https://2025.ieee-icra.org/
- Yuang Geng and Ivan Ruchkin at NeuS 2025 https://neus-2025.github.io/
Paper: https://openreview.net/forum?id=bPAIelioYq
Abstract: As autonomous robots are increasingly deployed in open and uncertain settings, there is a growing need for trustworthy world models that can reliably predict future high-dimensional observations. The learned latent representations in world models lack direct mapping to meaningful physical quantities and dynamics, limiting their utility and interpretability in downstream planning, control, and safety verification. In this paper, we argue for a fundamental shift from physically informed to physically interpretable world models — and crystallize four principles that leverage symbolic knowledge to achieve these ends:
1. Structuring latent spaces according to the physical intent of variables
2. Learning aligned invariant and equivariant representations of the physical world
3. Adapting training to the varied granularity of supervision signals
4. Partitioning generative outputs to support scalability and verifiability.
We experimentally demonstrate the value of each principle on two benchmarks. This paper opens intriguing directions to achieve and capitalize on full physical interpretability in world models.
Optimize IBM i with Consulting Services HelpAlice Gray
We offers a comprehensive overview of legacy system modernization, integration, and support services. It highlights key challenges businesses face with IBM i systems and presents tailored solutions such as modernization strategies, application development, and managed services. Ideal for IT leaders and enterprises relying on AS400, the deck includes real-world case studies, engagement models, and the benefits of expert consulting. Perfect for showcasing capabilities to clients or internal stakeholders.
Wondershare Filmora 14.3.2 Crack + License Key Free for Windows PCMudasir
COPY & PASTE LINK 👉👉👉
https://pcsoftsfull.org/dl
Wondershare Filmora for Windows PC is an all-in-one home video editor with powerful functionality and a fully stacked feature set. Filmora has a simple drag-and-droptop interface, allowing you to be artistic with the story you want to create.
Pushing the Limits: CloudStack at 25K HostsShapeBlue
Boris Stoyanov took a look at a load testing exercise conducted in the lab. Discovered how CloudStack performs with 25,000 hosts as we explore response times, performance challenges, and the code improvements needed to scale effectively
--
The CloudStack European User Group 2025 took place on May 8th in Vienna, Austria. The event once again brought together open-source cloud professionals, contributors, developers, and users for a day of deep technical insights, knowledge sharing, and community connection.
Eating Our Own Dog Food: How to be taken seriously when it comes to adding va...UXPA Boston
As user experience professionals, we've had a better-than-front-row seat when it comes to understanding the humans who try to use our products, services, and platforms. We've been on or in the field, researching users, gaining deep empathy and insights, and finding how to pull business and user needs together, for the happiest Venn diagram since "you got your chocolate in my peanut butter." We've gotten really good at this. When given some room and runway, we've turned journeys that were fraught with friction into seamless experiences for customers, clients, employees, patients, and so many other kinds of users. There's just one problem. Like the accountant, attorney, marketer, and more, we've been struck —mightily — by the curse of knowledge. We have our own jargon, which has become our seemingly secret internal UX code. We can talk in concepts with each other toward great results but, when we talk to our peers, stakeholders, leadership, and others, we forget to tailor our business and technology to their human needs. So they get lost, confused, and frustrated. In these cases, we're providing a terrible user experience. Eating Our Own Dog Food will give you a more objective way to view, talk about, and show the tremendous value that UX brings to the table, in a way that our users in this circumstance can understand it, be energized by it, and be sure to invite us to "the table."
Managing Geospatial Open Data Serverlessly [AWS Community Day CH 2025]Chris Bingham
At the AWS Community Day 2025 in Dietlikon I presented a journey through the technical successes, service issues, and open-source perils that have made up the paddelbuch.ch story. With the goal of a zero-ops, (nearly) zero-cost system, serverless was the apparent technology approach. However, this was not without its ups and downs!
For those who have ever wanted to recreate classic games, this presentation covers my five-year journey to build a NES emulator in Kotlin. Starting from scratch in 2020 (you can probably guess why), I’ll share the challenges posed by the architecture of old hardware, performance optimization (surprise, surprise), and the difficulties of emulating sound. I’ll also highlight which Kotlin features shine (and why concurrency isn’t one of them). This high-level overview will walk through each step of the process—from reading ROM formats to where GPT can help, though it won’t write the code for us just yet. We’ll wrap up by launching Mario on the emulator (hopefully without a call from Nintendo).
Building Connected Agents: An Overview of Google's ADK and A2A ProtocolSuresh Peiris
Google's Agent Development Kit (ADK) provides a framework for building AI agents, including complex multi-agent systems. It offers tools for development, deployment, and orchestration.
Complementing this, the Agent2Agent (A2A) protocol is an open standard by Google that enables these AI agents, even if from different developers or frameworks, to communicate and collaborate effectively. A2A allows agents to discover each other's capabilities and work together on tasks.
In essence, ADK helps create the agents, and A2A provides the common language for these connected agents to interact and form more powerful, interoperable AI solutions.
Fully Open-Source Private Clouds: Freedom, Security, and ControlShapeBlue
In this presentation, Swen Brüseke introduced proIO's strategy for 100% open-source driven private clouds. proIO leverage the proven technologies of CloudStack and LINBIT, complemented by professional maintenance contracts, to provide you with a secure, flexible, and high-performance IT infrastructure. He highlighted the advantages of private clouds compared to public cloud offerings and explain why CloudStack is in many cases a superior solution to Proxmox.
--
The CloudStack European User Group 2025 took place on May 8th in Vienna, Austria. The event once again brought together open-source cloud professionals, contributors, developers, and users for a day of deep technical insights, knowledge sharing, and community connection.
Setting up a local cloud environment for development and testing can be complex, but with Apache CloudStack and KVM, it becomes a powerful and flexible solution. This talk guided attendees through the process of creating a fully functional CloudStack-powered private cloud on a local machine or server, using KVM as the hypervisor and Ansible for automation.
--
The CloudStack European User Group 2025 took place on May 8th in Vienna, Austria. The event once again brought together open-source cloud professionals, contributors, developers, and users for a day of deep technical insights, knowledge sharing, and community connection.
13. MODULAR
Coupled to single view
Too brittle / specific to re-use
ENCAPSULATED
Specificity wars
MAINTAINABLE
14. MODULAR
Coupled to single view
Too brittle / specific to re-use
ENCAPSULATED
Specificity wars
Unpredictable behavior
MAINTAINABLE
15. MODULAR
Coupled to single view
Too brittle / specific to re-use
ENCAPSULATED
Specificity wars
Unpredictable behavior
MAINTAINABLE
16. MODULAR
Coupled to single view
Too brittle / specific to re-use
ENCAPSULATED
Specificity wars
Unpredictable behavior
MAINTAINABLE
Writing new CSS for every view
17. MODULAR
Coupled to single view
Too brittle / specific to re-use
ENCAPSULATED
Specificity wars
Unpredictable behavior
MAINTAINABLE
Writing new CSS for every view
Difficult to onboard new team members
61. /* Block component */
.list
/* Child element of parent block */
.list__card
/* Modifier that changes the style of the block */
.list--accordion
.list--spacing-large
82. QA testing: feature turned on for select user groups
Training session on rewriting existing markup
PHASE 2
83. QA testing: feature turned on for select user groups
Training session on rewriting existing markup
Identify & assign views for “hands-on learning” rewrites
PHASE 2