Skip to content
This repository has been archived by the owner on Jul 21, 2019. It is now read-only.

Add Travis build step #17

Closed
mattstratton opened this issue Nov 14, 2016 · 3 comments
Closed

Add Travis build step #17

mattstratton opened this issue Nov 14, 2016 · 3 comments
Labels
Milestone

Comments

@mattstratton
Copy link
Member

mattstratton commented Nov 14, 2016

Should crawl all the links in the site now and check for any type of errors, either http status or inside the console

@mattstratton mattstratton modified the milestone: v3.0 Release Dec 6, 2016
@mattstratton mattstratton modified the milestones: v2.0 Release, v1.0 Release Jan 18, 2017
@bridgetkromhout
Copy link
Contributor

Won't a lot of old links probably be bad? Do we want to break if some speaker from 2013 deleted their website or something?

@mattstratton
Copy link
Member Author

I think my theory is that a bad link is a bug on the site and needs to be fixed. So even if someone did delete something, that's a maintenance task to fix it.

I think that maybe it doesn't go in Travis; there's probably some type of other way we can have the site be crawled for bad links and then turn them into issues to fix. Actually, I think that Google's search console does that for us.

In fact, it does:

image

@mattstratton
Copy link
Member Author

Not needed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants