Open ghost opened 11 years ago
Have you all seen Ghost yet? The Markdown editor on it is really nice. As it's open source I propose we rip it out of there and use a variant/fork for Anchor. I was playing with it earlier so here is it ripped out (without the preview) and ready to be edited.
Forgive me for the silly question but how does it work? Is it mainly the styling you're looking at? We've also looked at the medium editor too, but we could merge the two?
Codemirror just a syntax highlighter. They have the textarea set to use custom Markdown styles and they're using a js markdown renderer to render the preview.
There is another good syntax highlighter called Ace that Github uses in gist snippets but I was thinking it might be easier to just modify Ghost's.
Having played with the Ghost demo a few weeks ago, I've had it in my mind to create a fork with similar functionality to their live side-by-side markdown editor preview, but haven't had the time to explore it. Think it would make a very nice addition.
How about trackback/pingback integration?
Please, add tags support. I very want add several tags into single post
Some better SEO out of the box would be good. Anchor doesn't play so well with search engines :/
What specifically would you want to be added that would count as better SEO?
Two requests:
With SEO I think adding the ability to add all custom meta tags per post, so you can specify the graph values per post. I think that would be very helpful.
On a system level, what I liked about wordpress was choosing which template I could use. So on this post use this template, a little like @idiot has done with his site. That would be very useful.
Also if you need a mirror for plugins I am happy to help.
I'd love to see a follow function similar to the one used on WP.
Bump... @idiot I'll be happy to do the documentation. But I don't know what methods I should be documenting...
@TheBrenny If you check out http://anchorcms.com/docs/function-reference/posts you will notice that there is some documentation. Also if you check out the php
files in anchor/functions
you will find the rest of the API which a large amount of might also need documenting :) Thanks for volunteering, writing docs is time consuming for a changing project :(
@CraigChilds94 @idiot Any news on this 1.0 release? If you need financial resources to get this done let me know.
@TheBrenny @daviddarnes just a side question regarding comments, is markdown available for comments just yet or no? I couldn't find anything relating to the topic on the docs and it seems like a very viable feature to have.
@redrails I'm not sure, seems like a logical feature addition. Maybe add it to FeatHub?
Mobile view/iOS app (but probably not the latter)
IB Times reports that smartphone market is dominated by the Android OS. Probably best to get rid of the "iOS app" part. After all, it's going to be available for phones anyway. :stuck_out_tongue_closed_eyes:
@idiot Anchor CMS is the by far most awesome CMS out there I have ever used. But when you say that the computer has to do more work, does that mean you will be relying on more ugly javascript?
Got comments/questions/suggestions? Leave them in the comments and we'll add them in when we can.
So, we just hit 0.8, and we're getting ever-closer to the big launch. Only seems fair that we have a big checklist for 1.0 (as well as the other issues here).
Features:
Bugs:
content
directorymod_rewrite
issues.UI:
By 1.0, it'd be nice to have a consistent, super-minimal UI framework across both Anchor and Roar. The goal is to:
That means we're going to need the computer and server to do a bit more thinking, but this could be the best-designed CMS out there.