Adventure Thru Inner Space: WP:GNG is very weak.  Sourcing is 90% Youtube, with one footnote to a passing mention in a news story and another mention in "The Disneyland Encyclopedia".  Per WP:ATD-R , I suggest redirecting this to Tomorrowland (Disney Parks) .  Piotr Konieczny aka Prokonsul Piotrus | reply here 12:56, 5 March 2024 (UTC) [ reply ] Note:  This discussion has been included in the deletion sorting lists for the following topics: Science fiction and fantasy , Toys ,  and United States of America .  Piotr Konieczny aka Prokonsul Piotrus | reply here 12:56, 5 March 2024 (UTC) [ reply ] Note: This discussion has been included in the list of Disney-related deletion discussions .  Toughpigs ( talk ) 16:54, 5 March 2024 (UTC) [ reply ] Comment - There is actually a lot of information on this ride out there - the problem is that most of the ones that go the most in-depth are either primary (being published by/posted on actual official Disney owned platforms) or would not be considered a reliable source (Disney/Disney Park fan sites).  I did find this article from the Los Angeles Times about a virtual reality re-creation of the ride to preserve it that was showcased a decade ago, which also discusses the original ride as well a bit more in-depth than the current LA Times article being used as a source in the article.  There are also a number of books out there that have a paragraph or two describing/discussing it.  While most of them fall along the lines of the many "unofficial Disney park guides" style book, there was also this one that seems a bit more promising.   Though, I'm also not sure if any of them actually have enough on the ride to be considered significant coverage.  I'm currently leaning towards a merge to Tomorrowland (Disney Parks) (or any other more appropriate target if someone has a better recommendation), but as this one is a bit on the edge for me on whether or not it pass the WP:GNG , I'll hold off on a formal recommendation for now, to see if anyone else has any luck finding anything more substantial than what I found in my own searches.  Rorshacma ( talk ) 16:57, 5 March 2024 (UTC) [ reply ] Keep : There are five pages on "Adventure Thru Inner Space" in the book The Disneyland Story: The Unofficial Guide to the Evolution of Walt Disney's Dream (2014), an independent published source.  There are two pages on the attraction in the book The Disneyland Encyclopedia (2017), also an unofficial and independent published source.  There was also contemporary newspaper coverage when the attraction opened; I added references to two articles, including the syndicated " Monsanto Opens Attraction on the Atom at Disneyland ".  This is enough to demonstrate notability.  Toughpigs ( talk ) 17:43, 5 March 2024 (UTC) [ reply ] Note:  This discussion has been included in the list of Amusement parks-related deletion discussions .  WC Quidditch ☎ ✎ 20:51, 5 March 2024 (UTC) [ reply ] Relisted to generate a more thorough discussion and clearer consensus.  Please add new comments below this notice.  Thanks, asilvering ( talk ) 20:37, 12 March 2024 (UTC) [ reply ] Keep : Keep per sources provided by Toughpigs.  StreetcarEnjoyer (talk) 22:23, 12 March 2024 (UTC) [ reply ] Comment to closer .  If this is kept but not improve, please replace notability template with {{ sources exist }} .  TIA.  -- Piotr Konieczny aka Prokonsul Piotrus | reply here 00:52, 13 March 2024 (UTC) [ reply ] Piotrus : I improved it — I added information and references from all of those sources that I mentioned.  Did you look at the current state of the article?  Toughpigs ( talk ) 01:54, 13 March 2024 (UTC) [ reply ] Keep the sources included in the current version of the article are sufficient to support notability.  Eluchil404 ( talk ) 00:27, 19 March 2024 (UTC) [ reply ] The above discussion is preserved as an archive of the debate.  Please do not modify it.  Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a deletion review ).  No further edits should be made to this page.

Discussion outcome: keep