Compare commits

..

2 commits

Author SHA1 Message Date
629fff0363 "State of DTI: 2024" copy edits 2024-09-20 13:53:18 -07:00
b4d56be69b Add RSS feed 2024-09-20 13:35:31 -07:00
4 changed files with 48 additions and 9 deletions

3
_config.yml Normal file
View file

@ -0,0 +1,3 @@
title: OpenNeo Blog
url: https://blog.openneo.net/
description: For Dress to Impress, and uhh maybe other things later!

View file

@ -3,8 +3,14 @@
<head> <head>
<meta name="viewport" content="width=device-width, initial-scale=1" /> <meta name="viewport" content="width=device-width, initial-scale=1" />
<meta charset="utf-8" /> <meta charset="utf-8" />
<title>{{ page.title }} - OpenNeo Blog</title> <title>{{ page.title }} - {{ site.title }}</title>
<link rel="stylesheet" href="/assets/css/main.css" /> <link rel="stylesheet" href="/assets/css/main.css" />
<link
rel="alternate"
type="application/rss+xml"
href="{{ site.url }}/feed.xml"
title="{{ site.title }}"
/>
</head> </head>
<body> <body>
<header> <header>
@ -12,7 +18,7 @@
<img src="/assets/images/logo.png" /> <img src="/assets/images/logo.png" />
</a> </a>
<h1> <h1>
<a href="/">OpenNeo Blog</a> <a href="/">{{ site.title }}</a>
</h1> </h1>
<p role="doc-subtitle"> <p role="doc-subtitle">
For For

View file

@ -21,9 +21,10 @@ After 15 years of DTI (what the heck??!), and 15 years of changing
circumstances, **our primary focus is keeping DTI around for the long-haul**. circumstances, **our primary focus is keeping DTI around for the long-haul**.
And, I'll be real with ya, the choices I made in earlier times weren't really And, I'll be real with ya, the choices I made in earlier times weren't really
designed for decades of operation 😅 designed for decades of operation 😅 (DTI I think is now officially older than I
was when I started it? 🤐)
- When I started DTI, I wasn't really uhh, good at working with others? So I - Back at the start, I wasn't really uhh, good at working with others? So I
never put together a formal team, and I built a codebase that was difficult to never put together a formal team, and I built a codebase that was difficult to
share. share.
- And when we rebooted as Impress 2020, I borrowed the technology and design - And when we rebooted as Impress 2020, I borrowed the technology and design
@ -55,7 +56,7 @@ beyond just DTI 😭 So, I didn't discover issues quickly; and when I _did_, it
would sometimes take a few hours, or even days, to become available. would sometimes take a few hours, or even days, to become available.
When I was younger, it was easier to be on-call all the time… now, we have to be When I was younger, it was easier to be on-call all the time… now, we have to be
smarter about it. So, we're being smarter! smarter about it. So, hey—we're being smarter!
- **🔔 Alerts:** We've set up automated notifications to tell us when the site - **🔔 Alerts:** We've set up automated notifications to tell us when the site
goes down, or when a new kind of crash appears. _(If you're curious, we're goes down, or when a new kind of crash appears. _(If you're curious, we're
@ -78,7 +79,7 @@ Right now, Dress to Impress is a weird combination of apps… I copy-pasted some
of Impress 2020's best UI changes over, but it all still used the Impress 2020 of Impress 2020's best UI changes over, but it all still used the Impress 2020
_server_ code, even when you're on `impress.openneo.net`. _server_ code, even when you're on `impress.openneo.net`.
This both doubled the danger of downtime (if _either_ app goes down, that's a This both doubled the danger of downtime (if _either_ server goes down, that's a
problem for both!), and added networking complexities that are hard to track problem for both!), and added networking complexities that are hard to track
down (hello, "error loading species/color"!) down (hello, "error loading species/color"!)
@ -132,7 +133,7 @@ and monitoring,** which just weren't happening on their own.
too**—though we didn't end up building all of the integrated elements we were too**—though we didn't end up building all of the integrated elements we were
hoping for. _(We were planning an "Add all to cart" NC Mall link, as a time hoping for. _(We were planning an "Add all to cart" NC Mall link, as a time
saver for folks, and a way to help TNT know that DTI helped you out.)_ Ah, saver for folks, and a way to help TNT know that DTI helped you out.)_ Ah,
well—that's product work! I hope it's been helpful in this form, too! well—that's product work! I hope it's been helpful in this form, too 💝
**Right now, we're on a bit of a pause,** as TNT's dev team focuses on the Void **Right now, we're on a bit of a pause,** as TNT's dev team focuses on the Void
Within plot and the other things on their plate. But our next plan is to look Within plot and the other things on their plate. But our next plan is to look
@ -154,5 +155,5 @@ promise I'm giving the community the best I know how to give, always 💜)_
### As always, thank you! ### As always, thank you!
I hope this plan makes sense, as just one guy doing her best to keep the site I hope this plan makes sense, as just one guy doing her best to keep the site
online! And I hope this work can help set the stage for more people to join in online! And I hope this work can help set the stage for more people to join our
the coming years, too. team of maintainers in the coming years, too.

29
feed.xml Normal file
View file

@ -0,0 +1,29 @@
---
layout: null
---
<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>{{ site.title }}</title>
<link>{{ site.url }}</link>
<atom:link href="{{ page.url | prepend: site.url }}" rel="self" type="application/rss+xml" />
<description>{{ site.description }}</description>
<lastBuildDate>{{ site.time | date_to_rfc822 }}</lastBuildDate>
{% for post in site.posts %}
<item>
<title>{{ post.title }}</title>
<link>
{{ post.url | prepend: site.url }}
</link>
<description>
{{ post.content | escape }}
</description>
<pubDate>{{ post.date | date_to_rfc822 }}</pubDate>
<guid>
{{ post.url | prepend: site.url }}
</guid>
</item>
{% endfor %}
</channel>
</rss>