Pet Plate

petplate

Optimizing Tech Design Meetings with Structured Ticket Templates

Optimaliseer tegniese ontwerpvergaderings met gestruktureerde kaartjiesjablone

Аптымізацыя сустрэч па тэхнічным дызайне з дапамогай структураваных шаблонаў білетаў

Optimalizace schůzek technického designu pomocí strukturovaných šablon vstupenek

Optimización de reuniones de diseño tecnológico con plantillas de tickets estructuradas

構造化されたチケット テンプレートを使用して技術設計会議を最適化する

ტექნიკური დიზაინის შეხვედრების ოპტიმიზაცია ბილეთების სტრუქტურირებული შაბლონებით

Оптимизирање на состаноци за технолошки дизајн со структурни шаблони за билети

संरचित टिकट टेम्प्लेटहरूको साथ टेक डिजाइन बैठकहरू अनुकूलन गर्दै

Optimaliseren van technische ontwerpvergaderingen met gestructureerde ticketsjablonen

Go kaonafatša Dikopano tša Moralo wa Theknolotši ka Dithempleite tša Thekethe tše di Rulagantšwego

د جوړښت شوي ټکټ ټیمپلیټونو سره د ټیک ډیزاین غونډې اصلاح کول

Ukuthuthukisa Imihlangano Yedizayini Yezobuchwepheshe Ngezifanekiso Zamathikithi Ahleliwe

How to Use Docker to Template Local Database

I’ve always been inspired by the openness within the developer community—the way they freely share solutions and source code for anyone to explore. Beyond the vast array of available learning materials and self-study courses, there are entire repositories filled with code you can dive into, adapt, learn, and borrow solutions from for your projects. In contrast, the graphic design world tends to be more closed off. Designers often showcase only final results, with little insight into their creative process. For me, the openness in development helps move the whole field forward. We all benefit from those contributions when everyone can access knowledge and tools. A Multidisciplinary Approach to Design While graphic design has always been my core focus, I’ve been drawn to other fields that intersect with it—motion design, illustration, typography, photography, and digital design. This doesn't mean I have mastered each profession (there are always far more experienced professionals in each specific field), but I believe in a multidisciplinary approach. Understanding the foundations of a field before diving into it helps shape your design perspective and ensures that the practical aspects of the medium inform your work. For instance, in graphic design, it’s important to understand the specifics of printing before preparing a layout. That knowledge guides the design process. Similarly, when I began designing a website for my design studio, I became interested in front-end and back-end website development. At that time, I had some knowledge of HTML, CSS, and a little JavaScript, so the first version of the site I built manually without any CMS. But soon, I realized I needed a more flexible content management system. Exploring CMS Options A developer friend of mine recommended Kirby, a flexible and user-friendly file-based PHP CMS that’s ideal for small sites. Using it helped me understand the core concept of setting up content management systems and integrating it with the frontend, which had previously felt so complex. Later I even built a student exhibition website using Kirby, where 150 students uploaded their work themselves, but that’s a story for another day. This opened the door for me to explore new tools, and I started experimenting with Gatsby (a React-based framework for static sites) and Sanity (a headless CMS). I set myself a challenge: to update my portfolio website using these tools to learn more about them. In that process, I was greatly helped by the large amount of knowledge, documentation, and video tutorials available: it's a fascinating process. Once I finished and published my studio’s website, I had an idea. Why not create a tool for other designers? Specifically, an open-source portfolio template that any designer or visual creator could use to build their own website. Visual-First Approach & Customisation There are plenty of portfolio templates built with Next.js which can be easily deployed on Vercel. But those templates are usually made for developers with a focus on development specifics. Designers, on the other hand, need a different approach—one that highlights their visual work. That’s why, for this template, I used a grid layout with large project previews and project pages that emphasize imagery and content. Customization is also key for designers. When building the template, I included features like setting custom background and text colors, reordering projects displayed on the main page, and creating project pages using modular content blocks—images, video embeds, and text. The idea is to be able to easily compile a story about a particular project out of predefined content pieces, creating an ideal visual storytelling. I used Tailwind CSS for the frontend, which makes styling and adapting content for different devices extremely easy. Thanks to Sanity’s powerful content management and the integration with Next.js, users can update content without needing to rebuild with each content update through Webhook-triggered Incremental Static Revalidation. This makes it easy to populate the portfolio with projects from scratch, keep it updated, and add projects on the go when a new project is completed and ready to be published. Easy Deployment and Accessibility Using Vercel, a user can deploy a copy of their own website with just one click, even with no development experience. The only thing needed is to register a set of free accounts: GitHub, Vercel, and Sanity. And for those who are more technically inclined, the code is open-source, so they can tweak it to suit their needs. Vercel and Sanity have more than enough traffic and content storage for a small portfolio site, and with the provided CDN, loading time is minimized, which is important for a site with a large amount of visual content. The only thing left is to connect a custom domain, which will make the portfolio site truly personal for the designer. This template is perfect for junior and experienced designers, even small design studios. One of the biggest challenges for designers in creating a portfolio is the blank page syndrome—getting stuck while being overwhelmed with designing and structuring their future portfolio website. I’ve taken care of the design and layout part, so all designers need to do is select their best projects and publish them. I named the template Collected, as it’s a place to collect and showcase the best work. I’ve created a small dedicated website to showcase the template, complete with a visual overview, a demo version, step-by-step instructions, and a video screencast where I show how to set up a portfolio website. My goal is to make the process as intuitive and visual as possible, showing designers how they can easily create a professional portfolio site without development experience. collected.to What’s next Looking ahead, I plan to keep expanding the template’s functionality. I want to add options for choosing fonts from Google Fonts, changing the grid’s column layout on the main page, and adding even more flexibility in the project page builder. I’m excited to see how the design community will use and adapt this project. Some of my fellow designers have already shared their work using this template, and I am thrilled to see what they have created. I think that by encouraging a culture of openness, we can push design forward, creating better tools and more collaborative opportunities, similar to what I've seen in the developer community. I hope this project will inspire more designers to explore the technical aspects of their craft, as understanding the tools we use is as important as creating designs in today's digital world. The complete source code for this project can be found on GitHub. I’ve always been inspired by the openness within the developer community—the way they freely share solutions and source code for anyone to explore. Beyond the vast array of available learning materials and self-study courses, there are entire repositories filled with code you can dive into, adapt, learn, and borrow solutions from for your projects. In contrast, the graphic design world tends to be more closed off. Designers often showcase only final results, with little insight into their creative process. For me, the openness in development helps move the whole field forward. We all benefit from those contributions when everyone can access knowledge and tools. A Multidisciplinary Approach to Design While graphic design has always been my core focus, I’ve been drawn to other fields that intersect with it—motion design, illustration, typography, photography, and digital design. This doesn't mean I have mastered each profession (there are always far more experienced professionals in each specific field), but I believe in a multidisciplinary approach. Understanding the foundations of a field before diving into it helps shape your design perspective and ensures that the practical aspects of the medium inform your work. For instance, in graphic design, it’s important to understand the specifics of printing before preparing a layout. That knowledge guides the design process. Similarly, when I began designing a website for my design studio, I became interested in front-end and back-end website development. At that time, I had some knowledge of HTML, CSS, and a little JavaScript, so the first version of the site I built manually without any CMS. But soon, I realized I needed a more flexible content management system. Exploring CMS Options A developer friend of mine recommended Kirby , a flexible and user-friendly file-based PHP CMS that’s ideal for small sites. Using it helped me understand the core concept of setting up content management systems and integrating it with the frontend, which had previously felt so complex. Later I even built a student exhibition website using Kirby, where 150 students uploaded their work themselves, but that’s a story for another day. This opened the door for me to explore new tools, and I started experimenting with Gatsby (a React-based framework for static sites) and Sanity (a headless CMS). I set myself a challenge: to update my portfolio website using these tools to learn more about them. In that process, I was greatly helped by the large amount of knowledge, documentation, and video tutorials available: it's a fascinating process. Kirby Gatsby Sanity Once I finished and published my studio’s website, I had an idea. Why not create a tool for other designers? Specifically, an open-source portfolio template that any designer or visual creator could use to build their own website. Visual-First Approach & Customisation There are plenty of portfolio templates built with Next.js which can be easily deployed on Vercel. But those templates are usually made for developers with a focus on development specifics. Designers, on the other hand, need a different approach—one that highlights their visual work. That’s why, for this template, I used a grid layout with large project previews and project pages that emphasize imagery and content. Customization is also key for designers. When building the template, I included features like setting custom background and text colors, reordering projects displayed on the main page, and creating project pages using modular content blocks—images, video embeds, and text. The idea is to be able to easily compile a story about a particular project out of predefined content pieces, creating an ideal visual storytelling. I used Tailwind CSS for the frontend, which makes styling and adapting content for different devices extremely easy. Thanks to Sanity’s powerful content management and the integration with Next.js, users can update content without needing to rebuild with each content update through Webhook-triggered Incremental Static Revalidation. This makes it easy to populate the portfolio with projects from scratch, keep it updated, and add projects on the go when a new project is completed and ready to be published. Easy Deployment and Accessibility Using Vercel, a user can deploy a copy of their own website with just one click, even with no development experience. The only thing needed is to register a set of free accounts: GitHub, Vercel, and Sanity. And for those who are more technically inclined, the code is open-source , so they can tweak it to suit their needs. Vercel and Sanity have more than enough traffic and content storage for a small portfolio site, and with the provided CDN, loading time is minimized, which is important for a site with a large amount of visual content. The only thing left is to connect a custom domain, which will make the portfolio site truly personal for the designer. open-source This template is perfect for junior and experienced designers, even small design studios. One of the biggest challenges for designers in creating a portfolio is the blank page syndrome—getting stuck while being overwhelmed with designing and structuring their future portfolio website. I’ve taken care of the design and layout part, so all designers need to do is select their best projects and publish them. I named the template Collected , as it’s a place to collect and showcase the best work. I’ve created a small dedicated website to showcase the template, complete with a visual overview, a demo version, step-by-step instructions, and a video screencast where I show how to set up a portfolio website. My goal is to make the process as intuitive and visual as possible, showing designers how they can easily create a professional portfolio site without development experience. Collected collected.to collected.to collected.to What’s next Looking ahead, I plan to keep expanding the template’s functionality. I want to add options for choosing fonts from Google Fonts, changing the grid’s column layout on the main page, and adding even more flexibility in the project page builder. I’m excited to see how the design community will use and adapt this project. Some of my fellow designers have already shared their work using this template, and I am thrilled to see what they have created. I think that by encouraging a culture of openness, we can push design forward, creating better tools and more collaborative opportunities, similar to what I've seen in the developer community. I hope this project will inspire more designers to explore the technical aspects of their craft, as understanding the tools we use is as important as creating designs in today's digital world. The complete source code for this project can be found on GitHub. The complete source code for this project can be found on GitHub . GitHub

Bridging Design and Development: Creating an Open-Source Portfolio Website Template for Designers

TL;DR The templating engine will give us the ability to use res.render() instead of res.send()
res.engine() will decide what res.render() will send Start Here We will create a directory which will contain our custom files inside. We will give it custom extension. In this tutorial, my extension will be "kanby". Lets create our custom files in that pages folder. Now its time to create our template engine. First we import required packages const express = require("express");
const fs = require("fs"); Then write that how you want your template engine to work app.engine('kanby', (filePath, options, callback) => { 
  fs.readFile(filePath, (err, content) => {

    // Error handler
    if (err) return callback(err)
    
    // process the content of file here
    // you can custumize however you want
    // this will change only #title# and #message#
    // but you can do advenced stuff with regular expressions. 
    // this example is the example used in express js docs
    const rendered = content.toString()
      .replace('#title#', `<title>${options.title}</title>`)
      .replace('#message#', `<h1>${options.message}</h1>`)
    return callback(null, rendered)
  })
}) After that, you need to define 2 more setting. app.set('views', './pages') // specify the directory for pages
app.set('view engine', 'kanby') // register the template engine Then you are ready ! You can use res.render() function to render your own files. app.get('/', (req, res) => {
  res.render('landingpage', { title: 'Hey', message: 'Hello there!' })
}) First it will render landingpage.kanby, the it will send rendered content to client. please do not forget to add status code res.status(200).render(); Future Plans This is basically an entrance for templating engine development. This is so simple. In my further blogs, i am thinking to create an advanced (usable) template engine for express JS. If you have any questions, Here is my Instagram @emrekanbay.en TL;DR The templating engine will give us the ability to use res.render() instead of res.send() res.engine() will decide what res.render() will send The templating engine will give us the ability to use res.render() instead of res.send() res.render() res.send() res.engine() will decide what res.render() will send res.engine() res.render() Start Here We will create a directory which will contain our custom files inside. We will give it custom extension. In this tutorial, my extension will be "kanby". Lets create our custom files in that pages folder. Now its time to create our template engine. First we import required packages First const express = require("express");
const fs = require("fs"); const express = require("express");
const fs = require("fs"); Then write that how you want your template engine to work app.engine('kanby', (filePath, options, callback) => { 
  fs.readFile(filePath, (err, content) => {

    // Error handler
    if (err) return callback(err)
    
    // process the content of file here
    // you can custumize however you want
    // this will change only #title# and #message#
    // but you can do advenced stuff with regular expressions. 
    // this example is the example used in express js docs
    const rendered = content.toString()
      .replace('#title#', `<title>${options.title}</title>`)
      .replace('#message#', `<h1>${options.message}</h1>`)
    return callback(null, rendered)
  })
}) app.engine('kanby', (filePath, options, callback) => { 
  fs.readFile(filePath, (err, content) => {

    // Error handler
    if (err) return callback(err)
    
    // process the content of file here
    // you can custumize however you want
    // this will change only #title# and #message#
    // but you can do advenced stuff with regular expressions. 
    // this example is the example used in express js docs
    const rendered = content.toString()
      .replace('#title#', `<title>${options.title}</title>`)
      .replace('#message#', `<h1>${options.message}</h1>`)
    return callback(null, rendered)
  })
}) After that, you need to define 2 more setting. app.set('views', './pages') // specify the directory for pages
app.set('view engine', 'kanby') // register the template engine app.set('views', './pages') // specify the directory for pages
app.set('view engine', 'kanby') // register the template engine Then you are ready ! You can use res.render() function to render your own files. res.render() app.get('/', (req, res) => {
  res.render('landingpage', { title: 'Hey', message: 'Hello there!' })
}) app.get('/', (req, res) => {
  res.render('landingpage', { title: 'Hey', message: 'Hello there!' })
}) First it will render landingpage.kanby, the it will send rendered content to client. please do not forget to add status code res.status(200).render(); res.status(200).render(); Future Plans This is basically an entrance for templating engine development. This is so simple. In my further blogs, i am thinking to create an advanced (usable) template engine for express JS. If you have any questions, Here is my Instagram @emrekanbay.en @emrekanbay.en

Template Engine For Express JS

The template below has consistently brought me success; it’s an outstanding method for organizing technical articles. Template Introduction
    Learning Objectives
    Prerequisites
    Getting Started
      Sub Topics 1
        Code Examples for Each Sub-Topic
        Output
      Sub Topics 2
        Code Examples for Each Sub-Topic
        Output
    Final Thoughts/Conclusion
    Github Sample (If Applicable)
    Impressum Here’s a List of Statistics That Demonstrate the Success of Following This Template: Tip 1: How to Write an Introduction Writing a compelling introduction is crucial for grabbing the reader’s attention and setting the base for the article's contents. Clearly define the topic of the article
Briefly explain why the topic is important
Define the problem you’re trying to solve
Set tone Tip 2: How to Write Learning Objectives Define what the reader is going to learn after finishing the story. Clearly define the skills the reader will gain
Don’t write what you aren’t delivering. Example Tip 3: How to Write Prerequisites Define what knowledge or skills are required to understand the article. Identify the Required Knowledge or Skills Example Tip 4: How to Write “Getting Started” The simplest trick is to divide the content into sub-topics and create a section for the same. Example Divide each section with a paragraph and code example for each of the sub-sections. Bonus: Add the output of the code as a screenshot or GIF if applicable. Tip 5: How to Write “Final Thoughts/Conclusion” Summarize key points.
Highlight the takeaways.
Provide CTA (Call to Action) if applicable. Tip 6: Github Sample This section can be optional, but if you add a GitHub sample, it enhances the article in many ways. It acts as a testament to the code examples above.
Enhance learning with practical examples.
Improve SEOs too.
Most Devs are searching on Google to solve a problem, and a GitHub sample makes their life easier. Tip 7: Add Impressum An Impressum provides more information about the author; it adds professionalism and credibility to the story. Keep it short and crisp.
Don’t add too many links.
Don’t ask for claps as the Medium doesn't encourage it. Medium Impressum Example C# Programming🚀 Thank you for being a part of the C# community! Before you leave: Follow us: Youtube | X | LinkedIn | Dev.to Visit our other platforms: GitHub Conclusion The above template has proven to be highly successful for writing technical articles, engaging readers, and providing a standard structure to the stories Including a GitHub sample further solves the challenges a dev faces while looking for practical implementations of the code. The structure makes the content more memorable & actionable. More Cheatsheets Cheat Sheets — .Net The template below has consistently brought me success; it’s an outstanding method for organizing technical articles. Template Introduction
    Learning Objectives
    Prerequisites
    Getting Started
      Sub Topics 1
        Code Examples for Each Sub-Topic
        Output
      Sub Topics 2
        Code Examples for Each Sub-Topic
        Output
    Final Thoughts/Conclusion
    Github Sample (If Applicable)
    Impressum Introduction
    Learning Objectives
    Prerequisites
    Getting Started
      Sub Topics 1
        Code Examples for Each Sub-Topic
        Output
      Sub Topics 2
        Code Examples for Each Sub-Topic
        Output
    Final Thoughts/Conclusion
    Github Sample (If Applicable)
    Impressum Here’s a List of Statistics That Demonstrate the Success of Following This Template: Tip 1: How to Write an Introduction Writing a compelling introduction is crucial for grabbing the reader’s attention and setting the base for the article's contents. Clearly define the topic of the article Briefly explain why the topic is important Define the problem you’re trying to solve Set tone Clearly define the topic of the article Briefly explain why the topic is important Define the problem you’re trying to solve Set tone Tip 2: How to Write Learning Objectives Define what the reader is going to learn after finishing the story. Clearly define the skills the reader will gain Don’t write what you aren’t delivering. Clearly define the skills the reader will gain Don’t write what you aren’t delivering. Example Example Tip 3: How to Write Prerequisites Define what knowledge or skills are required to understand the article. Identify the Required Knowledge or Skills Identify the Required Knowledge or Skills Example Example Tip 4: How to Write “Getting Started” The simplest trick is to divide the content into sub-topics and create a section for the same. Example Divide each section with a paragraph and code example for each of the sub-sections. Bonus: Add the output of the code as a screenshot or GIF if applicable. Bonus: Tip 5: How to Write “Final Thoughts/Conclusion” Summarize key points. Highlight the takeaways. Provide CTA (Call to Action) if applicable. Summarize key points. Highlight the takeaways. Provide CTA (Call to Action) if applicable. Tip 6: Github Sample This section can be optional, but if you add a GitHub sample, it enhances the article in many ways. It acts as a testament to the code examples above. Enhance learning with practical examples. Improve SEOs too. Most Devs are searching on Google to solve a problem, and a GitHub sample makes their life easier. It acts as a testament to the code examples above. Enhance learning with practical examples. Improve SEOs too. Most Devs are searching on Google to solve a problem, and a GitHub sample makes their life easier. Tip 7: Add Impressum An Impressum provides more information about the author; it adds professionalism and credibility to the story. Keep it short and crisp. Don’t add too many links. Don’t ask for claps as the Medium doesn't encourage it. Keep it short and crisp. Don’t add too many links. Don’t ask for claps as the Medium doesn't encourage it. Medium Impressum Example C# Programming🚀 Thank you for being a part of the C# community! Before you leave: Follow us: Youtube | X | LinkedIn | Dev.to Youtube X LinkedIn Dev.to Visit our other platforms: GitHub GitHub Conclusion The above template has proven to be highly successful for writing technical articles, engaging readers, and providing a standard structure to the stories Including a GitHub sample further solves the challenges a dev faces while looking for practical implementations of the code. The structure makes the content more memorable & actionable. More Cheatsheets Cheat Sheets — .Net Cheat Sheets — .Net

How to Unlock 50K Views on Medium With This Winning Article Template

Howdy Hackers! With summer over and vacation season ending, it's common to hit a writing slump. Don’t worry—we’ve got you covered. The HackerNoon team has prepared a range of writing templates to kickstart your creativity. We'll guide you through using them in this writer’s note. Let's dive in! Where Do You Find Templates, and What Are They All About? We’re glad you asked. The HackerNoon team has spent a ton of time making templates to make it as easy as possible to get you writing. The team is constantly brainstorming new ideas based on what our writers love to write about to bring you new and exciting templates every week. As writers, we know it can be challenging when all you have is a blank screen staring at you, and you can’t seem to find an idea despite having a burning urge to write. That’s why we made them! All of HackerNoon’s writing templates can be found right after you click the “Start Writing” button next to the “Start Draft” box. You can search for whatever templates you’d like and also see a pinned list of our favorites along with any ongoing contest templates. We have templates for AI, gaming, web development, listicles, and more! If you ever think we should have a template for a particular topic, let us know, and we’ll get working on it. Already a template pro? Take the following templates out for a spin and see if you can land a spot on the HackerNoon front page!
10 Programming Languages Beginners Should Try
AP Style Reporting
Keeping Yourself Safe in Cyberspace How Do I Use These Templates Effectively? We have a lot of templates, so it can be pretty daunting to figure out what’s what. Let’s take some of the guesswork out of using them with the following guidelines to keep in mind when writing. If it’s an interview-style template, keep all the questions just the way they are. They’re there to guide your answers!
Formatting templates guide you on how to write, so you should remove any headings or word count suggestions as you write. These are meant to be a mold in which you find your own words!
Some templates will have tags already put in for you; keep those and also add some of your own. We think the preexisting ones would be the best tags to showcase your piece with.
If you’re writing for a contest, keep any sponsor tags and mentions.
Ask your editors for help when needed! If you need some more inspiration regarding how to use these templates, check out some fabulous template pieces written by our writers across the whole spectrum of HackerNoon’s catalog: Machine Learning Made Simple: A Beginner's Guide to AI
Golang - How to Parse JSON Data in Go
PayPal Becomes First Major Fintech Company to Launch Dollar-Backed Stablecoin Templates Make It Easy To Join Our Monthly Writing Contests In case you didn’t know, HackerNoon runs sponsored writing contests every month where you can win cash prizes and more! To get you started and to get all the juices flowing, the team at HackerNoon offers templates for every contest so you can be on your way to winning cold, hard cash in no time! For a complete list of contests currently underway, check out our HackerNoon Writing Contests page or click the green box down below to get started in our current Bitcoin Writing Contest. The Bitcoin Writing Contest is still in full swing! Toss your hat in the ring for a chance at the $17,500 prize pool.
Click here to get started with our Bitcoin Writing Contest Template That’s it from us today, Hackers! See you in cyberspace! Howdy Hackers! With summer over and vacation season ending, it's common to hit a writing slump. Don’t worry—we’ve got you covered. The HackerNoon team has prepared a range of writing templates to kickstart your creativity. We'll guide you through using them in this writer’s note. Let's dive in! Where Do You Find Templates, and What Are They All About? We’re glad you asked. The HackerNoon team has spent a ton of time making templates to make it as easy as possible to get you writing. The team is constantly brainstorming new ideas based on what our writers love to write about to bring you new and exciting templates every week. As writers, we know it can be challenging when all you have is a blank screen staring at you, and you can’t seem to find an idea despite having a burning urge to write. That’s why we made them! All of HackerNoon’s writing templates can be found right after you click the “Start Writing” button next to the “Start Draft” box. You can search for whatever templates you’d like and also see a pinned list of our favorites along with any ongoing contest templates. We have templates for AI, gaming, web development, listicles, and more! If you ever think we should have a template for a particular topic, let us know, and we’ll get working on it. Already a template pro? Take the following templates out for a spin and see if you can land a spot on the HackerNoon front page! 10 Programming Languages Beginners Should Try AP Style Reporting Keeping Yourself Safe in Cyberspace Already a template pro? Take the following templates out for a spin and see if you can land a spot on the HackerNoon front page! Already a template pro? Take the following templates out for a spin and see if you can land a spot on the HackerNoon front page! 10 Programming Languages Beginners Should Try 10 Programming Languages Beginners Should Try AP Style Reporting AP Style Reporting Keeping Yourself Safe in Cyberspace Keeping Yourself Safe in Cyberspace How Do I Use These Templates Effectively? We have a lot of templates, so it can be pretty daunting to figure out what’s what. Let’s take some of the guesswork out of using them with the following guidelines to keep in mind when writing. a lot If it’s an interview-style template, keep all the questions just the way they are. They’re there to guide your answers! Formatting templates guide you on how to write, so you should remove any headings or word count suggestions as you write. These are meant to be a mold in which you find your own words! Some templates will have tags already put in for you; keep those and also add some of your own. We think the preexisting ones would be the best tags to showcase your piece with. If you’re writing for a contest, keep any sponsor tags and mentions. Ask your editors for help when needed! If it’s an interview-style template, keep all the questions just the way they are. They’re there to guide your answers! Formatting templates guide you on how to write, so you should remove any headings or word count suggestions as you write. These are meant to be a mold in which you find your own words! Some templates will have tags already put in for you; keep those and also add some of your own. We think the preexisting ones would be the best tags to showcase your piece with. If you’re writing for a contest, keep any sponsor tags and mentions. Ask your editors for help when needed! If you need some more inspiration regarding how to use these templates, check out some fabulous template pieces written by our writers across the whole spectrum of HackerNoon’s catalog: Machine Learning Made Simple: A Beginner's Guide to AI Golang - How to Parse JSON Data in Go PayPal Becomes First Major Fintech Company to Launch Dollar-Backed Stablecoin Machine Learning Made Simple: A Beginner's Guide to AI Machine Learning Made Simple: A Beginner's Guide to AI Golang - How to Parse JSON Data in Go Golang - How to Parse JSON Data in Go PayPal Becomes First Major Fintech Company to Launch Dollar-Backed Stablecoin PayPal Becomes First Major Fintech Company to Launch Dollar-Backed Stablecoin Templates Make It Easy To Join Our Monthly Writing Contests In case you didn’t know, HackerNoon runs sponsored writing contests every month where you can win cash prizes and more! To get you started and to get all the juices flowing, the team at HackerNoon offers templates for every contest so you can be on your way to winning cold, hard cash in no time! For a complete list of contests currently underway, check out our HackerNoon Writing Contests page or click the green box down below to get started in our current Bitcoin Writing Contest. HackerNoon Writing Contests The Bitcoin Writing Contest is still in full swing! Toss your hat in the ring for a chance at the $17,500 prize pool. Click here to get started with our Bitcoin Writing Contest Template The Bitcoin Writing Contest is still in full swing! Toss your hat in the ring for a chance at the $17,500 prize pool. Click here to get started with our Bitcoin Writing Contest Template here That’s it from us today, Hackers! See you in cyberspace!

Get Out of That Post-Summer Slump With a Template!

¡Uka Post-Verano Slump ukanx mä plantillampiw mistuñama!

Выйдзіце з гэтага паслялетняга спаду з дапамогай шаблона!

Izađite iz tog posljeljetnog pada uz predložak!

¡Sal de esa depresión posverano con una plantilla!

Päästä eroon kesän jälkeisestä lamasta mallin avulla!

テンプレートを使って夏後のスランプから抜け出しましょう!

Keluar dari Kemerosotan Selepas Musim Panas Dengan Templat!

Tšwa go Slump Yeo ya Ka Morago ga Selemo ka Thempleite!

¡Lloqsiy chay Caída Post-Veranomanta huk Plantillawan!

Kaga bax Dhiirrigelinta Xagaaga Kadib adigoo wata Template!

Şablon bilen tomusdan soňky çöketlikden çykyň!

使用模板摆脱夏季后的低迷！

Tracking my habits has become an integral part of my personal growth journey. It helps me build better habits and stick to them consistently. As a product creator, I love creating micro tools like Personal Finance Tracker to increase my productivity for life + work. In this post, I’ll walk you through a step-by-step tutorial on how I create a Notion tracker to track my daily habits. I’ll also provide a free Notion template (available on my personal website) so you can try it out and see how it works. 1. Plan out your daily habits First, think about what personal habits matter to you and what you would like to do consistently every day. Pro Tip: From my experience, I’ve learned that it’s optimal to focus on 5 to 7 habits each year. More than that can become overwhelming and difficult to maintain. Here are some habits to consider Morning routines: Wake up early, Meditate, Exercise, Healthy breakfast, Write, Go outdoor
Learning Habits: Read, Listen to podcasts, Learn a skill/course
Self-care habits: Journal, Skincare, Hydrate, Take breaks
Evening routines: Unplug from devices, Reflect on your day, Plan for tomorrow, Sleep early 2. Set up your Habit Tracker database Now that you have a list of habits you want to track, it’s time to create your habit tracker database in Notion. (1) Create a database Open Notion and create a new page. Within this page, type “/” and select the “Inline Database” option to create a new database.
Name your database, for example, “My Habit” or something similar. (2) Add a Date property Click on the “+” sign on the database table to add a new property.
Select “Date” as the property type. (3) Add properties for each habit you want to track Click on the “+” sign next to the Date column to add a new property.
Select “Checkbox” as the property type and rename the Checkbox column with the habit you want to track. Repeat this process for each habit. For example, if you have 6 habits, create 6 checkboxes, each labeled with a different habit.
Your database should now have columns for each habit you want to track, 3. Calculate your habit progress Next, you’ll need to create custom formulas in Notion to calculate the progress of your habits. Here’s how you can set this up: (1) On your Habit Tracker Database Click on the “+” sign next to the Habit column to add a new property.
Select “Formula” as the property type. We’ll create 3 columns with Formula properties. Make sure to name them accordingly: Total Checked
Progress Number
Progress Bar % Click on each of these Formula columns (Total Checked, Progress Number, Progress Bar %) to edit their formulas, (2.1) Customize Notion formula (Total Checked) toNumber(Wake 6am ☀️ ) + toNumber(Journal 📕 ) + toNumber(Exercise 💪 ) + toNumber(Read 15min 📚 ) + toNumber(Go outdoor 🌳 ) + toNumber(Sleep 11pm 😴 ) (2.2) Customize Notion formula (Progress Number) Consider the following example: If you have 6 habits, use the formula below. If you have 10 habits, simply change the number 6 to match your total number of habits. round((Total Checked / 6) * 100) (2.3) Customize Notion formula (Progress Bar %) Progress Number/100 (3) Test the Notion formula Click on each checkbox to see if your formulas are calculating correctly, (4) Format the “Progress Bar %” column Click on the “Progress Bar %” column.
Edit the property settings.
Set the number format to “Percent” and choose “Bar” under “Show as.” 4. Customize your habit tracker Before that, let’s start by adding your first habit record. Log your first habit record Name Column: Enter today’s day in this column (e.g., Sunday).
Date Column: Enter today’s date in this column (e.g., Jul 21, 2024).
Check Off Boxes: Mark the checkboxes for the habits you’ve completed for the day. Once you’ve built out the necessary columns in your database, you can enhance its visual appeal by changing the view. Add a Calendar View Click on the “+” sign next to the “Table” tab to add a new view. Select “Calendar” from the available view options.
Hover over the top right corner of your new Calendar view and click on the three dots icon (“…”).
Then, select “Properties” Customize your Calendar display in Properties Toggle on the “Eye” icon to display the properties you want.
You might want to show “Date,” “Habit 1,” “Habit 2,” “Habit 3,” “Habit 4…. and “Progress Bar %.”
Hide any properties you don’t want to display in the calendar view. 5. Create your habit reports Next, you can set up a separate view in a weekly format to better analyze and review your habit progress. Here’s how: Add a New Table View Next to the Calendar view tab, click on the “+” sign to add a new view.
Select “Table” from the view options. Configure the Grouping On the top right corner of your database, click on the three dots (…) to open the menu.
Select “Group.”
Choose “Date” as the property to group by.
Set the Date by grouping to “Week.” Here’s what it looks like after breaking down the table by Weekly view: Calculate the Average In your table view, hover next to the date’s toggle. You’ll see a “Count all” label, click on it.
Select “More Options” -> “Average” -> “Progress Bar %”
This will calculate the average progress for each week! Get The Notion Habit Tracker Template 🌟🌟 You can download the template on my personal website: https://whizzoe.com/#tools Tracking my habits has become an integral part of my personal growth journey. It helps me build better habits and stick to them consistently. As a product creator, I love creating micro tools like Personal Finance Tracker to increase my productivity for life + work. Personal Finance Tracker Personal Finance Tracker In this post, I’ll walk you through a step-by-step tutorial on how I create a Notion tracker to track my daily habits. I’ll also provide a free Notion template ( available on my personal website ) so you can try it out and see how it works. free Notion template available on my personal website 1. Plan out your daily habits First, think about what personal habits matter to you and what you would like to do consistently every day. Pro Tip: From my experience, I’ve learned that it’s optimal to focus on 5 to 7 habits each year. More than that can become overwhelming and difficult to maintain. Pro Tip: Here are some habits to consider Here are some habits to consider Morning routines: Wake up early, Meditate, Exercise, Healthy breakfast, Write, Go outdoor Learning Habits: Read, Listen to podcasts, Learn a skill/course Self-care habits: Journal, Skincare, Hydrate, Take breaks Evening routines: Unplug from devices, Reflect on your day, Plan for tomorrow, Sleep early Morning routines: Wake up early, Meditate, Exercise, Healthy breakfast, Write, Go outdoor Morning routines: Learning Habits: Read, Listen to podcasts, Learn a skill/course Learning Habits: Self-care habits: Journal, Skincare, Hydrate, Take breaks Self-care habits: Evening routines: Unplug from devices, Reflect on your day, Plan for tomorrow, Sleep early Evening routines: 2. Set up your Habit Tracker database Now that you have a list of habits you want to track, it’s time to create your habit tracker database in Notion. (1) Create a database Open Notion and create a new page. Within this page, type “/” and select the “Inline Database” option to create a new database. Name your database, for example, “My Habit” or something similar. Open Notion and create a new page . Within this page, type “/” and select the “Inline Database” option to create a new database. new page “/” “Inline Database” Name your database, for example, “My Habit” or something similar. “My Habit” (2) Add a Date property Date property Click on the “+” sign on the database table to add a new property. Select “Date” as the property type. Click on the “+” sign on the database table to add a new property. “+” sign Select “Date” as the property type. “Date” (3) Add properties for each habit you want to track (3) Add properties for each habit you want to track Click on the “+” sign next to the Date column to add a new property. Select “Checkbox” as the property type and rename the Checkbox column with the habit you want to track. Click on the “+” sign next to the Date column to add a new property. “+” Date column Date column Select “Checkbox” as the property type and rename the Checkbox column with the habit you want to track. “Checkbox” Repeat this process for each habit. For example, if you have 6 habits, create 6 checkboxes, each labeled with a different habit. Your database should now have columns for each habit you want to track, Repeat this process for each habit. For example, if you have 6 habits, create 6 checkboxes, each labeled with a different habit. each labeled Your database should now have columns for each habit you want to track, 3. Calculate your habit progress Next, you’ll need to create custom formulas in Notion to calculate the progress of your habits. Here’s how you can set this up: (1) On your Habit Tracker Database (1) On your Habit Tracker Database Click on the “+” sign next to the Habit column to add a new property. Select “Formula” as the property type. Click on the “+” sign next to the Habit column to add a new property. “+” sign Select “Formula” as the property type. “Formula” We’ll create 3 columns with Formula properties. Make sure to name them accordingly: We’ll create 3 columns with Formula properties. Make sure to name them accordingly: Total Checked Progress Number Progress Bar % Total Checked Progress Number Progress Bar % Click on each of these Formula columns (Total Checked, Progress Number, Progress Bar %) to edit their formulas, Click on each of these Formula columns (Total Checked, Progress Number, Progress Bar %) to edit their formulas, Formula columns edit (2.1) Customize Notion formula (Total Checked) toNumber(Wake 6am ☀️ ) + toNumber(Journal 📕 ) + toNumber(Exercise 💪 ) + toNumber(Read 15min 📚 ) + toNumber(Go outdoor 🌳 ) + toNumber(Sleep 11pm 😴 ) toNumber(Wake 6am ☀️ ) + toNumber(Journal 📕 ) + toNumber(Exercise 💪 ) + toNumber(Read 15min 📚 ) + toNumber(Go outdoor 🌳 ) + toNumber(Sleep 11pm 😴 ) (2.2) Customize Notion formula (Progress Number) Consider the following example: If you have 6 habits, use the formula below. If you have 10 habits, simply change the number 6 to match your total number of habits. simply change the number 6 round((Total Checked / 6) * 100) round((Total Checked / 6) * 100) (2.3) Customize Notion formula (Progress Bar %) Progress Number/100 Progress Number/100 (3) Test the Notion formula Click on each checkbox to see if your formulas are calculating correctly, Click on each checkbox to see if your formulas are calculating correctly, checkbox (4) Format the “Progress Bar %” column (4) Format the “Progress Bar %” column Click on the “Progress Bar %” column. Edit the property settings. Set the number format to “Percent” and choose “Bar” under “Show as.” Click on the “Progress Bar %” column. “Progress Bar %” Edit the property settings. Edit the property Set the number format to “Percent” and choose “Bar” under “Show as.” “Percent” “Bar” 4. Customize your habit tracker Before that, let’s start by adding your first habit record. Log your first habit record Log your first habit record Name Column: Enter today’s day in this column (e.g., Sunday). Date Column: Enter today’s date in this column (e.g., Jul 21, 2024). Check Off Boxes: Mark the checkboxes for the habits you’ve completed for the day. Name Column: Enter today’s day in this column (e.g., Sunday). Name Column: Date Column: Enter today’s date in this column (e.g., Jul 21, 2024). Date Column: Check Off Boxes: Mark the checkboxes for the habits you’ve completed for the day. Check Off Boxes: Once you’ve built out the necessary columns in your database, you can enhance its visual appeal by changing the view. Add a Calendar View Add a Calendar View Click on the “+” sign next to the “Table” tab to add a new view. Select “Calendar” from the available view options. Hover over the top right corner of your new Calendar view and click on the three dots icon (“…”). Then, select “Properties” Click on the “+” sign next to the “Table” tab to add a new view. Select “Calendar” from the available view options. “+” “Table” tab Hover over the top right corner of your new Calendar view and click on the three dots icon (“…”) . three dots icon (“…”) Then, select “Properties” “Properties” Customize your Calendar display in Properties Customize your Calendar display in Properties Toggle on the “Eye” icon to display the properties you want. You might want to show “Date,” “Habit 1,” “Habit 2,” “Habit 3,” “Habit 4…. and “Progress Bar %.” Hide any properties you don’t want to display in the calendar view. Toggle on the “Eye” icon to display the properties you want. “Eye” icon You might want to show “Date,” “Habit 1,” “Habit 2,” “Habit 3,” “Habit 4…. and “Progress Bar %.” Hide any properties you don’t want to display in the calendar view. 5. Create your habit reports Next, you can set up a separate view in a weekly format to better analyze and review your habit progress. Here’s how: Add a New Table View Add a New Table View Next to the Calendar view tab, click on the “+” sign to add a new view. Select “Table” from the view options. Next to the Calendar view tab, click on the “+” sign to add a new view. Select “Table” from the view options. “Table” Configure the Grouping On the top right corner of your database, click on the three dots (…) to open the menu. Select “Group.” Choose “Date” as the property to group by. Set the Date by grouping to “Week.” On the top right corner of your database, click on the three dots (…) to open the menu. three dots (…) Select “Group.” “Group.” Choose “Date” as the property to group by. “Date” Set the Date by grouping to “Week.” “Week.” Here’s what it looks like after breaking down the table by Weekly view: Here’s what it looks like after breaking down the table by Weekly view: Calculate the Average In your table view, hover next to the date’s toggle. You’ll see a “Count all” label, click on it. Select “More Options” -> “Average” -> “Progress Bar %” This will calculate the average progress for each week! In your table view, hover next to the date’s toggle. You’ll see a “Count all” label, click on it. “Count all” Select “More Options” -> “Average” -> “Progress Bar %” “More Options” “Average” “Progress Bar %” This will calculate the average progress for each week! Get The Notion Habit Tracker Template 🌟🌟 Get The Notion Habit Tracker Template Get The Notion Habit Tracker Template You can download the template on my personal website: https://whizzoe.com/#tools https://whizzoe.com/#tools

How I Built a Habit Tracker in Notion (with Template)

Authors:
(1) Christopher D. Clack, Centre for Blockchain Technologies, Department of Computer Science, University College London;
(2) Vikram A. Bakshi, Investment Bank CTO Office, Barclays;
(3) Lee Braine, Investment Bank CTO Office, Barclays. Table of Links Abstract and 1 Introduction 2 Foundations and 2.1 Terminology — “smart contracts” 2.2 Automation 2.3 Enforceability 2.4 The semantics of contracts 3 Smart Contract Templates 3.1 Templates and Parameters 3.2 The design landscape for Smart Contract Templates 4 Summary and Further Work and References 4 Summary and Further Work 4.1 Summary This paper has considered four foundational topics regarding smart contracts: terminology, automation, enforceability, and semantics. We defined a smart contract as an automatable and enforceable agreement. We viewed legal contracts within a simple semantic framework based on two key aspects: one being the operational aspects concerning automation of the contract and another being the non-operational aspects. We then described templates for legally-enforceable smart contracts as electronic representations of legal documents containing prose and parameters (with each parameter comprising an identifier, a type and an optional value). Agreements are then fully-instantiated templates, including customised legal prose and parameters. By selecting the appropriate smart contract code, this approach results in the creation of Ricardian Contract triples. We then explored the design landscape: increasing the sophistication of parameters to complex higher-order types and business logic that could be admissible in court and potentially replace the corresponding legal prose. We also explored increasing the use of common standardised code through greater sharing, evolving from different codebases across banks to broader adoption of common utility functions to common business logic. Additionally, longterm research was outlined which could lead to source languages which can be automatically translated into both code and legal prose; even longer term research could result in formal languages which themselves are admissible in court. 4.2 Further Work A benefit of looking to the future is that it helps to identify a potential roadmap for applying research within industry. Smart Contract Templates have already demonstrated a way to link standardised agreements to standardised code and so, in the near term, it may be possible to utilise them with existing infrastructure. In the longer term, they could be utilised on shared ledgers. We are continuing to collaborate broadly, including via trade associations such as ISDA and FIA, on exploring formats for the storage and transmission of smart legal agreements comprising legal prose and parameters. Of particular interest are the corresponding essential requirements and design options, including the possibility of extending the scope of existing data standards such as FpML (Financial products Markup Language) for derivatives. There are many open questions for the future. We have explored some of these questions in this paper, but we will end with one more: is it possible to provide straight-through-processing of financial contracts, with full confidence in the fidelity of the automated computer code to the entire semantics of the contract? This, of course, will require substantial work and collaboration by the financial services industry, standards bodies, academia[8], and lawyers. References [1] Axoni. AxCore, 2016. https://axoni.com/. [2] L. Braine. Barclays’ Smart Contract Templates, 2016. Barclays London Accelerator, https://vimeo.com/168844103/ and http://www.ibtimes.co.uk/barclays-smart-contracttemplates-heralds-first-ever-public-demo-r3s-corda-platform-1555329/. [3] R.G. Brown, J. Carlyle, I. Grigg, and M. Hearn. Corda: An introduction, 2016. At https://static1.squarespace.com/static/55f73743e4b051cfcc0b02cf/t/ 57bda2fdebbd1acc9c0309b2/1472045822585/corda-introductory-whitepaper-final.pdf. Also see https://www.corda.net/. [4] CommonAccord, 2016. http://www.commonaccord.org/. [5] Digital Asset. The Digital Asset Platform - Non-technical White Paper, 2016. Available at https://digitalasset.com/press/digital-asset-releases-non-technical-white-paper.html. [6] Ethereum, 2016. https://www.ethereum.org/. [7] I. Grigg. The ricardian contract. In Proceedings of the First IEEE International Workshop on Electronic Contracting, pages 25–31. IEEE, 2004. http://iang.org/papers/ricardian_ contract.html. [8] I. Grigg. On the intersection of ricardian and smart contracts, 2015. http://iang.org/ papers/intersection_ricardian_smart.html. [9] I. Grigg. The sum of all chains — let’s converge!, 2015. Presentation for Coinscrum and Proof of Work. http://financialcryptography.com/mt/archives/001556.html. [10] T. Hvitved. Contract Formalisation and Modular Implementation of Domain-Specific Languages. PhD thesis, Department of Computer Science, University of Copenhagen, 2012. [11] Hyperledger Fabric, 2016. https://github.com/hyperledger/fabric/. [12] Monax Industries. Dual Integration, 2016. https://monax.io/explainers/dual_ integration/. [13] Legalese, 2016. http://www.legalese.com/. [14] M. Mainelli and A. Milne. The impact and potential of blockchain on the securities transaction lifecycle, 2016. SWIFT Institute Working Paper No. 2015-007. [15] R3 and Norton Rose Fulbright. Can smart contracts be legally binding contracts?, 2016. http://www.nortonrosefulbright.com/knowledge/publications/144559/can-smartcontracts-be-legally-binding-contracts/. [16] J. Stark. Making sense of blockchain smart contracts, 2016. http://www.coindesk.com/ making-sense-smart-contracts/. [17] T. Swanson. Great chain of numbers: A guide to smart contracts, smart property and trustless asset management, 2014. https://s3-us-west2.amazonaws.com/chainbook/Great+Chain+of+Numbers+A+Guide+to+Smart+Contr acts%2C+Smart+Property+and+Trustless+Asset+Management+-+Tim+Swanson.pdf. [18] T. Swanson. Consensus-as-a-service: a brief report on the emergence of permissioned, distributed ledger systems, 2015. http://www.ofnumbers.com/wp-content/uploads/2015/ 04/Permissioned-distributed-ledgers.pdf. [19] N. Szabo. Formalizing and securing relationships on public networks. First mind, 2(9), 1997. This paper is available on arxiv under CC BY 4.0 DEED license. [8] For example, further investigation of contract semantics and the specification language CLACK is being pursued at University College London. Authors: (1) Christopher D. Clack, Centre for Blockchain Technologies, Department of Computer Science, University College London; (2) Vikram A. Bakshi, Investment Bank CTO Office, Barclays; (3) Lee Braine, Investment Bank CTO Office, Barclays. Authors: Authors: (1) Christopher D. Clack, Centre for Blockchain Technologies, Department of Computer Science, University College London; (2) Vikram A. Bakshi, Investment Bank CTO Office, Barclays; (3) Lee Braine, Investment Bank CTO Office, Barclays. Table of Links Abstract and 1 Introduction Abstract and 1 Introduction 2 Foundations and 2.1 Terminology — “smart contracts” 2 Foundations and 2.1 Terminology — “smart contracts” 2.2 Automation 2.2 Automation 2.3 Enforceability 2.3 Enforceability 2.4 The semantics of contracts 2.4 The semantics of contracts 3 Smart Contract Templates 3 Smart Contract Templates 3.1 Templates and Parameters 3.1 Templates and Parameters 3.2 The design landscape for Smart Contract Templates 3.2 The design landscape for Smart Contract Templates 4 Summary and Further Work and References 4 Summary and Further Work and References 4 Summary and Further Work 4.1 Summary This paper has considered four foundational topics regarding smart contracts: terminology, automation, enforceability, and semantics. We defined a smart contract as an automatable and enforceable agreement. We viewed legal contracts within a simple semantic framework based on two key aspects: one being the operational aspects concerning automation of the contract and another being the non-operational aspects. We then described templates for legally-enforceable smart contracts as electronic representations of legal documents containing prose and parameters (with each parameter comprising an identifier, a type and an optional value). Agreements are then fully-instantiated templates, including customised legal prose and parameters. By selecting the appropriate smart contract code, this approach results in the creation of Ricardian Contract triples. We then explored the design landscape: increasing the sophistication of parameters to complex higher-order types and business logic that could be admissible in court and potentially replace the corresponding legal prose. We also explored increasing the use of common standardised code through greater sharing, evolving from different codebases across banks to broader adoption of common utility functions to common business logic. Additionally, longterm research was outlined which could lead to source languages which can be automatically translated into both code and legal prose; even longer term research could result in formal languages which themselves are admissible in court. 4.2 Further Work A benefit of looking to the future is that it helps to identify a potential roadmap for applying research within industry. Smart Contract Templates have already demonstrated a way to link standardised agreements to standardised code and so, in the near term, it may be possible to utilise them with existing infrastructure. In the longer term, they could be utilised on shared ledgers. We are continuing to collaborate broadly, including via trade associations such as ISDA and FIA, on exploring formats for the storage and transmission of smart legal agreements comprising legal prose and parameters. Of particular interest are the corresponding essential requirements and design options, including the possibility of extending the scope of existing data standards such as FpML (Financial products Markup Language) for derivatives. There are many open questions for the future. We have explored some of these questions in this paper, but we will end with one more: is it possible to provide straight-through-processing of financial contracts, with full confidence in the fidelity of the automated computer code to the entire semantics of the contract? This, of course, will require substantial work and collaboration by the financial services industry, standards bodies, academia[8], and lawyers. References [1] Axoni. AxCore, 2016. https://axoni.com/. [2] L. Braine. Barclays’ Smart Contract Templates, 2016. Barclays London Accelerator, https://vimeo.com/168844103/ and http://www.ibtimes.co.uk/barclays-smart-contracttemplates-heralds-first-ever-public-demo-r3s-corda-platform-1555329/. [3] R.G. Brown, J. Carlyle, I. Grigg, and M. Hearn. Corda: An introduction, 2016. At https://static1.squarespace.com/static/55f73743e4b051cfcc0b02cf/t/ 57bda2fdebbd1acc9c0309b2/1472045822585/corda-introductory-whitepaper-final.pdf. Also see https://www.corda.net/. [4] CommonAccord, 2016. http://www.commonaccord.org/. [5] Digital Asset. The Digital Asset Platform - Non-technical White Paper, 2016. Available at https://digitalasset.com/press/digital-asset-releases-non-technical-white-paper.html. [6] Ethereum, 2016. https://www.ethereum.org/. [7] I. Grigg. The ricardian contract. In Proceedings of the First IEEE International Workshop on Electronic Contracting, pages 25–31. IEEE, 2004. http://iang.org/papers/ricardian_ contract.html. [8] I. Grigg. On the intersection of ricardian and smart contracts, 2015. http://iang.org/ papers/intersection_ricardian_smart.html. [9] I. Grigg. The sum of all chains — let’s converge!, 2015. Presentation for Coinscrum and Proof of Work. http://financialcryptography.com/mt/archives/001556.html. [10] T. Hvitved. Contract Formalisation and Modular Implementation of Domain-Specific Languages. PhD thesis, Department of Computer Science, University of Copenhagen, 2012. [11] Hyperledger Fabric, 2016. https://github.com/hyperledger/fabric/. [12] Monax Industries. Dual Integration, 2016. https://monax.io/explainers/dual_ integration/. [13] Legalese, 2016. http://www.legalese.com/. [14] M. Mainelli and A. Milne. The impact and potential of blockchain on the securities transaction lifecycle, 2016. SWIFT Institute Working Paper No. 2015-007. [15] R3 and Norton Rose Fulbright. Can smart contracts be legally binding contracts?, 2016. http://www.nortonrosefulbright.com/knowledge/publications/144559/can-smartcontracts-be-legally-binding-contracts/. [16] J. Stark. Making sense of blockchain smart contracts, 2016. http://www.coindesk.com/ making-sense-smart-contracts/. [17] T. Swanson. Great chain of numbers: A guide to smart contracts, smart property and trustless asset management, 2014. https://s3-us-west2.amazonaws.com/chainbook/Great+Chain+of+Numbers+A+Guide+to+Smart+Contr acts%2C+Smart+Property+and+Trustless+Asset+Management+-+Tim+Swanson.pdf. [18] T. Swanson. Consensus-as-a-service: a brief report on the emergence of permissioned, distributed ledger systems, 2015. http://www.ofnumbers.com/wp-content/uploads/2015/ 04/Permissioned-distributed-ledgers.pdf. [19] N. Szabo. Formalizing and securing relationships on public networks. First mind, 2(9), 1997. This paper is available on arxiv under CC BY 4.0 DEED license. This paper is available on arxiv under CC BY 4.0 DEED license. available on arxiv [8] For example, further investigation of contract semantics and the specification language CLACK is being pursued at University College London.

Smart Contract Templates:
Foundations, Design and Research - Summary, Further Work & References

Smart Contract Templates:
Foundations, Design and Research - Smart Contract Designs

Authors:
(1) Christopher D. Clack, Centre for Blockchain Technologies, Department of Computer Science, University College London;
(2) Vikram A. Bakshi, Investment Bank CTO Office, Barclays;
(3) Lee Braine, Investment Bank CTO Office, Barclays. Table of Links Abstract and 1 Introduction 2 Foundations and 2.1 Terminology — “smart contracts” 2.2 Automation 2.3 Enforceability 2.4 The semantics of contracts 3 Smart Contract Templates 3.1 Templates and Parameters 3.2 The design landscape for Smart Contract Templates 4 Summary and Further Work and References 3.1 Templates and Parameters A template is an electronic representation of a legal document as issued by a standards body — for example, by the International Swaps and Derivatives Association (ISDA). As illustrated in Figure 2, a template contains both legal prose and parameters, where each parameter has an identity (a unique name), a type, and may (but need not) have a value. An agreement is a fully-instantiated template (including any customised legal prose and parameters). The customisation of legal prose and parameters at this stage is commonplace and results from negotiation between the counterparties. The legal prose of an agreement will be derived from that of the template, but need not be identical, and similarly the parameters of the agreement will be derived from the template but need not be identical. It is also common for agreements to comprise multiple documents such as framework agreements (e.g. a Master Agreement) with various annexes (e.g. a Schedule) and credit support documentation (e.g. a Credit Support Annex). Deriving the set of code parameters may be complicated by three factors: It is common for parameters to be embedded in the legal prose — such parameters would initially be identified visually, aided by a graphical user interface.


Some of the values identified as “parameters” in the agreement (or template) may not have an operational impact and therefore would not be passed to the smart contract code.


It is possible for a parameter to be defined (given a name) in one document, given a value in a second document, and used (e.g. in business logic) in a third document. Although parameters need not have values in a template, they must have values in a signed agreement. All of an agreement’s parameter values are a critical part of the contract as they directly reflect the business relationship between parties and those that are code parameters influence the automated operation of the contract. This paper is available on arxiv under CC BY 4.0 DEED license. Authors: (1) Christopher D. Clack, Centre for Blockchain Technologies, Department of Computer Science, University College London; (2) Vikram A. Bakshi, Investment Bank CTO Office, Barclays; (3) Lee Braine, Investment Bank CTO Office, Barclays. Authors: Authors: (1) Christopher D. Clack, Centre for Blockchain Technologies, Department of Computer Science, University College London; (2) Vikram A. Bakshi, Investment Bank CTO Office, Barclays; (3) Lee Braine, Investment Bank CTO Office, Barclays. Table of Links Abstract and 1 Introduction Abstract and 1 Introduction 2 Foundations and 2.1 Terminology — “smart contracts” 2 Foundations and 2.1 Terminology — “smart contracts” 2.2 Automation 2.2 Automation 2.3 Enforceability 2.3 Enforceability 2.4 The semantics of contracts 2.4 The semantics of contracts 3 Smart Contract Templates 3 Smart Contract Templates 3.1 Templates and Parameters 3.1 Templates and Parameters 3.2 The design landscape for Smart Contract Templates 3.2 The design landscape for Smart Contract Templates 4 Summary and Further Work and References 4 Summary and Further Work and References 3.1 Templates and Parameters A template is an electronic representation of a legal document as issued by a standards body — for example, by the International Swaps and Derivatives Association (ISDA). As illustrated in Figure 2, a template contains both legal prose and parameters, where each parameter has an identity (a unique name), a type, and may (but need not) have a value. An agreement is a fully-instantiated template (including any customised legal prose and parameters). The customisation of legal prose and parameters at this stage is commonplace and results from negotiation between the counterparties. The legal prose of an agreement will be derived from that of the template, but need not be identical, and similarly the parameters of the agreement will be derived from the template but need not be identical. It is also common for agreements to comprise multiple documents such as framework agreements (e.g. a Master Agreement) with various annexes (e.g. a Schedule) and credit support documentation (e.g. a Credit Support Annex). Deriving the set of code parameters may be complicated by three factors: It is common for parameters to be embedded in the legal prose — such parameters would initially be identified visually, aided by a graphical user interface. Some of the values identified as “parameters” in the agreement (or template) may not have an operational impact and therefore would not be passed to the smart contract code. It is possible for a parameter to be defined (given a name) in one document, given a value in a second document, and used (e.g. in business logic) in a third document. It is common for parameters to be embedded in the legal prose — such parameters would initially be identified visually, aided by a graphical user interface. It is common for parameters to be embedded in the legal prose — such parameters would initially be identified visually, aided by a graphical user interface. Some of the values identified as “parameters” in the agreement (or template) may not have an operational impact and therefore would not be passed to the smart contract code. Some of the values identified as “parameters” in the agreement (or template) may not have an operational impact and therefore would not be passed to the smart contract code. It is possible for a parameter to be defined (given a name) in one document, given a value in a second document, and used (e.g. in business logic) in a third document. It is possible for a parameter to be defined (given a name) in one document, given a value in a second document, and used (e.g. in business logic) in a third document. Although parameters need not have values in a template, they must have values in a signed agreement. All of an agreement’s parameter values are a critical part of the contract as they directly reflect the business relationship between parties and those that are code parameters influence the automated operation of the contract. This paper is available on arxiv under CC BY 4.0 DEED license. This paper is available on arxiv under CC BY 4.0 DEED license. available on arxiv

Smart Contract Templates:
Foundations, Design and Research - Templates and Parameters

Stories, News & Mentions about PETPLATE

Petplate’s Stories on HackerNoon