Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
branch: master
Commits on Apr 23, 2015
  1. Merge branch 'master' of github.com:pothibo/ecrire

    authored
    Conflicts:
    	lib/ecrire/version.rb
  2. Merge pull request #138 from pothibo/template

    authored
    Template
  3. Fixed suggestion post

    authored
Commits on Apr 22, 2015
  1. Fixed Gemfile dev mode

    authored
  2. Merge pull request #137 from pothibo/template

    authored
    Post template rework.
  3. Post template rework.

    authored
  4. Removed body_tag as it mislead people thinking CSS selector should be

    authored
    off the body
    
    Overlays, popups and others exists inside the body but outside
    <main> and are styled by the admin engine. I want user to focus on using
    the <main> as their root css selector instead of <body> to not break css
    outside main.
Commits on Apr 21, 2015
  1. It's now possible to add a class to the body by using content_for

    authored
    This allow the blog theme to specify classes outside the layout. This
    will make it easier for someone to have global css styles matching a
    subset of the <body> by adding classes to different views
Commits on Apr 9, 2015
  1. Fixed typo... /facepalm

    authored
  2. Updatig gemfile

    authored
  3. Merge pull request #131 from pothibo/Gemfile-development

    authored
    [ci-skip] The default theme looks for ecrire in a local development path. Fix that
  4. The default theme looks for ecrire in a local development path. Fix that

    authored
    by using git@master which should fix #130
Commits on Apr 7, 2015
  1. Added new title option for the code block. Fixed issues with the parsers

    authored
    and the new line.
    
    Fixed Updated tests to cover those corner case
  2. Merge branch 'markdown'

    authored
  3. Merge pull request #128 from pothibo/markdown

    authored
    Markdown
  4. Removed Kramdown and switch to my own implementation of markdown

    authored
    This is introduced because I wanted to use a markdown engine on the
    server that reflects the features implemented on the frontend.
Commits on Apr 6, 2015
Commits on Apr 4, 2015
  1. Fixed URL issue

    authored
  2. Merge pull request #126 from pothibo/production-redirect

    authored
    Theme are now tested and also production blog will redirect some errors ...
  3. Theme are now tested and also production blog will redirect some erro…

    authored
    …rs back to the page which is a fix for #108
  4. Fixed onboarding theme and default template

    authored
    Also added tests that will make sure that next time I make change to
    Ecrire, the onboarding and default theme will behave as expected.
Commits on Apr 1, 2015
  1. Merge pull request #125 from pothibo/routes

    authored
    Got sick of using named routes.
  2. Got sick of using named routes.

    authored
    Named routes module is a leaky abstraction. First, routes are split when
    the engines are isolated, which isn't always obvious. Then, I always
    have to type ````rake routes``` to remember what named routes I should
    use.
    
    Third, and probably the most important, is that keys cannot be map
    easily to an object which I think is pretty dumb since URLs are *built*
    with models. to_param returning a string instead of a hash was just the
    icing on the cake.
    
    So, instead of trying to be extra clever about everything, I decided to
    introduce a ```url(string, options ={})``` method where you pass a url
    structure as a first parameter and a hash with the objects you want to
    map into the URL.
    
    Here's an example
    
    ~~~ruby
     # Before:
    post_path(@post.year, @post.month, @post.slug)
     # After:
    url('/:post.year/:post.month/:post.slug/', post: @post)
    ~~~
    
    Nested resources now can be as complex as you want. Here's an example
    
    ~~~ruby
     # This method could return all post published in a year with the given
     # tag.
     # The named routes would require you to do either complex
     # routing/parsing or would need to use GET params.
    url('/tags/:tag.id/posts/:post.year', tag: @tag, post: @post)
    ~~~
    
    This, I believe, is much easier to maintain and understand.
Something went wrong with that request. Please try again.