Routing: IronRouter is recommended, and can I split the html?

[pickhardt]

For websites using Meteor, is IronRouter the recommended router? https://github.com/iron-meteor/iron-router

I have been looking around IronRouter and it is unclear if you’re supposed to just throw all the various views into one big HTML file. I’d prefer to have something like

/views
  index.html
  faq.html
  contact.html
  _layout.html (this contains the header and footer and any other JS like Google Analytics)

Is there a good blog post or something I can read about this to learn more?

[Steve]

For websites using Meteor, is IronRouter the recommended router?

It is a mater of taste and requirements. Although I still use Iron Router (for historical reasons), my advice is to not use it, cause it is an overly complex package with pending issues. Alternatives are: 1. no router 2. flow-router.

[sergiotapia]

Almost every bit of Meteor code I’ve seen in the wild uses iron-router. It’s even recommended in the Discover Meteor book. If you’re used to routing a-la Rails, then it’s highly recommended because you will feel at home and waste less time.

[Steve]

Some more ref:

Should I be using Iron Router (or is it dying)?

I’ve been developing with Meteor since last Fall and have LOVED it. Props to the MDG team for their awesome work. I started my Meteor journey by following the Discover Meteor book tutorial. This was my first introduction to Iron Router. I have built quite a few apps with Iron Router, and it seems to work well. However, I’ve seen a number of posts on different sites all stating that Iron Router is no longer being maintained and that it would be better to switch to something like @arunoda’s Flow …

Question to MDG: Building routing into core

Do you guys intend on building routing into core? It feels like Iron Router is no longer being maintained, with 240 open issues on Github and latest update half a year ago… It’d be sensible to have this vital functionality natively built-in and maintained by MDG.