marionettejs / blog Goto Github PK

We should have a blog post on Marionette Modules and our plans for them. This is just to document that I'm writing it now!

This seems to be something with a lot of value that is under documented and not explicitly an opinion of Marionette. But not following a pattern like this can get you into trouble.

I think @marionettejs/marionette-core should consider either removing the blog, or having a regular release schedule and goals.

Possibly reconsider having guest posters, or even repost, or having tl;dr posts linking to other useful blog posts out there.

The blog should be some centralized useful, somewhat regularly updated place for all things marionette.

This works fairly organically for the YouTube channel. But the blog should try and utilize content that's already being created so it's less of a burden to keep things fresh.

You can use the Renderer to make specifying your view templates a lot easier.

The first two posts haven't been reviewed so they shouldn't be live yet.

Write post about features/changes in new v3

Blog post related to @jasonLaster's video on behaviors. This is a fantastic new feature to Marionette. People should learn it early and use it often.

Continuing #34 I propose to write some easy start post/configuration with build tools. We have Mn integration repo where all this stuff is configured. So it will be just sharing some config examples in article and pointing how to easy build Mn apps.

I think most of you aware about post https://hackernoon.com/how-it-feels-to-learn-javascript-in-2016-d3a717dd577f#.px3ilttei how it's hard to start learning js nowadays.
For newbies it's hard to try smth fancy like Angular2.0 because of big stack of technologies (typescript, jsx etc..)
I propose make post for people who already new js basics and wanna try some framework. Of course it wil be about Marionette.js 😄

Soon we'll have Guides on the website. What should the distinction be for when something should be a guide, or a blog post? Should guides be entry-level looks at a topic, and blog posts be a more detailed analysis? I'm not too sure!

We should set up an nginx server, or something, that drops the suffixes to the blog posts. I can set up and host a server on Bocoup's AWS account if we're 👍 to that.

https://github.com/marionettejs/blog/blob/master/source/_posts/backbone-radio.md

When I view http://blog.marionettejs.com/ the logo does not appear. Requesting http://marionettejs.com/images/marionette_logo-4eeb07e5.png gives a 404 error. I don't see a logo png file in the source repos. Whomever can build and push the blog needs to add the logo file.

/cc @jdaudier

As I'm concerned we have it on marionettejs.com. It will be nice to have it here.

Add fixed top nav and update colors (blue) to match new site

v3 and v4.

An Architecture Update and a View Update. I'd like to write this one, too, unless someone else is just jonesin' to write a blog post about our future major releases. Just lemme know – I got 2 others in the works so it's nbd.

https://github.com/marionettejs/blog/blob/master/source/_drafts/v201-release.md

This is placeholder - would be nice to get more into the details on WHY they should upgrade

I should write about using Radio in v2.3

https://robots.thoughtbot.com/blog-in-markdown-deploy-with-webhooks
https://developer.github.com/webhooks/

Was reading this post and wondering if there's a way we can do something similar where once a new post gets merged to the master branch of the content repository, we respond by kicking off a new deployment.

cd into `public` folder
git add .
git commit -m 'publish <TITLE>' && git push live master:gh-pages

@thejameskyle's Wires shows off a really awesome pattern for Backbone/Marionette: making a directory of Base objects. I should write a post about why I think this is really beneficial to devs.

This is in reference to:
Note: The Marionette.View class is not intended to be used directly.

I think this should be changed. I find that using views directly is a good way to provide an interface to existing elements, or an interface to other view types. In this case it acts as a "controller" of sorts. Say you have a group of tabs and each tab renders a different collection, a view can provide an interface to handle the transition.

https://github.com/hexojs/hexo/releases/tag/3.0.0-rc.3

• Medium is way better for authoring and drafts..
• It's where readers are
• we can get a custom domain so just point blog.marionettejs.com to medium
• we can request other marionette or even backbone posts be published by our publication with a click.
• anyone can submit just like on here except they can still publish it if we turn it down (for some reason)
• no maintenance

https://help.medium.com/hc/en-us/articles/214559417-New-Publication

@samccone and others are doing great work over on the new website. The blog should be integrated with that site.