New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CHANGE docs for 0.6 release #234
Conversation
@@ -3,27 +3,27 @@ | |||
|
|||
/* TODO: cosmetic changes needed */ | |||
.source_btn { | |||
position:relative; | |||
position:relative; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see different code style is applied here and there, from 4 to 2 spaces. Let's stick to one, and add csslint/eslint/editorconfig? Keeping the 4 spaces as the standard.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And I would really like to have style changes as separate PR next time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've tried to make it 4 spaces everywhere, in this particular code example it's 4 spaces.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
eslint is definitely a must do!
Getting an error on
|
|
||
### Server-side Templating Engines | ||
|
||
As we mentioned before, it's easy to use other server-side templating engines like Jade, you only need to create a simple SourceJS middleware ([example](https://github.com/sourcejs/sourcejs-jade)) or process your sources with Grunt/Gulp. | ||
As we mentioned before, it's also possible to use *other* server-side templating engines like Jade. You need to create a SourceJS middleware that will perform the rendering. Our [sourcjejs-jade Middleware](https://github.com/sourcejs/sourcejs-jade) may serve as an example of such middleware. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's keep the name "plugin" for all "sourcejs-*" extensions, middleware is just a type of a plugin, and the name "plugin" in more approachable for non-node devs.
Huge tanks for the help with docs, that's one one of the blockers before final release. The hardest part left now, is to determine the migration path, and re-check compatibility. |
Thanks for the feedback, I'll work on it more this week. Sorry for the whitespace commit, I noticed I had placed tabs everywhere, so I had to clean it up. |
Adding zero-width spaces breaks ejs pattern-finder
# Conflicts: # assets/js/modules/loadEvents.js
Merged 0.6.0-dev into this branch, if you have no further comments, it can be merged in? |
@operatino We should pick this up and possibly merge? Let's release 0.6! |
@ndelangen, yeah, let's finally do it. I've been cleaning up the issues, not just need to sit down and re-test everything. |
😴 |
🙁 |
😇 |
I'll revisit the file name structure in docs folder, but the rest is fine now. Next weeks I'll have few free days, will start final preps before 0.6 release. |
I've given the docs an overhaul. I'll work on it some more later I think.
Feedback is very welcome.
I spend a considerable amount of time getting the scrolling behavior to work in in casperjs; something I did made it not work anymore, and thus I refactored that a bit into what seemed like a sane test to me.