
@JonTheGeek @Netlify Not at all. I know the feeling.
That old traditional saying: "A watched DNS update never propagates"
That old traditional saying: "A watched DNS update never propagates"

@JonTheGeek @Netlify Waiting for DNS is the worst!

@JonTheGeek @Netlify Yikes! I've not seen that.
Did you make a recent change to your DNS to move your domain over? Very often issues like this are down to DNS propagation still happening. I'm seeing a successful site load FWIW.
Did you make a recent change to your DNS to move your domain over? Very often issues like this are down to DNS propagation still happening. I'm seeing a successful site load FWIW.

@JonTheGeek @Netlify The site looks good to me on either domain... but I do see (via dev tools) that there are all sorts of tracking codes and js requests happening. Seemingly from Disqus and the embedded Twitter view.
What was the error you saw? A complete failure or a partial load?
What was the error you saw? A complete failure or a partial load?

@ChrisFerdinandi I was pondering just that! Let me go through the form and double check the theme. Could be great!

@patrick_h_lauke It would be spinning by default.

@nowakowskipl @Netlify Ah... perhaps it is the routing... the CDN will be trying to find an asset on that paths, but with a SPA the path does not exist... I think the redirect settings will be what you need to tweak:
https://www.netlify.com/docs/redirects/#history-pushstate-and-single-page-apps
https://www.netlify.com/docs/redirects/#history-pushstate-and-single-page-apps

Phil Hawksworth
@philhawksworth •
When a conference digitally enhances you with a fancy 8-bit bow tie, it raises sartorial questions. https://twitter.com/coldfrontconf/status/965881463089479680

@coldfrontconf @Netlify Sartorial decisions:

@nowakowskipl @Netlify The route works via the link on your home page. Could this be a client-side SPA which does not have all of the routes pre-rendered as valid entry points? Do you get different behavior locally?
@Netlify can help with pre-rendering: https://www.netlify.com/docs/prerendering/
@Netlify can help with pre-rendering: https://www.netlify.com/docs/prerendering/

Phil Hawksworth
@philhawksworth •
Very excited to be returning to Copenhagen for @coldfrontconf again later this year. Its quality talks, friendly atmosphere, and great organisation have made it a firm favourite for me.
And there is a call for recommendations now open. Who do you want to see give a talk? https://twitter.com/coldfrontconf/status/963322097979109376
And there is a call for recommendations now open. Who do you want to see give a talk? https://twitter.com/coldfrontconf/status/963322097979109376

@jamchiller @Netlify Nice.

@Gedaly @Netlify Yes indeed! Once the redirects are deployed they should be very fast as they happen at the CDN. Not sure what a sensible max number of entries might be though.
I made a simple example which generates your redirects automatically:
https://github.com/philhawksworth/linkylinky
I made a simple example which generates your redirects automatically:
https://github.com/philhawksworth/linkylinky

Phil Hawksworth
@philhawksworth •
RT @thenewdynamic: 🔥 “Build Better Faster Websites: the New Dynamic 02/17 links and showcase” http://newsletter.thenewdynamic.org/archive/96681 with @philhawksworth…

@m1sp @Kikobeats @Netlify And @ddprrt wrote a great article on how you can use Wordpress as a back-end and get content from its API into a #JAMstack build.
https://fettblog.eu/wordpress-and-jamstack-sites/
https://fettblog.eu/wordpress-and-jamstack-sites/

@bdougieYO @Netlify I can't believe that day is already here. Legend!
I hope @github know how lucky they are. Good look BeeeDougie!
I hope @github know how lucky they are. Good look BeeeDougie!

@JordanHawker @Netlify Depending on how your site is built, this might be the information you're looking for:
https://www.netlify.com/docs/redirects/#history-pushstate-and-single-page-apps
https://www.netlify.com/docs/redirects/#history-pushstate-and-single-page-apps

@JordanHawker @Netlify Ack! I'm an idiot. I didn't spot that Intercom is for those on the paid plan. Best direct support contact without that is https://www.netlify.com/support/. Sorry for adding confusion there!
Meanwhile I'm afraid I don't quite understand the expected and actual behaviors you get
Meanwhile I'm afraid I don't quite understand the expected and actual behaviors you get

@JordanHawker @Netlify Hi Jordan. Would you mind asking this to support via the little intercom chat thing-a-mi-bob in https://app.netlify.com? That way the team can see your build/settings and diagnose things far more easily.

@chrisbiscardi @Netlify 👍

@toddhalfpenny 1.5p

@chrisbiscardi @Netlify Folders in your site will form the path on your site (so, yes... if I'm understanding your second example correctly).
You can also have different branches in your repo drive different subdomains domains.
Docs for that here: https://www.netlify.com/docs/custom-domains/#branch-subdomains
You can also have different branches in your repo drive different subdomains domains.
Docs for that here: https://www.netlify.com/docs/custom-domains/#branch-subdomains