While you can develop site architecture (the structure and organization of a website) without considering how it will be built on the backend, it’s generally not advisable for anything beyond the most basic, static websites. 

Here’s why:

• Functionality: The backend is responsible for processing data, managing user interactions, handling payments, and much more. If you design your site architecture without considering these backend functionalities, you might create a structure that’s difficult or even impossible to manage.
• Performance: Backend architecture significantly impacts website speed and responsiveness. If you design a complex site structure without considering backend efficiency, you could end up with a slow and frustrating user experience.
• Scalability: Your site is built to grow, so how your content management system’s backend is structured can determine how well your site can handle increased traffic and data. A site architecture designed without scalability in mind might lead to problems as your website grows.
• Security: Backend security measures, like user authentication and data encryption, are crucial. Designing the site architecture without considering security could make it vulnerable to attacks. 

In essence, the front-end (what users see) and back-end (what powers the site) are interconnected. Ignoring the backend during site architecture planning can lead to challenges and limitations in building a functional, performant, scalable, and secure website. 

For more complex websites, consider a decoupled or headless architecture where the front-end and back-end are separated, but still communicate via APIs. This offers flexibility and scalability, but requires careful planning and skilled backend development.