Skip to content

Instantly share code, notes, and snippets.

View jdanyow's full-sized avatar
💭
Confirming my whereabouts

Jeremy Danyow jdanyow

💭
Confirming my whereabouts
View GitHub Profile
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>GistRun</title>
<link rel="stylesheet" href="https://static.docs.com/ui/latest/site/en-us/styles/site-ltr.css">
<style>
/* hide the table header by default */
.matrix-group-row:first-child {
display: none;
@jdanyow
jdanyow / index.html
Last active November 17, 2020 23:17
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>GistRun</title>
<style>
.face-fallback {
display: none;
}
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>GistRun</title>
</head>
<body>
<h1>Hello world!</h1>
<pre><code id="output"></code></pre>
@jdanyow
jdanyow / index.html
Last active September 16, 2020 16:15
product directory
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>GistRun</title>
<style>
.directory {
columns: 3;
}
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>GistRun</title>
<link rel="stylesheet" href="https://static.docs.com/ui/latest/site/en-us/styles/site-ltr.css">
<style>
.example {
display: inline-block !important;
border: 1px solid blue;
@jdanyow
jdanyow / index.html
Created September 1, 2020 19:01
svg clip-path
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>GistRun</title>
<style>
* {
margin: 0;
padding: 0;
}
@jdanyow
jdanyow / index.css
Created July 3, 2020 03:09 — forked from LeaVerou/dabblet.css
Playing with background-attachment
/**
* Playing with background-attachment
*/
pre {
max-height: 150px;
border: 1px solid silver;
overflow: auto;
background: url('http://placekitten.com/200/200');
color: white;
@jdanyow
jdanyow / templating.md
Last active September 10, 2021 10:13
Templating - Docs Composition Service

Templating - Docs Composition Service

Writing down some thoughts about server-side templating solutions for Docs.

Today

Today Docs.Rendering & docs-render follow roughly the same process. This is by design, for the initial release of docs-render we're prioritizing backwards compatibility, template reuse, time to market.

The heavy parts of handling a request look roughly like this:

foo

bar


author: SusanneWindfeldPedersen title: "FAQ" description: "" ms.custom: na ms.date: 04/01/2020 ms.reviewer: na ms.suite: na ms.tgt_pltfrm: na ms.topic: article