Re: [attic] New website url - https://attic-backup.org/
- Petros Moisiadis
- 2014-03-11 @ 10:03
On 03/10/2014 10:55 PM, Jonas Borgström wrote:
> The project homepage has now moved to a prettier and easier to remember
> url (The old urls redirect to the new location):
> So far the content is exactly the same but this change gives us more
> control over the website. How do you guys think the website could be
> For example:
> - News section: Information about new releases and change logs
> - Guides/tutorials: "How do I use Attic to do X..."
> - FAQ
> / Jonas
Some things that in my opinion would improve the first impression that
newcomers get about attic.
1) Have a "Key Features" section in first view with a link to a full
list of features inside the user guide. The full list could consist of
features such as ability to prune older backups, repository integrity
checking (although that may be better stated as a key feature), facts
about the code (few lines of code, unit test coverage, etc.), using
already available and widely deployed ssh infrastructure (no need for
special services or daemons), self-contained repositories (no need for
databases), documentation, etc.
2) A "Comparison with similar tools" section with an as much unbiased
comparison as it can be of features and functions shared among similar
tools and features that are unique to attic or that attic may lack. Some
metrics about speed and size of backups, like those that Dan Christensen
had presented lately, could have their place there too.
3) The news section, besides release announcements, could also feature
from time to time some preview notes about features that are planned to
come next and maybe invite community to test pre-releases or contribute
by discussing in the mailing-list on how they would expect things to
work. Some projects use blog posts for that kind of stuff, but maybe a
blog it is too much for now.
4) For when attic becomes more popular: Have a section about people and
organizations using attic, as well as references in other places (tech
sites, conferences, etc.).
5) Have a changelog / history / timeline section.