[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GMG-Devel] Fwd: Re: About Blogging System Project
From: |
Christopher Allan Webber |
Subject: |
[GMG-Devel] Fwd: Re: About Blogging System Project |
Date: |
Mon, 22 Apr 2013 09:17:06 -0500 |
User-agent: |
mu4e 0.9.9.5-dev5; emacs 24.1.50.1 |
Spaetz meant to send this to the list but accidentally only sent it to
me, so forwarding! :)
Sounds like we're on the same page.
Sebastian Spaeth writes:
> On 16.04.2013 21:12, Christopher Allan Webber wrote:
>> Greg Grossmeier kindly brought up something on IRC that is a concern of
>> mine as well: scope creep.
>>
>> As brought up on IRC, the biggest reason *against* blogging as part of
>> MediaGoblin is scope creep.
>
> Yes, there is plenty to do in our core areas (search and federation to
> mention the most important ones). So I am all for adding (if at all) a
> rather zero-bloat blog plugin only as an option.
>
>> Here are my thoughts on how to do a zero-bloat blogging system in
>> MediaGoblin that respects the architecture we have.
>>
>> - Blogposts are media entries, and don't try to pretend otherwise.
>> They show up in galleries, maybe with a special icon, or maybe a user
>> can supply a thumb; whatever. If you don't like this too much, don't
>> use MediaGoblin as a blog! (or read my next two bullet points ;))
>
> Yes, that is the simplest option and it is actually the one that I
> currently favor (it requires NO changes to the core). One thing the blog
> plugin would bring in addition is a template for a "gallery view" that
> filters by media type (ie shows only blog posts).
>
>> The most complicated part of this is how to get appropriate
>> javascript into the {% head %} element... I have an idea for this
>> that involves each media type declaring that bit and then looping
>> through the head of all templates with what's needed here, and this
>> also can work with the {% include %} stuff... I can explain on IRC
>> better though. :)
>
> Write, perhaps each mediatype can simply declare the name of a "js" and
> "css" template name that is being {%include ...%} and the template just
> groups and includes all required files once... Or even better, our
> gallery view should not depend on media-type-specific code :-).
>
>
>> - Lastly, for those who want the "deviantart" style of having the
>> gallery of their images on their homepage but the blogposts listed in
>> a separate section off to the side, we can have a plugin that mangles
>> the user's homepage, and if they want, other pages too to do
>> filtering on that SQL statement and etc. I think it wouldn't be
>> pretty, but if people really want that, they can do it in a plugin
>> without messing up the MediaGoblin main code if we provide the
>> appropriate hooks.
>
> Right, the blog-post only gallery can come as a separate plugin
> template. The "supress blog posts from user media timeline" is left to
> masochistic readers for homework.
>
>> How does that sound? I realize it's a bit of a braindump ;)
>
> Sensible. A blog plugin makes a nice gsoc project, but otherwise we
> should focus on core things such as search and federation :-).
>
> Sebastian
- Re: [GMG-Devel] About Blogging System Project, (continued)
- Re: [GMG-Devel] About Blogging System Project, Sebastian Spaeth, 2013/04/12
- Message not available
- [GMG-Devel] About Blogging System Project, Aditi Mittal, 2013/04/15
- [GMG-Devel] About Blogging System Project, Aditi Mittal, 2013/04/15
- Re: [GMG-Devel] About Blogging System Project, Aditi Mittal, 2013/04/15
- Re: [GMG-Devel] About Blogging System Project, Sebastian Spaeth, 2013/04/16
- Re: [GMG-Devel] About Blogging System Project, Christopher Allan Webber, 2013/04/16
- Re: [GMG-Devel] About Blogging System Project, Christopher Allan Webber, 2013/04/16
- Re: [GMG-Devel] About Blogging System Project, Christopher Allan Webber, 2013/04/16
- Message not available
- [GMG-Devel] Fwd: Re: About Blogging System Project,
Christopher Allan Webber <=