anchor-cms
anchor-cms copied to clipboard
anchorcms
The Big 1.0
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:
- [ ] Plugins
- [x] Idiot-proof installer. Let's crush all these bugs that keep popping up.
- [x] Simplified UI (more on that).
- [x] Drag-to-add media (drag a file to the screen, add/detect type).
- [x] Simplified/smarter themes
- [ ] Full documentation.
- [ ] A simple API
- [ ] Mobile view/iOS app (but probably not the latter)
- [x] Markdown WYSIWG (bold/italic/etc. toolbar, very simple)
- [x] Namespacing table names.
Bugs:
- [x] Search functionality
- [x]
contentdirectory - [x]
mod_rewriteissues.
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:
- Remove as many decisions as possible
- Remove as many obstacles as possible
- Be as simple and usable as possible
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.
Awesome, so psyched for this. Must discuss my side project with you (which you're aware of).
Couple of suggestions:
- Tick box dropdown custom field types
- Ability to add custom fields with the functions file, stops a theme with special fields being database dependant
Looks like a solid roadmap so far. +1 on David's suggestion for theme specific custom fields. Perhaps the option to add a short description when creating custom fields, to be shown on hover when creating posts?
Tags possibly? So you can mark several posts several attributions. Unlike categories which is more a filing method.
Mobile view FTW. That would be awesome. Simple API would be great too!
Auto-update would be cool, but only if we could modify/override some core functionality from within the theme. Until then, I wouldn't like my site to "auto-break" every time a new version comes out.
The ability to export the CSS/JS inclusions to external files rather than having it inline.
@chrisgwynne export? Do you mean when uploading a js or css file you'd like to be able to reference it for a post rather than using a style block? Those fields are for minor additions and special cases, not entire re-theme of a site.
@daviddarnes like on VisualIdiot.com for example, each post has its own styling and has it's CSS/JS saved as such "/posts/mailappapp/style.css" or "/posts/anypost/style.css". Having inline CSS/JS is always bad.
@idiot uses custom templates all together so instead of article.php there will be a template like article-mailappapp.php, correct me if im wrong.
If the theme is made as expected the styles will be placed in an internal style sheet and the same for the js, which isn't inline. And yes if you wanted to do completely custom pages you could create a custom article file.
Custom HTML would be a nice addition as well, the default editor isn't that handy when you try adding custom UI elements like the ones in twitter bootstrap.
Laurens
I already knew that (markdown accepts xhtml) but sometimes it can be annoying that markdown auto processes your html as plain text.
Laurens
@dechuck what would you use this for? essentially every post/page can be whatever you want them to be.
@borisovg This can already be done using post description
@Simonclavey so post description is what will show in the list? And if it's blank then the whole thing is shown? If so that's cool. :-)
@borisovg Post description shows the snippet of text you add to the desc field on the post page. By default if there is no desc nothing is shown but it would be easy to add a quick if else statement to display whole post if desc is null. (this is going a little off-topic)
@Simonclavey So the desciption is only shown in list view, not on the post itself, which is not the same as the "more" tag. To get the desired result I would have to copy paste a part of the post into description, which means duplicating content. :-(
@borisovg O okay so you just want to show a snippet from the actual article. Just make a new function that returns the first ~140 characters of all your articles on the post loop page.
In 0.9 we change the article_description function so that if you enter a short desc it will use that if not it will get a snippet from the content, I think this was discussed on the forums too.
The advantage I will see is for client. Exemple, you have to different type of post, one is blog post and the other projet. The two different type of post have different custom field. They also have different permalink.
@dechuck I think extra post types would be better suited as a plugin. Good suggestion though.
I'd like to have most things (like the custom post types with custom URLs) as a plugin so it keeps the base CMS small and fast as it is.
The more you add everything to the core the more it becomes overweighted like most other CMS with lots of built-n stuff.
What do all others think? Built-in or rather plugin? In my opinion plugins are the better solution and for sure a good documentation of all plugins like anchor Themes - could also host it on Github or at least creat a respo so everyone can fork and add their own plugins.
I think this is a great idea, as having a modular CMS will make it easy for everyone to tailor it to their own needs.
You don't care about SEO? Fine, you don't have to! You want a grea homepage slider? There's a plugin for that!
The above situation would be ideal for most cases, and I agree with @Kevin.
Let's keep it simple, stupidly simple.
Sent from beneath my fingertips
On 20 Apr 2013, at 09:41, Kevin [email protected] wrote:
I'd like to have most things (like the custom post types with custom URLs) as a plugin so it keeps the base CMS small and fast as it is.
The more you add everything to the core the more it becomes overweighted like most other CMS with lots of built-n stuff.
What do all others think? Built-in or rather plugin? In my opinion plugins are the better solution and for sure a good documentation of all plugins like anchor Themes - could also host it on Github or at least creat a respo so everyone can fork and add their own plugins.
— Reply to this email directly or view it on GitHub.