Skip to content

Conversation

@ffes
Copy link
Member

@ffes ffes commented May 21, 2016

Closes #49

This adds a blog to the website. I used Jekyll to create the posts. See the Jekyll docs for more information how to add new posts or use drafts.

I have written two quite simple posts. One announcing the blog and the other one announcing the new version of the Notepad++ plugin

ffes added 3 commits May 21, 2016 14:07
- Add required front matter fields
- Join lines to better word wrap
- Various minor improvements
@ffes
Copy link
Member Author

ffes commented Jul 1, 2016

I just pushed two additional commits.
Any changes anyone could take a look at this?

cc @xuhdev @treyhunner

@xuhdev
Copy link
Member

xuhdev commented Jul 2, 2016

Thanks! I'll look into this tomorrow and give my comments.

@xuhdev
Copy link
Member

xuhdev commented Jul 2, 2016

It looks good to me, except for that it's a bit weird to have the "Blog added" post not the earliest post. Besides that, I think it's ready to be merged. @treyhunner What do you think?

@ffes
Copy link
Member Author

ffes commented Jul 4, 2016

I understand your point about the date of the "Blog added" post. I added two posts (in the original PR) to have some content. Since there is a new release of the N++ plugin after this PR was opened, the first post (announcing N++ plugin v0.3.0) can be deleted anyway.

@treyhunner
Copy link
Member

@ffes thanks for the work you've put into this!

I have a couple stylistic suggestions for the sidebar (see screenshot below), but I'll avoid bike shedding over those. I can make those changes after we've merged this.
selection_797


As for the blog itself:

  • When should posts be written?
  • Who will write posts?
  • Should we encourage plugin authors to write posts announcing new features in their plugins?

I can help edit posts, but I don't think I'll be authoring many myself.

@ffes
Copy link
Member Author

ffes commented Jul 6, 2016

I like the stylistic changes. The reason I choose the slightly indented layout was because that is what the current layout is. But I agree this definitely looks better. And I am not a web designer, so layout adjustments will almost certainly be an improvement over what I have done.

When should posts be written?
Who will write posts?
Should we encourage plugin authors to write posts announcing new features in their plugins?

In #48 @xuhdev states that a blog would be great for announcements. I think (being "a new guy" to this project) the most announcements would be about plug-in releases. So I think that will be the main content of the blog. And writing a blog post is not too difficult: copy an existing, write out the new features and create a PR. It should be relative little work for plug-in authors to create a blog post. The advantage for them is that their works get noticed.

Some final reviewing on the English by a native speaker (which I'm not) would be great.

@xuhdev
Copy link
Member

xuhdev commented Jul 6, 2016

I agree with @ffes . The blog would be the best place (IMO) to make announcements. It can also be used to make other project-wide announcements. If @treyhunner is OK with it, either of us can merge the PR.

@xuhdev
Copy link
Member

xuhdev commented Jul 12, 2016

@treyhunner Do you have any problem with merging the PR?

@xuhdev
Copy link
Member

xuhdev commented Jul 12, 2016

@ffes Before merging, can we remove the Notepad++ 0.3.0 announcement?

@xuhdev
Copy link
Member

xuhdev commented Jul 12, 2016

Or make the blog anouncement earlier...

As discussed in editorconfig#57.
Since the blog wasn't merged before 0.3.1 was released, there
is not much need for the announcement of 0.3.0

And now the "Blog Added" post is the oldest, which is more
natural.
@ffes
Copy link
Member Author

ffes commented Jul 12, 2016

I just remove the N++ 0.3.0 post. So now "Blog added" is the first one.

@xuhdev
Copy link
Member

xuhdev commented Jul 13, 2016

Thanks! I'll merge it and make an announcement in the mailing list for all the plugin authors to make announcement on the website when they make new releases.

@xuhdev xuhdev merged commit 67a887a into editorconfig:master Jul 13, 2016
@ffes ffes deleted the blog branch July 13, 2016 08:55
@ffes
Copy link
Member Author

ffes commented Jul 13, 2016

Maybe @andreynering could be asked to write a post about the new core-go he release a couple of days ago.

@andreynering
Copy link
Contributor

andreynering commented Jul 13, 2016

@ffes I'd happly do that, if you guys are OK with that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants