Deciding What Belongs on the Site

I have more ideas for RitesDev than I can fit into one first version of the website.

Some ideas are pages people need in order to understand the business. Others are projects I may build later, or tools that make my own work easier. They all feel related, but they don’t all need to be on the public site right away.

Keep the visitor in mind

The question I ask is: does this help someone who visits the site?

If it explains a service, gives useful background, or helps a person get in touch, it probably belongs somewhere in the public website. If it’s mainly a tool for me, it might belong in a local app instead.

That distinction isn’t always obvious while I’m building. A personal project can start as an internal tool and later become something worth showing. I don’t need to settle that for every idea now.

Let the site grow with the work

I make decisions for the next step rather than every step after it. The website should be useful today, and I should be able to improve it as I learn what RitesDev needs.