-
-
Notifications
You must be signed in to change notification settings - Fork 315
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Techstack-beta] Blog: Newsletters #1249
Comments
Tagging @garbas here as he is more up to date about the future of the newsletter |
The order is fixed. Blog is going to be improved, but we need to start somewhere. At this moment it is good enough. Since maintaining content between two sites is getting really hard. Newsletter is the first topic I'm going to work on after we do the switch. |
I don't quite understand the current status of the newsletters, they seem to be working fine. If I could find a team of people to update the newsletter, could we immediately start resurrecting it before the "website refactoring"? |
What is holding against having everything in a central spot except to different pages spread all over? Apart from that, tagging @garbas , since he is responsible for bringing the newsletters back to life |
Since this changes the presentation and content of the section, I will add this:
But like mentioned in #1248, for now it would be safer to not change the form of the content, and have the newsletters in their discrete listing page.
Here, I'm not sure making new pages for the content of a now archived community project is a good idea. I'm not even sure I was in favour of repeating in full the content of what we should have been linked to the weekly website...
Though, adding new pages here shouldn't be taken lightly, as the URLs need to live on in the future.
Though, with that said:
The newsletters are not in proper chronological order.
See
#06 - NixOS Weekly - Published on Mon Jun 29 2020
being shown at the top, and#07 - NixOS Weekly - Published on Wed Aug 05 2020
at the bottom...The text was updated successfully, but these errors were encountered: