Einfache Struktur: Events – Episode – Analysis Beim Start meiner Challenge habe ich bewusst eine schlanke Form gewählt. In Richards & Farrell bin ich auf ein Modell gestossen, das mir sofort einleuchtete: Events – Episode – Analysis. Events: kurze, stichwortartige Notizen zu den wichtigsten Geschehnissen der Lektion. Episode: eine kleine Szene, die ich erzählerisch ausformuliere: vielleicht eine gute Diskussion, vielleicht ein technisches Problem. Analysis: meine Gedanken dazu: Warum war diese Episode wichtig? Was hat dazu geführt? Und was nehme ich mir für die nächste Einheit vor?

When shallow routing, you may want to render another +page.svelte inside the current page.

Is it that we each do our own thing and we develop some form of in a collegiality between us, how to go forward?

Some frameworks call this “template inheritance”. In this example, we might say that the application layout “inherits from” or “extends” the base layout. In Rails, this is known as nested layouts, and it is a bit awkward to use. The standard Rails practice for nested layouts is complicated and involves these considerations

But what if you want to reuse one layout within another?

Here’s my common practice: Every page in the app needs the standard HTML boilerplate with my common stylesheets and JavaScripts. I need a layout that provides these, but makes no assumptions on the actual body of the page. This is my “base” layout. Most – but not all – pages in the app need a common header and footer. This is my “application” (default) layout. I’d like the application layout to reuse the base layout to keep my code DRY.

PDF Index Card Calendars 4 little templates for printing directly to 3 x 5 and 4 x 6 index cards (with the dates already filled in). Perfect for the Hipster PDA and other compact GTD organizational systems.

Out-of-the-box, Salesforce gives you ten pre-built, customizable templates to choose from. Let’s look at the most outstanding ones, summarizing their features and benefits.

I'm a huge fan of digital over paper but what would you want on the custom stationary. A typical paper Zettle has:A unique identifier line or boxA content section (I'd assume that can be most of the front and all the backA related notes section.I'd think a typical 5x7 index card with (3) in the top area, (1) in the lower left and (2) on all the rest does the trick.The main place I could see stationary helping is if you want the identifier to have distinguished sections. For example lots of people are using the Dewey Decimal System or Britanica Propedia classification for simplicity ... while I think Library of Congress classification makes more sense since it is available and agreed by the publisher. You could potentially use both in the ID section.

W3.CSS Intro (Kitchen Sink)

Responsive Image Gallery How to use CSS media queries to create a responsive image gallery that will look good on desktops, tablets and smart phones.

The beauty of FAST framework Overloaded with information → Filter Drowning in busywork → Automate Descending into chaos → Structure Doing things over and over → Templatize

Link to the planner in the video, FREE on github: https://github.com/kudrykv/latex-year... + generated planners from 2022-2032 here: https://github.com/kudrykv/latex-year... (the exact one in the video is sn_a5x.breadcrumb.dotted.default.ampm.dailycal.2022) ► A bunch of FREE Supernote templates at this link: https://supernote-templates.mostlyuse... CUSTOMIZABLE TEMPLATES ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ Use these mix-and-match modules to easily make custom templates! 🛒 My shop on Etsy: https://www.etsy.com/shop/pixelleaves Layouts for the Kindle Scribe, Remarkable, Onyx Boox, and Supernote e-ink tablets available

If foo is a function, foo is called with the current node as its argument. Else if org-roam-node-foo is a function, foo is called with the current node as its argument. The org-roam-node- prefix defines many of Org-roam’s node accessors such as org-roam-node-title and org-roam-node-level. Else look up org-roam-capture--info for foo. This is an internal variable that is set before the capture process begins. If none of the above applies, read a string using completing-read. Org-roam also provides the ${foo=default_val} syntax, where if a default value is provided, will be the initial value for the foo key during minibuffer completion.

Org-roam provides the ${foo} syntax for substituting variables with known strings. ${foo}’s substitution is performed as follows:

Org-roam’s templates are specified by org-roam-capture-templates

Org-roam capture templates are incompatible with org-capture templates.

My preference here is biased by the fact that I spend everyday at work building web components, so Svelte's approach feels very familiar to slots in web components.

I was pleasantly surprised by Svelte's templating; in the past I've found templating languages overwhelming and inflexible, but Svelte offers just the right amount of templating whilst enabling you to use JavaScript too.

Partials

We all know that real business logic does not belong in the presentation layer, but what about simple presentation-oriented things like coloring alternate rows in table or marking the selected option in a <select> dropdown? It seems equally wrong to ask the controller/business logic code to compute these down to simple booleans in order to reduce the logic in the presentation template. This route just lead to polluting the business layer code with presentation-oriented logic.

Templates with logic versus "logic-less" templates is a hotly debated point among template language designer and users. Dust straddles the divide by adopting a "less logic" stance.

The success of JSX has proved that the second curly is unnecessary. Moreover, a lot of people — particularly those who have been exposed to React — have a visceral negative reaction to double curlies, many of them assuming that it brings with it all the limitations of crusty old languages like Mustache and Handlebars, where you can't use arbitrary JavaScript in expressions.

Then at some moment I just stumbled upon limitations and inexpressiveness of templates and started to use JSX everywhere — and because JSX was not a typical thing for Vue I switched to React over time. I don’t want to make a step back.

Arguably, it leans into JSX land—including logic in the templates.

I could imagine people putting a more complex expression in an @const than we typically find in svelte expressions today, which might create more demand for those blocks to have TypeScript support, which I don't think they have now.

Also a vote against, for the simple reason that logicless templates would be the ultimate goal for me.

one of the reasons people sometimes balk at mustache-like syntax is just that: logic in the templates.

IMO svelte does have a responsibility to teach/demo the basics of "functional javascript" probably as a docs/tutorial/demos chapter on "the power of javascript expressions"

Writing a logic-less template requires a bloated view model with comprehensive getters for the raw data. As a result, a messy and difficult-to-maintain view model usually accompanies logic-less templates.

Full-of-logic, logic-less, and less-logic solutions

that does not mean that I am advocating the other extreme–i.e., a templating language that allows a lot of logic. I find such templating languages, especially those that allow the host programming languages to be used inside the template, to be hard to read, hard to maintain, and simply a bad choice.

Mustache is described as a "logic-less" system because it lacks any explicit control flow statements, like if and else conditionals or for loops

Here, when x is a Boolean value then the section tag acts like an if conditional, but when x is an array then it acts like a foreach loop.

Strategic Planning with Remote Teams: Does it really work?

Remote collaboration pain? Try a dash of Google Drawings!

Over 5000 Free Templates

but the lack of constraints

A hand-built site is much less templated, as one is free to fully create their digital self in any way possible.