-
Notifications
You must be signed in to change notification settings - Fork 391
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
Change "magazines" section to "newsletters" and update resources at library page #2044
Conversation
✅ Deploy Preview for barolo-time-757cf9 ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
If the moneromoons ccs proposal is not merged to funding , he will not produce the newsletter anymore , something to consider (and is currently away for the next 4 weeks) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Better add a brief description of each newsletter otherwise it's quite ugly and differs from the style of the rest of the page.
Opinions about my comment above? |
@erciccione It can be great but what should we write? |
@HardenedSteel i don't know as i'm not very familiar with any of them, but even just author and structure (published every N) would be enough. |
84eceb7
to
1e92fe8
Compare
ping @HardenedSteel |
we can merge as is OR add/test html scripting with this pull request ive made here HardenedSteel#2 |
I'd merge as it is, since this is already reviewed and i would open a dedicated pr after if you want to propose that patch. That said, personally i don't see the need to increase complexity and add a new file. It's only two entries, but even if it was more, the current structure could still be used without problems. |
and it will close #1976