Compare commits

..

No commits in common. "629fff0363d52b928a7cbba970c7869424ab34be" and "032b1ce57dba0f04c81c7a4c202b7e1cc169de98" have entirely different histories.

4 changed files with 9 additions and 48 deletions

View file

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

View file

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

View file

@ -21,10 +21,9 @@ 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**.
And, I'll be real with ya, the choices I made in earlier times weren't really
designed for decades of operation 😅 (DTI I think is now officially older than I
was when I started it? 🤐)
designed for decades of operation 😅
- Back at the start, I wasn't really uhh, good at working with others? So I
- When I started DTI, 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
share.
- And when we rebooted as Impress 2020, I borrowed the technology and design
@ -56,7 +55,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.
When I was younger, it was easier to be on-call all the time… now, we have to be
smarter about it. So, hey—we're being smarter!
smarter about it. So, we're being smarter!
- **🔔 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
@ -79,7 +78,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
_server_ code, even when you're on `impress.openneo.net`.
This both doubled the danger of downtime (if _either_ server goes down, that's a
This both doubled the danger of downtime (if _either_ app goes down, that's a
problem for both!), and added networking complexities that are hard to track
down (hello, "error loading species/color"!)
@ -133,7 +132,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
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,
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
Within plot and the other things on their plate. But our next plan is to look
@ -155,5 +154,5 @@ promise I'm giving the community the best I know how to give, always 💜)_
### As always, thank you!
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 our
team of maintainers in the coming years, too.
online! And I hope this work can help set the stage for more people to join in
the coming years, too.

View file

@ -1,29 +0,0 @@
---
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>