Wishlist

Hello !

Here is what functionnalities are missing to Chyrp : - Allow the upload of Media while writing content - Remove Twig at least for front-end themes ;) - Allow to select the default admin page after login for example

That's all I have right now, but I remember I had other ideas, but can't remember...

I'd like to either remove Twig, or create a PHP-template engine to work alongside it. Themes declare with template engine they use in the YAML file.

I'd be happy to help develop this.

Also, I'd like more documentation of Theme, Module & Feather development. Currently the only thing to learn from is hacking at code from the things already there.

Wishlist:

• All feathers should have an optional title. (some of them are missing them)
• Photo feather image linking to optional url. (Tumblr style)
• Multiphoto feather. (Gallery)
• Multiaudio feather. (Mixtape)
• Event / Calendar (google/ical)
• Posting twitter updates in Chyrp. (other microblog services too)
• Posting chyrp posts on twitter. (other microblog services too)

edit: * File Download (with count)

Guys, I'm impressed with all these great ideas and suggestions. Frankly speaking, some I do enjoyed and some should be thought precisely before taking further action.

Replacing Twig with plain PHP has shown to be highly desired by many. Matt-SD has already started to work on something that makes the switch possible, I'm quite curious to see how it comes out in the end. If it turns to work as expected, I am willing to accept all the good improvements.

As for Feathers, one thing that I'm concerned with for now is having a unique way to handle post URLs. Since Feathers with no slug show a "{ feathertype.post.id }" kind of URL which isn't the best way to be.

@ParadisoShlee, Photo feather already has a ... how they say at Tumblr, "click-through" link, check out the More Options under Photo and right there is Source field. That does it.

I'm thinking about the optional titles for all feathers, seems good to be there, and so on.

Can't go through all the points you guys mentioned for now.

Ah, and one more thing, Posting Twitter to Chyrp and viceversa should be a functionality added by a module which doesn't need to be shipped with the core.

That is for now. Great suggestions again, keep 'em coming.

If you've got some spare time, join us on IRC channel, #chyrp at FreeNode and have a stay there or say something.

Hooks, filters, and documentation thereof, really strenuously.

I have been working with WordPress (wp) for a while now: I dig it, and have found that some of the best modification opportunities come through the hook/filter system. I cannot claim to understand how that system works, but hooks to inject functionality (especially in the template context) and filters to modify default markup are incredibly powerful and flexible.

The problem with hooks/filters is that they seem to be add-ons as a way to get around default behaviours. I have written more code undoing what wp does than i have written doing what i want it to do. If you limit the default behaviours in the first place hooks/filters become a way to augment default behaviours, or add un-imagined functionality.

Being able to call an arbitrarily registered hook in a template context imparts great power. Being able to filter a default function's output imparts great adaptability.

Almost all sites need the same basic things: a crazy index/home page with content from every-damn-where, largely static, client-created content pages, some searchable/taggable.catergorized news/blog posts, and other stuff. Hooks hanld ethe every-damn-where content, filters handle the bulk of the rest.

I see it this way: Chyrp-devs want to build 'their' system: a CMS that meets their needs. That is not a slight, it's what most devs are building: something that does what they want, the way they want. Unfortunately, no one wants the same things.

Avoid overbuilding. Find a core, focus on that and tell people about it. Handle the bits no one wants to fiddle with and you'll build a winning system.

Create rules and stick to them. It's great that i can pass arguments to WP as an array or a string, but if you mandate an array AND STICK TO IT I'll give you an array every time and love it. That would be wonderful.

Imagine that Chyrp devs write an excerpt function that returns 10 full sentences of a given page/post: a developer somewhere is going to need 12, or 6, or 64 characters including spaces to please her/his client.

Do you want to get into that fight, or would you prefer to put the onus on the demanding developer? Give him/her a way to specify the word/character count or over-ride the default behaviour altogether and you have a happy developer.

Implementing a robust hook/filter system would allow internal Chyrp developers to focus on a core set of functionality/functions that no one else wants to write, and create more easily-modified template tags (regardless of engine) that power-users can tweak, and would create in-roads for outside developers to create custom functionality, or 'feathers'.

People do not write their own CMSes because the basics are hard, tedious, or both. If a CMS wants to be useful, it will focus on the business end: user registration and privileges, posting, archiving, tagging/categorizing, page creation, and template application. Focusing on those processes and their security is a great foundation for any CMS (in my highly biased opinion).

I work in a shop that builds a bunch of sites for a bunch of clients. They all need a blog, a few static pages, and other stuff. The complication lies in the 'other stuff' and the particular blog needs. The CMS that handles the needs and has a system that lets me build (and share, as possible) the other stuff is going to win, and most shops will pay a bit for it.

I'll admit it, and i doubt that I am alone: i want something that handles users, user privileges and template allocation for me: i want a system that allows me to build to client specific demands in that framework. If I need to drop in Facebook API access, that's my problem. Twitter? see above, re: my problem.

This is pretty much a post aimed at the Chyrp devs: figure out what you want to build and build it. Maybe I am describing a thing you do not want to build. My bad. But, when you try to please everyone you please no one, and roll out M$ Word.

I may be wrong on all counts, but i feel strongly about them, and that has to count for something.

I have an idea. proof of concept coming soon :)

This is just a reminder for myself!

Removing Twig would remove an extra step, and processing - which in turn would make the system run quicker, use a little less mem / cpu, and take up less space (with twig removed).

There's a suggestion to create a php template engine, but what about NO template engine (in favor of regular php / html / css for themes)?

I understand the concept of a Template Engine as an extra layer between the presentation and the processing designed to help people without much knowledge to create themes - here's the problem:

People who can't create a theme, don't want to learn a new 3rd party language to create it - they grab one of the millions of free themes already out there - for them, learning a new system is enough, they don't want to struggle with creating a custom theme too.

People who want a custom theme, typically already know how to create it - and would not use a 3rd party language (Twig) to create it.

I see only positives doing it this way - with the only negative being "some don't know html, php, css" (in that case they won't know Twig either, and would still have to learn css).

At any rate, just wanted to drop my 2 cents, I'll keep checking back.

The anti-Twig movement has grown recently to a degree I think is impossible to settle with a perfect solution.

At this point of time, something strike me and made me came to the conclusion, and that is: * there is no way to satisfy everybody at the same time.

Even ExpressionEngine doesn't use plain PHP but yet it remains one of the most favored blogging engines (cms, name it as you like) of web designers and developers. And believe it or not it's way more complicated than Twig is, that's for a fact.

Frankly, at the beginning I was eager to make the switch but then a discussion that took place in our IRC channel (which some of you may have missed) enlightened me, and right now I can say there is a final decision regarding this much rambled topic.

The poll was a nice move to gather various opinions and I'm glad and thankful for all you who voted.

The decision we took will shortly be announced in the blog. Still it may not make everyone happy. All I can tell you now is it's not going to be Twig but neither plain PHP, and it will come with Chyrp version 2.2.

This maybe will disappoint some, but first) Chyrp won't deviate from it's principles, and second) see my conclusion above.

This is a BIGGIE and debatable as a legal requirement, since it is arguable that Chyrp is a programmatic tool and not a web interface....

BUT what I should like to see is a THEME whose primary aim is ACCESSIBILITY. This could then enable us to identify any areas of Chyrp core that need any upgrades...

I'll make another thread on the subject as soon as I have installed the latest version to a "Vanilla" blog for the fixtheweb project to check out.... watch this space.

It would be good if every user could change his password himself. Currently, the admin has to do this which is annoying for both, admin and editor.

I would like to upload multiple pictures in one post using the photo feather

susepaste.org feather, it is great for posting code (highhlighting for any language for free) and not to have to bother about the storage, this is especially handy on overpriced VPS with almost no storage.

openID module, to let people comment if they have an openID