59 Matching Annotations
  1. Nov 2023
  2. Oct 2023
    1. 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.

      Good - Salesforce's template options seem like having a toolbox for the website. No need to be a coding or design guru, these templates provide a great starting point tailored to my business needs.

  3. Sep 2023
    1. 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.

      reply to u/JeffB1517 at https://www.reddit.com/r/Zettelkasten/comments/16ulsye/comment/k2mb8s2/?utm_source=reddit&utm_medium=web2x&context=3

      I've only seen some modest discussion of DDC and outside of Joseph Voros, vanishingly little discussion (much less usage) of Propædia as classification systems for zettelkasten id numbering. I'm wholly unaware of anyone actively using the Universal Decimal Classification, but would love to see examples of it in action if they exist. From where are you drawing your sampling of "lots of people"? Do you use Library of Congress classification for your own, and if so, can you provide an example of numbers and titles of half a dozen cards to demonstrate your specific method? Given the prevalence of its use in filing/ordering, I'd more likely place the ID at the top of the card over the bottom and put other links at the bottom. Is there a particular affordance that would encourage you to do it the opposite?

      Perhaps you're including it in the idea of "related notes", but I also keep a separate reference section on each card for the source or related context of the main idea or excerpted quotation.

    1. https://www.reddit.com/r/antinet/comments/16ilfgj/my_antinet_zettelkasten_setup/

      A great walkthrough of the physical pieces that a zettelkasten user is using.

      It almost borders on some of the productivity porn that is seen in the planner/productivity space.

      Not seen before: some pre-made templates for placing data on physical cards.

  4. Jul 2023
  5. scription.typepad.com scription.typepad.com
    1. https://scription.typepad.com/

      Patrick Ng seems to be the inventor of a chronodex visual planning system. His website has half yearly printable planner inserts for Midori's Traveler's Notebooks.

      One of his downloadable templates reads:

      Chronodex ideas and notations are copyrighted, it is free for personal use, please contact Patrick Ng (patrickng@mac.com) for commercial usage.

      Examples of chronodex layouts on his website show his uses which also seem to include some sketchnoting usage as well.

  6. Jun 2023
  7. Apr 2023
    1. 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.
  8. Mar 2023
    1. The beauty of FAST framework Overloaded with information → Filter Drowning in busywork → Automate Descending into chaos → Structure Doing things over and over → Templatize

      The beauty of FAST framework<br><br>Overloaded with information → Filter<br><br>Drowning in busywork → Automate<br><br>Descending into chaos → Structure<br><br>Doing things over and over → Templatize pic.twitter.com/kn6Gi27DLG

      — Andrew Altshuler (@1eo) February 4, 2023
      <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
  9. Feb 2023
  10. Jan 2023
    1. 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

      Custom .pdf planners and templates for the Supernote platform...

  11. May 2022
  12. Oct 2021
    1. 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.

      Click here to get a handle on the behavior of the expansions in multiple context.

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

      Org-roam Template has expansions with similar syntax to yasnippet!

    3. Org-roam’s templates are specified by org-roam-capture-templates
    4. Org-roam capture templates are incompatible with org-capture templates.
  13. May 2021
  14. Mar 2021
    1. 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.

      first sighting: That <template>/<slot> is part of HTML standard and the reason Svelte uses similar/same syntax is probably because it was trying to make it match / based on that syntax (as they did with other areas of the syntax, some of it even JS/JSX-like, but more leaning towards HTML-like) so that it's familiar and consistent across platforms.

    2. 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.
  15. Nov 2020
    1. Partials
    2. 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.
    3. 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.
    1. 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.
  16. Oct 2020
    1. 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.
    1. I think logic-less templates are overrated. We already have logic in components with {#if} so I don't see what the concern is about logic in templates.

    2. Arguably, it leans into JSX land—including logic in the templates.
    3. 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.
    4. Also a vote against, for the simple reason that logicless templates would be the ultimate goal for me.
    5. one of the reasons people sometimes balk at mustache-like syntax is just that: logic in the templates.
    1. 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"
    1. 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.
    2. Full-of-logic, logic-less, and less-logic solutions
    3. 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.
    1. Mustache is described as a "logic-less" system because it lacks any explicit control flow statements, like if and else conditionals or for loops
    2. 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.
  17. Aug 2020
  18. Feb 2020
  19. Feb 2018
  20. Oct 2016
  21. Jan 2016
    1. but the lack of constraints

      and hilarity ensued...MySpace is/was/never has been less templated than Wordpress. Just not as well templated as Wordpress or as peopled by good developers who add more choice via plug-ins and the WP API. But make no mistake: plug-ins are templates.

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

      This is partly true, but....every space is a templated space. Coding creates the space. Text boxes and the metaphor of page and post are templated. Just minimally so. Templates are not the boogey man. A haiku is a template, a sonnet is a template, but is anyone reasonably arguing that Basho and Shakespeare would have been better off not using them. We use templates to create buildings. We call them "forms" and use rebar and concrete to send them to the sky.