You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thinking about how we're likely to use announcements, I'd expect any PR making visible changes to include a new announcement file explaining the changes, so the users are informed.
We need some way of making that announcement stay visible for 3 days after the PR is merged, rather than the date that the code is committed. Obviously I could push a commit to update the date before merging the changes, but something automatic would be nice.
The text was updated successfully, but these errors were encountered:
More fully-featured version of the announcements function introduced last week.
This sets up an announcements page that lists the 20 most recent announcements at datacore.app/announcements. Announcements can now link excerpts on the index page to the announcements page for more details. An amended version of the new voyage calc announcement demos this.
Announcements on the index page can now be dismissed. Otherwise announcements will expire 7 days after the post date. Resolves#299.
I have yet to figure out an easy way to handle #300. Any suggestions would be welcome!
This separates the announcements functions to their own page and component. Also fixes the unintentional "feature" of creating pages for each individual announcement.
More fully-featured version of the announcements function introduced last week.
This sets up an announcements page that lists the 20 most recent announcements at datacore.app/announcements. Announcements can now link excerpts on the index page to the announcements page for more details. An amended version of the new voyage calc announcement demos this.
Announcements on the index page can now be dismissed. Otherwise announcements will expire 7 days after the post date. Resolves#299.
I have yet to figure out an easy way to handle #300. Any suggestions would be welcome!
This separates the announcements functions to their own page and component. Also fixes the unintentional "feature" of creating pages for each individual announcement.
Thinking about how we're likely to use announcements, I'd expect any PR making visible changes to include a new announcement file explaining the changes, so the users are informed.
We need some way of making that announcement stay visible for 3 days after the PR is merged, rather than the date that the code is committed. Obviously I could push a commit to update the date before merging the changes, but something automatic would be nice.
The text was updated successfully, but these errors were encountered: