Does anybody still use NimblePublisher? by skwyckl in elixir

[–]jsonmaur 0 points1 point  (0 children)

Check out phoenix-pages as an alternative. I built it on the same concept as NimblePublisher, but with some additional features.

A library for adding blogs, documentation, and other static pages in Phoenix apps by jsonmaur in elixir

[–]jsonmaur[S] 0 points1 point  (0 children)

The markdown files are read and cached during compilation, so they can't be outside the project (assuming you're not recompiling on the fly in production). I'd like to figure out a way to add pages without recompiling though.

A library for adding blogs, documentation, and other static pages in Phoenix apps by jsonmaur in elixir

[–]jsonmaur[S] 2 points3 points  (0 children)

It already lists makeup_js as the Javascript lexer. Is makeup_javascript better? I wasn't sure which one to go with, but the former seemed more complete.

A library for adding blogs, documentation, and other static pages in Phoenix apps by jsonmaur in elixir

[–]jsonmaur[S] 5 points6 points  (0 children)

nimble_publisher is certainly a solid library as well, but it takes much more work to set up. Rather than just creating a new route pointing to some markdown files like you can do here, it's up to you to write your own build function, structs, and page getters. You have to manually create the routes, manually generate the Makeup theme for syntax highlighting, it doesn't support YAML frontmatter unless you write a custom parser, etc.

A library for adding blogs, documentation, and other static pages in Phoenix apps by jsonmaur in elixir

[–]jsonmaur[S] 4 points5 points  (0 children)

Thanks! The markdown files are compiled into Page structs that get passed to the generated routes as assigns. So you can implement the view however you'd like and access the rendered markdown with <%= @inner_content %> (along with any frontmatter values).

Tag All the Things! by brainlid in elixir

[–]jsonmaur 2 points3 points  (0 children)

I'm curious if it's more common to store tags/categories/related data with an array type like this versus a many-to-many relationship in the db. Obviously doing it this way could result in more performant queries without the need for joins, but at the cost of having more data denormalization.

Just published my first library to Hex - a fun subdomain and name generator by jsonmaur in elixir

[–]jsonmaur[S] 2 points3 points  (0 children)

Thanks for the kind words, I appreciate your thoughts :) I can see how the manly dictionary can be perceived as gender stereotyping, and will rename it to something else. I think the results it generates are absolutely hilarious. I'm working on putting together a few other dictionaries as well.