deadsuperhero / pine Goto Github PK

I suspect this is happening because of an incorrect usage of Permitted Params, which I am a bit unfamiliar with in Rails 4+. Basically, I have two fields that do not update, and currently do not render:

• Name (string)
• Avatar (string, via CarrierWave)

Currently trying to figure out the right place to tweak this.

This is something I have little experience in, but I want to learn. This app is going to need some basic tests, as it grows more complex a TDD approach will be necessary.

Currently, posts are only public if the boolean for Public is marked. It would be great to display a list of Drafts for any article that isn't public, with the exception that only the author can view it.

It would be nice to allow articles to be tagged by the original author for categories.

This can be accomplished by using the acts_as_taggable_on gem. The other half of this will probably require an appropriate jquery plugin of some sort.

Semi-minor thing, but I need to check that Devise permissions are properly set on articles. We don't just want to check that authors are signed in, we also only want to permit such actions to the original author.

Currently, Pine does not allow for basic customization of itself. Specifically, I should focus on these things:

• Name for the site
• Description for the site
• Brand logo
• Allow signups?
• Approval queue for registrations?
• Copy for footer text

Weird bug, basically saving the form the first time on a create action for a new article seems to submit blank content for title and body fields of the article.

Editing seems to update the article without any problems, but for now when someone makes their initial article, they lose all of their work, and can't view the post without using the edit action.

Need to come up with a fix, a little clueless on this one.

This actually requires more investigation. I can see some benefits in doing this to play nice with other servers, but I'm also holding some assumptions about how other OStatus servers would react to a conversation that relies on a GUID string as a conversation_id.

Publications are a model that belong to authors, that have many articles. A publication basically acts as a list of articles, authors can declare which publication an article gets assigned to.

Publications should also have an endpoint similar to users, allowing them to be followed through OStatus subscriptions. What would be really cool is if a feed could somehow preserve attribution of the original author for each individual article - the question then becomes: how does one do that exactly? Is every article in a Publication's feed effectively a "reshare"?

Turns out that textarea and input elements have some fun limitations. Need to figure out:

• How to increase the height of the article name field when more than 1 row sits in the textarea
• How to set sane default fallbacks for scenarios when someone is either writing a new article, or editing an old one.

An extension is available that brings in full image functionality, complete with layout capabilities. However, I'll need to investigate the best way to incorporate that into the assets pipeline.

Plugin: https://github.com/orthes/medium-editor-insert-plugin

The bonus is that it also supports video embeds, and embeds from other social networks. In theory, might be possible to even take embeds from GNU Social or Mastodon?

So, time to do a little bit of planning. This is pretty new territory, but in principle it seems simple.

The OStatus2 Gem is what Mastodon uses for OStatus-based federation. Since it's Ruby-based, it will work with our Ruby on Rails app.

This issue seeks to explore and plan out the different aspects of this gem, and consider methods of implementation in Pine. The docs seem a bit cryptic, so figuring out the "correct Rails 4+ way" to do this will be less-than-obvious.

So we need to:

• Construct an XML-based Atom Feed that features Articles (showing each Title and Body)
• Make sure that each entry references the Article author (useful for multi-author publication feeds)
• Create an hCard for Authors and possibly Publications
• Do something with Salmon so that interaction is possible. This is perhaps the part I currently know least about

Concepts:

• Every Author has their own feed, with stream entries that are the contents of articles.
• Each Article should have comments, which are federated.
• Entries should concatenate the title and body field, and truncate the result for the stream entry
• A Publication might represent a collection of authors, and would need attribution for each individual article. Does this mean that

Shouldn't be that hard to add support for. This just basically requires a quick migration and some CarrierWave assignment. Would be really nice to make some kind of AJAXy button for a smooth upload of image.

As a bonus, that image can be passed as the og:image value for any article post.