I'm wondering if we should keep this.
We've got the wonderful anchorthemes.com, so I feel like we don't really need this repo.
There's also the fact that nothing has been done here for a year now, so everything is outdated.

I'm not saying we should remove this immediately (although I'd be fine with that), but maybe a huge deprecated warning in the readme with a link to Anchor Themes in there (because it's already in the readme, but way to far down, imo).

Let me know what you think.

Issue

This repo has existed for quite a while now. It holds the original themes that were created at the very of Anchor CMS. However, we have a couple issues with this repo.

1. Managing 8 themes in 1 repo is a bad way of working. Pull requests, branching and issue creating looks really confusing. Especially if it's to do with just 1 theme
2. If you want to download or fork a theme for your own use you take the other 7 with you. This also occurs on the Anchor Themes site as it directly links to the GitHub download zip
3. Author credit! This probably the most important thing in my eyes. At the minute nobody is taking credit for the themes and I'd like to change that

Proposed Solution

Here is what I plan to do with this repo:

• Duplicate the repo 7 times over onto my own account (this excludes Default theme as it is currently being worked on within anchor-cms). Yes this does look like I'm trying to take credit for these themes, but I'm definitely not. I'll be making sure the README.md has an explanation to why it's on my account
• Rename each duplicated repo to the name of each theme
• Clean out the other repos so that there are 7 repos with a single theme in it
• Clear out the themes from this repo and update the README.md stating what has happened and where the themes have gone
• Contact all the theme authors as best as I can and explain the situation and provide a simple method to change ownership of the repo over

Thoughts? This shouldn't take long to do and will hopefully make it easier for authors to claim back their theme, if not at least it means that we can manage the themes easier.

@Bertdasquirt when you get a chance could you rename this repo to "anchor-themes" so it falls inline with the others please :)

Use git remote set-url origin [email protected]:anchorcms/anchor-themes.git to update your repo.

Added a preview of the theme

I've spent some times going through all the themes for anchor and updating them for version 0.9 (development version).

My branch is https://github.com/daviddarnes/anchor-themes/tree/0.9

If the boilerplate theme has been deleted do we just use 'default' instead?

If I use ul and li in my posts, the text is black and not styled. The css-file is to confusing for me, sorry.
I don´t know if that is meant to be, but I don´t think so.