Jonathan Yankovich

As a counterpoint, having the documentation in source control makes a lot of sense to me. I agree that the readme could be improved and split out into multiple files,...

For the benefit of others - this seems to be due to repaints - One post said "if you don't use `position: relative` then performance improves significantly". Another said they...

If anyone is doing a lot of active work on their fork, we could make a PR to add a link to that repo to the README so people could...

@stevensonmt Sounds reasonable to me. Not sure if that would have implications with compilation vs runtime, since i don't know the details of the internals very well, but that sounds...

I'm all for keeping it simple. I'd love to get something going that I could start to work with, test, and use, even if it was pretty verbose (as in...

I dug into this pretty deeply - To implement HEEx name/attribute awareness, the changes to the library itself aren't that significant, its more how the engines are wired up. Here's...

I discovered something interesting and problematic. This function: ``` defp render_attribute_code(name, content, _, safe) do value = if safe == :eex, do: "slim__v", else: "{:safe, slim__v}" """ \ \ =""\...

I've got a working branch! It requires changes to both `slime` and `phoenix_slime`. The changes are actually pretty trivial on both sides (assuming I didn't do something horribly wrong). I...

I have a branch running that successfully generates HEEx which is then parsed by to produce HTML. I would love some feedback on the approach. The work is done in...

It's working great, I'm using it in production and haven't run into any issues. Currently it doesn't support a sigil, which as far as I know is the only parity...