<p dir="auto">We have structured our files so that page specific code is in the pages folder. Here is an example:</p>
<ul dir="auto">
<li>pages
<ul dir="auto">
<li>manage-users
<ul dir="auto">
<li>__tests__
<ul dir="auto">
<li>manage-users.test.js</li>
</ul>
</li>
<li>index.js</li>
<li>components
<ul dir="auto">
<li>ManageUsersPage.js</li>
<li>&lt;other page specific components here&gt;</li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
</ul>
<p dir="auto">The index.js file has the ManageUsersPage.js components as its default export. That is a regular next.js page component</p>
<p dir="auto">This structure has worked fine for us except when we build. This hardcoded glob assumes that all js files under pages is a page: <a href="https://github.com/zeit/next.js/blob/canary/server/build/webpack.js#L50">https://github.com/zeit/next.js/blob/canary/server/build/webpack.js#L50</a></p>
<p dir="auto">Does it make sense to make this glob overridable or do we have to not use file based routing?</p>
<h1 dir="auto">Bug report</h1>
<h2 dir="auto">Fixed Sidebar Not working after route change.</h2>
<p dir="auto">I have implemented a fixed sidebar in my next app using <code class="notranslate">react-sticky-box</code>. The sticky sidebar is working perfectly fine when the page is reloaded from the browser's reload button but stops working once the page is changed clicking the next.js's  Link tag.</p>
<h2 dir="auto">System information</h2>
<ul dir="auto">
<li>OS: macOS</li>
<li>Browser  chrome</li>
<li>Version of Next.js : 9.0.6</li>
</ul>