Autor: Johann Franz [Freising, Bischof]
Erschienen 1695
BSB-Signatur Cgm 2268(4

URN: urn:nbn:de:bvb:12-bsb00003723-2
URL: http://daten.digitale-sammlungen.de/~db/0000/bsb00003723/images/

Preaching Today provides pastors and preachers sermon prep help with sermon illustrations, sermons, sermon ideas, and preaching articles.

Germany’s energy network nearly broken down in January because of poor execution from wind turbines and sun based boards, as indicated by information from a noteworthy exchange union. Wind and sunlight based power plants failed to meet expectations in January, 2017, as a result of shady climate with almost no wind, setting the phase for …

The post Germany Facing Mass Blackouts Because The Wind And Solar Won’t Cooperate appeared first on LatestSolarNews.

The future is solar LED lights. You will see them in the parking lots and other large areas around a city. They are cheap and save a good deal of money on electricity bills. Nowadays, the majority of parking lots feature the conventional lights that get their power from the grid. These products are not …

The post 4 Benefits Of Solar LED Lights For Parking Lots appeared first on LatestSolarNews.

At some point, while working on the MontageJS framework, the question came up what CSS naming convention we should start using. After a long discussion we settled on using the BEM methodology, but changed the syntax a bit. To keep this post short, I won’t go into detail why using BEM is a good idea, but rather explain why we chose a different syntax. Here some examples:

.digit-Progress          /* org-Component */
.digit-Progress-bar      /* org-Component-childElement */
.digit-Progress--small   /* org-Component--variation */

Note: The org- (digit-) prefix is used as a name-space so it wouldn’t conflict with other packages/libraries/frameworks.

Now let’s take a look at the reasons for choosing such a syntax.

Hyphens (-)

The main reason why we’re using a hyphen (-) instead of underscores (_), has to do with the fact that their behavior is different when double-clicking to select text. Try for yourself:

component__element /* underscores */
component-element  /* hyphen */

See how when you’re using underscores it selects the part before and after, in this case the whole component__element. But with hyphens it let’s you select only the part you double-clicked. component OR element. This let’s you quickly edit only the parts you want:

camelCase

Now, what if the component or child element consists of multiple words? We could use underscores like component_name-element_name. It would still be double-clickable, but readability suffers since it’s harder to see what belongs together. Better to use camelCase which groups each part visually: componentName-elementName.

MainComponent

OK, I think we’re getting closer. As a last rule, for the “main” component we use PascalCase. The reason for it is to add emphasis and make it easier to distinguish the main component from a child element. Also when using a namespace, the component moves to the second position, which makes it even more important to have it stick out: org-Component-childElement

–variation

We kept the more commonly used double hyphens (–) for variations. digit-Progress--small. It makes sense, because it pulls the variation (–small) visually more apart and makes it look like it’s something “different” than the default component.

So that’s about it. For more details about this naming convention, take a look at the SUIT framework, which also started to use the same syntax and documented it really well.

In the end, whatever Shade of BEM you choose to cook with probably depends on your personal taste, but thinking about a great UX by improving usability and readability won’t hurt either.

One of the struggles that marketers face is how to send the right message at exactly the right time to target people in a way that will appeal to them. To solve the problem, businesses need to get themselves acquainted with new technologies and the power of personalization. In the past few years, digital marketing […]

Content Management Systems are arguably the internet’s most powerful web development tool. In a rapidly growing market where every business under the sun requires a website that is not only fully functioning, but optimised, easy to update regularly, and implement the latest features, the right CMS is important. As a web developer it can be […]

The first global pandemic of the digital era is upon us. We’re living in unprecedented and uncomfortable times. For our senior citizens, these past several weeks have been particularly discomforting. According to the CDC, men and women over the age of 65 are significantly more likely to develop complications from COVID-19. As we seek to […]

Rotch Library - TR184.B75 2018

Rotch Library - N7425.D459 2018

Rotch Library - N6488.I8 V433 2019 Y8

Rotch Library - N6948.5.D42 M6613 2019

Rotch Library - TR647.P37 2018

Rotch Library - NX512.3.A35 Z67 2019

Rotch Library - N6498.V53 B15 2018

Rotch Library - N8251.S555 A48 2018

Rotch Library - N6496.3.S9 Z876 2018

Rotch Library - N6659.M55 A4 2018

Rotch Library - N6488.I8 V433 2019 A38

Rotch Library - ND673.K396 A4 2019

Rotch Library - NX460.5.P47 G65 2018

Rotch Library - N7255.P6 E88 2018

Rotch Library - N6488.I8 V433 2019 S6

Rotch Library - N6488.I8 V433 2019 R6

Rotch Library - NC251.M64 J35 2018

Rotch Library - N6488.I8 V433 2019 C2

Rotch Library - N72.A76 O47 2019

Rotch Library - ND673.B73 B46 2018

Rotch Library - TR185.P52 2018

Barker Library - NX650.M6 M663 2018

Rotch Library - N6488.I8 V433 2019 A9

Rotch Library - ND723.K53 A4 2018

Barker Library - NC975.5.K78 A2 2018

Rotch Library - N8214.5.F8 C539 2019

Rotch Library - N7274.S76 2019

Rotch Library - TR350.P53 2018

Rotch Library - N72.G55 M63 2020

Rotch Library - N6260.S56 2019

Online Resource