Richard Feldman (Mar 23 2024 at 15:37): Richard Feldman (Mar 23 2024 at 15:37):so I want to write an article about the new ! syntax, and I'm not sure where to put it.
the obvious default is to add a new section of roc-lang.org like /blog or /news or /articles or something, but I don't want to do that.
Richard Feldman (Mar 23 2024 at 15:40):the reasons I don't want to do that are:
Richard Feldman (Mar 23 2024 at 15:42):I was thinking about just posting something on rtfeldman.com and letting it get shared around. On the one hand, if I'm the one writing the post, then it seems reasonable to put it on a personal website. On the other hand, if I'm talking about a group effort, it feels a little weird to me to be posting it on a personal website instead of in a more group-like place (e.g. roc-lang.org)
Richard Feldman (Mar 23 2024 at 15:43):another option would be to put it on GitHub somehow under the roc-lang organization (like maybe a Gist would be fine - kind of informal, but the content would be the interesting part anyway)
Richard Feldman (Mar 23 2024 at 15:44):in a future where we have a forum up and running, that would be obvious choice, although I don't think that should be a blocker for this post
Richard Feldman (Mar 23 2024 at 15:44):I'm curious what others think!
Agus Zubiaga (Mar 23 2024 at 15:57):I agree on downsides of /blog. The personal blog seems like the best option for now. I don’t think it’s that weird to talk about a group effort there.
Isaac Van Doren (Mar 23 2024 at 16:09):What if it was put at at roc-lang.org/task-chaining-syntax (or whatever else the article will be called)? If it is on a personal blog it won't be organically discover-able from roc-lang.org at all, so it could just be on the official website without being in a specific section. That would avoid the downsides of a blog but it could still be on the main site. That being said, putting it on a personal site seems perfectly reasonable to me too.
Anton (Mar 23 2024 at 16:37):Yeah, if it's an explainer it could go on the website like the abilities page, but personal site is good for me too.
Richard Feldman (Mar 23 2024 at 16:40):yeah the trouble with making it dsicoverable on roc-lang.org is that then we probably need to put it in the nav bar :sweat_smile:
Anton (Mar 23 2024 at 16:42):It could go under "language reference" or a new subcategory in https://www.roc-lang.org/docs
Norbert Hajagos (Mar 23 2024 at 17:03):Agree with Anton. If the article is about teaching ! then it should be under the docs. I personally think /docs/abilities would also be better than /abilities, but that isn't so important.
If it is about the journey of moving towards ! and the challenges implementing it, maybe design decisions, a news or articles path would be best. Where would you put (waaay) later the announcement of a v1.0.0 for example? You could give a heads-up on the /articles path about communication happening mainly on Zulip and that this is a place for writing about major topics.
Brendan Hansknecht (Mar 23 2024 at 17:18):Could make a design doc section under docs
Brendan Hansknecht (Mar 23 2024 at 17:24):Or some form of temporary articles under docs
Brendan Hansknecht (Mar 23 2024 at 17:30):Don't think it has to be on the main page with a link, but I definitely think it should go on the website
Luke Boswell (Mar 23 2024 at 18:46):On a similar note, yesterday I was thinking all the Str explainer content that is currently in the Str builtin docs could be moved into another language reference article/guide. This would slim down the docs and they could link to the article.
Luke Boswell (Mar 23 2024 at 18:47):My concern is that the content isn't as discoverable nested within the Str sub-module.
Brendan Hansknecht (Mar 23 2024 at 18:48):Yeah, some general performance docs would be great as well
Richard Feldman (Mar 23 2024 at 19:21):yeah this is not about docs, it's more like announcements
Richard Feldman (Mar 23 2024 at 19:55):I think it's worth having a separate discussion about docs structure
Richard Feldman (Mar 23 2024 at 19:55):e.g. what should be in the builtin docs vs elsewhere
Hristo (Mar 23 2024 at 19:57):I like Anton's Language Reference suggestion, as it feels most natural for such kind of information to be expected to be found there (e.g., a new page referenced from a new bullet-point in that section). That's actually the first thing that came to mind, when I saw the question.
Alternatively, such kind of content would probably fit well in the Tutorial (a new sub-section in the tutorial, e.g., under "Advanced Concepts").
Richard Feldman (Mar 23 2024 at 20:05):this wouldn't go in a language reference
Richard Feldman (Mar 23 2024 at 20:06):it's more of an announcement
Hristo (Mar 23 2024 at 20:12):Okay, understood!
Also, my apologies, you did say that in the comment just above, and I did read it but I thought an announcement and some docs (which are arguably, more "permanent" in terms of how easy are to get referenced and found) weren't necessarily mutually exclusive.
It seems, one couldn't get away without a quasi "News"/"Blog" section for something like this (despite the discussed disadvantages, which I definitely agree with).
Eli Dowling (Mar 30 2024 at 12:24):Thinking about the news/blog indicating abandonment, I know it's work, but if we are concerned about not having content a little dot point summary of the monthly meetups with some links would probably be enough to indicate work is happening.
I actually think it might be good for people to have a single place to check in on the progress that's being made.
Ocaml for has ocaml weekly which I regularly check to see what's happening and keep up with stuff.
Obviously it's a thing someone should have to do, but still might be worth considering.
I watch the recordings most months and would be happy to put together a little dot point summary while I do so.
Richard Feldman (Mar 30 2024 at 13:47):that would be awesome! :smiley:
Richard Feldman (Mar 30 2024 at 13:48):I think doing that as an unofficial community thing (which we could link to from roc-lang.org/community) would work great!
Last updated: Jun 16 2026 at 16:19 UTC