.ns { max-width: 28rem; margin: 0 auto; padding: 3rem 1.5rem; color: #1f2937; text-align: center; } .ns-logo { width: 48px; height: 48px; margin: 0 auto 1rem; } .ns h1 { margin: 0 0 0.25rem; font-size: 2rem; font-weight: 800; letter-spacing: -0.02em; text-transform: uppercase; } .ns-tagline { margin: 0 0 1.5rem; font-size: 0.9rem; color: #6b7280; } .ns-image { width: 100%; border-radius: 0.5rem; margin-bottom: 1.5rem; } .ns-notice { background: #f3f4f6; border-radius: 0.5rem; padding: 1rem 1.25rem; font-size: 0.9rem; line-height: 1.6; color: #374151; } .ns-notice strong { color: #1f2937; } /* The two blocks the server injects further down the page (the site-nav twin and, on the archive, the date index) are <noscript> too, so they are only ever seen HERE — and they used to arrive unstyled: browser defaults, which on the dark background this same block sets meant black text and navy links on #111827. They share the panel's palette from here rather than carrying their own inline styles, so there is one place where the no-JS page is dressed. The font is the property's, inherited from body like everything else. */ #site-nav, #archive-index { color: #1f2937; } #site-nav { max-width: 48rem; margin: 2rem auto 3rem; padding: 1.5rem 1.5rem 0; border-top: 1px solid #e5e7eb; font-size: 0.9rem; } .site-nav-links { display: flex; flex-wrap: wrap; gap: 0.25rem 1.5rem; padding-top: 0.75rem; } /* Both blocks are collapsed (see _archive_index_html): the summary is the only line a no-JS reader sees until they ask for more. */ #site-nav summary, #archive-index summary { cursor: pointer; font-weight: 600; color: #374151; } #site-nav a, #archive-index a { color: #2563eb; } #archive-index { max-width: 48rem; margin: 2rem auto 0; padding: 0 1.5rem; } #archive-index summary { font-size: 1.05rem; font-weight: 700; } #archive-index > p { margin: 0 0 1.5rem; font-size: 0.9rem; line-height: 1.6; color: #6b7280; } #archive-index h3 { margin: 1.25rem 0 0.5rem; font-size: 0.8rem; font-weight: 600; text-transform: uppercase; letter-spacing: 0.04em; color: #6b7280; } /* Hundreds of dates in one column is the whole reason this page read as debris. Wrapped rows (not CSS columns) keep a month glanceable AND keep newest-first reading left-to-right: columns would flow the list down each column, so a reader scanning across a row would get the 7th, the 5th, the 3rd. */ #archive-index ul { display: flex; flex-wrap: wrap; gap: 0.25rem 1.5rem; margin: 0; padding: 0; list-style: none; font-size: 0.9rem; line-height: 1.9; } #archive-index li { flex: 0 0 auto; min-width: 6rem; } @media (prefers-color-scheme: dark) { body { background: #111827; } .ns { color: #f3f4f6; } .ns-tagline { color: #9ca3af; } .ns-notice { background: #1f2937; color: #d1d5db; } .ns-notice strong { color: #f9fafb; } #site-nav, #archive-index { color: #f3f4f6; } #site-nav { border-top-color: #374151; } #site-nav a, #archive-index a { color: #93c5fd; } #site-nav summary, #archive-index summary { color: #e5e7eb; } #archive-index > p, #archive-index h3 { color: #9ca3af; } }

Found along the way

One prompt a day. Go out, find it, take the photo, keep it in your journal.

JavaScript is required to play.
Please enable it in your browser settings and reload the page. A site index is below if you want to look around.

Site links

Home Your journal Updates