# Backdating News Articles

**URL:** <https://revolt.metaeducation.com/forum/t/backdating-news-articles/496>\
**Category:** Community\
**Created:** [January 27, 2018, 3:19am UTC](https://revolt.metaeducation.com/forum/t/backdating-news-articles/496 "2018-01-27T03:19:52Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![hostilefork](https://revolt.metaeducation.com/forum/user_avatar/revolt.metaeducation.com/hostilefork/32/421_2.png) [@hostilefork](https://revolt.metaeducation.com/forum/u/hostilefork)\
**Post date:** [January 27, 2018, 3:19am UTC](https://revolt.metaeducation.com/forum/t/backdating-news-articles/496/1 "2018-01-27T03:19:52Z")

</div>

The prototype [rebol.org](http://reboldocs.brianotto.com/) page features boxes for recent news.

Rather than launch with a completely empty news feed, I'm wondering if we want to take old commit announcements of features and put them in the chronology.

We've already done a "filling in" of the [bugs in rebol-issues](https://github.com/rebol/rebol-issues/issues?page=68&q=is%3Aissue+is%3Aopen), keeping them accurate with the CureCode dates. It helps people get an understanding that there has been a history, as opposed to Rebol just popping out of nowhere. We could combine the announcements from a GitHub commit with some stuff from a Trello to get an announcement. For instance the [HIJACK commit](https://github.com/metaeducation/ren-c/commit/fc7c536c66a87369b1384ebd02d80c3cb0468817) from Jun 19, 2016 would suggest a news announcement at that time would be fitting.

Perhaps even adding some even older curated news items out of the old AltME announcements of notable historical things, to put the dates in context:

[http://rebol.info/altme/105/announce](http://rebol.info/altme/105/announce)

...or important announcements from Carl's blog (if there's any issue with quoting the content in its entirety, a summary with a fair-use quote would do). Things like the open sourcing announcement...just to fill out a timeline.

It might be easiest if those news items were just posts here on the forum in a category...which were transcluded to look like a news feed. That would facilitate discussion as well as make edits easier, and fold in with a database that has to be running and backed up anyway.

---

<div class="post-metadata">

**Author:** ![BrianOtto](https://revolt.metaeducation.com/forum/letter_avatar_proxy/v4/letter/b/e480ec/32.png) [@BrianOtto](https://revolt.metaeducation.com/forum/u/BrianOtto)\
**Post date:** [January 27, 2018, 6:56am UTC](https://revolt.metaeducation.com/forum/t/backdating-news-articles/496/2 "2018-01-27T06:56:08Z")

</div>

> [@hostilefork](#):
>
> Rather than launch with a completely empty news feed, I'm wondering if we want to take old commit announcements of features and put them in the chronology.

Yea, I completely agree. We should definitely put some back dated new articles up when it launches.

> [@hostilefork](#):
>
> It might be easiest if those news items were just posts here on the forum in a category...which were transcluded to look like a news feed. That would facilitate discussion as well as make edits easier, and fold in with a database that has to be running and backed up anyway.

I like this idea. Not sure how possible it is to do with Github pages, but I can look into it once we get the rest of the design nailed down.

---

<div class="post-metadata">

**Author:** ![gchiu](https://revolt.metaeducation.com/forum/user_avatar/revolt.metaeducation.com/gchiu/32/22_2.png) [@gchiu](https://revolt.metaeducation.com/forum/u/gchiu)\
**Post date:** [January 27, 2018, 8:21pm UTC](https://revolt.metaeducation.com/forum/t/backdating-news-articles/496/3 "2018-01-27T20:21:10Z")

</div>

Luckily there's a [change timestamp](https://meta.discourse.org/t/update-changing-timestamp-through-ui/29464) feature just for this purpose.

It's used for migrating stuff from another site, or, to have secret articles that are released at a certain past date.
