Posts in top-level in _posts are not recognized/rendered about distill HOT 6 CLOSED

Each post needs to be in it's own folder (that is what is meant by "top-level", a top-level folder for each post)

from distill.

That's… not how I interpret that statement, but okay, that's alright.
I moved each Rmd file in its own folder, but they still don't build.
Folder structure here: https://github.com/jemus42/qm.jemu.name/tree/master/_posts

I'm starting to suspect there's either a bug or "You can use whatever scheme you like to organize the _posts directory" is a slight overstatement :/

from distill.

I need more info than "they still don't build". When I try to render your site locally I get this error:

Error in contrib.url(repos, "source") : 
  trying to use CRAN without setting a mirror
Calls: <Anonymous> ... withVisible -> eval -> eval -> install.packages -> contrib.url
Execution halted

Exited with status 1.

Every other Radix blog uses exactly this structure (_posts directory as you have) so my suspicion is that errors you are seeing are not related to folder structure.

from distill.

Sorry. When I click the RStudio "build" button or manually enter rmarkdown::render_site() in the console, the site itself is generated correctly, i.e. the index.html and about.html are generated, but none of the posts under _posts is generated, i.e. no html files are created.

I have now worked around this by manually rendering each .Rmd file under _posts and built the site afterwards, now everything shows up properly.
Since this "concluded" my project and I don't have to touch it again soon, I'm fine with that, but I thought there was either a bug or an issue with the documentation, but if you can't reproduce the problem then I guess you might as well close this issue.

Regarding your problem building the site, the lack of a set CRAN mirror does not look like a problem with my site because I don't touch CRAN repos anywhere oO

from distill.

Okay, now I get what's going on. That's actually the design of Radix -- you render posts individually then they are compiled into a site. If we didn't do it this way then as you got into dozens or hundreds of posts it would take forever to render the site. You also might get into reproducibility issues attempting to render posts from e.g. a couple of years back. So the idea is that you render posts individually as you author them.

from distill.

Well now I feel silly. Thanks for clearing this up m)

For context: I use blogdown (and love it) and wanted to investigate whether radix could be better for a particular use case. In blogdown, I use blogdown::build_site() to rebuild the entire site including all blog posts specifically to catch reproducibility issue in older posts to update them so they are still "valid" today.

The radix approach, however makes a lot of sense, of course, I just wish there was an easy way to build all the posts. Let's say you're importing a bunch of Rmd files from a different project (as I did) and want to render all of them, then having to render them individually is kind of inconvenient. Maybe a simple helper function that looks for Rmd files under _posts and renders them would be neat.

Anyway, my original question in this issue has been cleared up, thanks!

from distill.