marionettejs / blog Goto Github PK

View Code? Open in Web Editor NEW

4.0 12.0 8.0 463 KB

:memo: Blog for Marionettejs.com (hosted on the gh-pages branch)

Home Page: http://blog.marionettejs.com

JavaScript 9.25% CSS 60.77% HTML 29.99%

blog's Introduction

Marionette Blog

This blog is built using Hexo.

Topic suggestions

Please create a new GitHub issue for topic ideas that you would like us to write about

Steps to get it running:

1. Fork this repo

2. `npm install`

3. To create a new post in markdown: `hexo new draft <filename>`

4. Edit the file with your file name in this directory: _drafts

5. Edit your title at top of the file

6. Add a tag at the top of the file so that it can be filtered, choose from:

tags: news
tags: notes
tags: releases
tags: tutorials (beginner)
tags: tutorials (intermediate)
tags: tutorials (advanced)
tags: behind the scenes

Note: Make sure you add a space after the colon

To add multiple tags:

tags:
- news
- releases

7. Add your name as the last tag (after the word `by`):

tags:
- news
- by Uncle Bob

Note: Make sure you write your name the same way for all posts so it filters correctly (so no Uncle Bob one week and Uncle Bobby the next)

8. To edit a post that has been published, edit the file in this directory: _posts

9. Turn on the server: `hexo s` (if port 5000 is being used already, try `hexo s -p 4000`)

10. Preview your post at: localhost:5000

11. Once you're satisfied with your changes, send a pull request

Steps to go live:

12. To publish a post (moves a post from _drafts to _posts directory): `hexo p <filename>`

13. To generate static files into the `public` folder for hosting: `hexo generate`

14. To preview the blog: open the `index.html` file in the `public` folder

15. One time setup:

cd public
git init
git remote add live [email protected]:marionettejs/blog.git

16. To push to the `gh-pages` branch - NOT MASTER - (this is where blog.marionettejs.com is hosted on GitHub):

Make sure you're still in the public directory
git add .
git commit -m 'publish <TITLE>' && git push live master:gh-pages

Adding Images

There's a matching folder with the same name as your post. Save you image(s) in that folder.

To link to the image:

![alt text](/path/to/img.png "Title")

Code Highlighting

Backtick code block

``` [language]

    code snippet

```

More info on formatting: http://hexo.io/docs/tag-plugins.html

Disqus Syntax Highlighting

If you're responding to a comment on Disqus and want syntax highlighting, place your code inside <pre><code> tags. For example:

<pre><code>
var foo = 'bar';
alert('foo');
</code></pre>

Happy blogging!

Got questions? Contact @jdaudier at

blog's People

Contributors

Stargazers

Watchers

Forkers

jamesplease denar90 scott-w dsamodra ziedjabnoune hoshmands90 fragaly gmcmaroc

blog's Issues

Upgrade to Hexo v3.0.0-rc.3

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

Add a post discussing uses of Radio

Drop the .html suffixes to blog pages

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.

Using the Renderer

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

viewModel pattern / best practices

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.

Drop the blog and just use a medium publication

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

Documentation suggestion for views

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.

Add Google Analytics

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

Easy start with Marionette.js and build tools.

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.

Integrate the blog with the new website

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

What's new in Mn v3

Write post about features/changes in new v3

Light start with js frameworks using Marionette

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 😄

Using Radio in v2.3

I should write about using Radio in v2.3

BB.Radio blog post

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

Blog is already stale

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.

v2.0.1 blog post

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

Marionette's future major releases blog post

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.

Remove unreviewed posts from the live blog

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

logo does not show on blog

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.

Determine guidelines for a Guide vs. a Blogpost

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!

Auto deploy

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