April 6, 2019

Building a Website With A Single Page

I've been experimenting lately with building my web apps with a single page, using modal forms to take care of additional pages, like the terms of service, faq, the settings, etc., or checking URLs to show different things on a page. For me, it keeps things even more organized and simple.

It has actually come out to two pages so that I can throw up a regular index page and some type of dashboard as a secondary page, but I remember I used to create hundreds of pages and this was just getting to be too much. I notice with the one-page method, I'm more likely to complete my projects when I start them and I release them faster too.

Has anyone else adopted this method?

#ask-ih

  1. 1

    That’s what I’m trying as well. Keeps things less complicated for now, but there are also occasions you would want multiple pages.

  2. 1

    I pretty much never build single page websites but there's certainly no harm in it.

    My latest venture could completely be a standalone page (I purposefully don't link to any other pages from it) and it's converting and performing really well.

    It's only really an issue if you care about search traffic and lots of rankings :)

    1. 1

      It's only really an issue if you care about search traffic and lots of rankings :)

      Most people who create web apps only get a few pages indexed anyway and unless they started a blog, there wouldn't be too much of an issue.