2025
2024
- Dec 31 - End of 2024
- Oct 30 - Winding down usage of Twitter
- Oct 21 - Copyright and Co-Authors
- Jan 8 - 2023 Year-end Update
2023
2022
- Dec 31 - A year of transition
- Sep 30 - RSS is back!
- Jan 25 - Legacy author migration
- Jan 25 - Announcing engrXiv's new host
- Jan 24 - Website access issues possible
- Jan 17 - Notice of submission downtime
2021
2020
- Dec 29 - Done with 2020
- Jun 8 - Participating in the Strike for Black Lives
- May 27 - 1000 eprints
- Feb 15 - Our Future and Financial Sustainability
2019
- Dec 31 - 2019 State of the Server
- Oct 26 - Update to Engineering Archive's legal status and announcing the Membership Circle
- Apr 11 - Switching to pre-moderation and a new withdraw feature
2018
- Dec 31 - A great 2018 at engrXiv
- Jul 23 - Engineering Archive now integrated with Hypothesis
- Mar 19 - Progress of engrXiv posts
2017
- Dec 29 - 2017 has been quite a year
- Sep 22 - engrXiv and OSF for Meetings for your conference proceedings
- Jul 27 - One year anniversary of engrXiv
- Jul 17 - Citation benefits of preprinting with engrXiv
- Jul 14 - Big news on DOIs and the engrXiv URL
- Jul 12 - An open letter to ASME
- Apr 17 - Now indexed by Google Scholar
- Feb 22 - Template now available
- Feb 3 - Recommended citation formatting now available
2016
- Dec 7 - engrXiv is here to make engineering knowledge more open and accessible
- Sep 26 - Opportunities to contribute
- Sep 1 - Author on overleaf, submit to engrXiv
- Aug 16 - Working across disciplines
- Aug 4 - Why call it engrXiv?
- Aug 2 - What can you do with a new engrXiv post?
- Jul 28 - How to check a journal's eprint policy
- Jul 27 - Announcing engrXiv, the eprint server for engineering