Tags: zhangaz1/archivy
Tags
v1.0 Archivy began as a small personal project in August 2020. However, since then it's grown into much more, with the help of contributors and the many discussions and ideas we've brainstormed on the discord server (https://discord.gg/uQsqyxB). There have been major improvements in the design, structure and general features of the project like for example: - development of a CLI interface and deployment of archivy on pip, docker, the aur and nixpkgs - redesign to make archivy actually look good :slight_smile: - introduction of a powerful markdown editor / rendering - a complete documentation website - auth system - focus on extensibility: Python API / Web API / plugin system and much more! I'm extremely excited for the current state of Archivy and it's future even beyond v1, outlined in the roadmap archivy#74 (comment). Thank you to all the people who have shaped this project, and as always, don't hesitate to ask any questions or talk to us if you'd like to share your opinion or ideas!
v0.11.0 Major changes: - Complete restructure of user interface and design (see https://uzpg.me/assets/images/archivy.mov) - including a new bookmarklet - removal of date in file names (won't break with old format) BUGFIX: non-markdown files showed up as directories in tree, now fixed.
v0.10.1 Implements [hooks](https://archivy.github.io/reference/hooks/) for better plugin flexibility.
v0.10.0 - Pandoc dependency has been phased out and is replaced by the `markdown-it` js editor for better speed, security and coherence. - Frontend editor now supports LaTeX / footnotes also. - The watcher has been removed and is replaced with several changes: - Two new commands have been added for formatting / unformatting of content, which the watcher used to do automatically: `format` and `unformat`. - The `archivy index` command auto-indexes your data to ES and whenever you make an edit through the web editor it is synced directly.
PreviousNext