Flask python blueprint logic code separation
am I right your logic should be in models and service classes?
and blueprints (aka views) only a thin middleware between template and these modules?
I'm a bit confused about separation for my flask app. Users can login, post adverts and these are available to the public.
The URL structure would be something like this:

User Home - www.domain.com/user
User login - www.domain.com/user/login
User advert List - www.domain.com/user/advert
User advert add - www.domain.com/user/vacancy/add
Public Advert - www.domain.com/advert/1

The issue comes from the fact that there is advert forms and logic which is required inside and outside of the user control panel. Which of these is the most correct way of laying out my application:
Option 1:

User Blueprint (no url prefix) Contains all user related logic
Advert Blueprint (no url prefix) Contains all advert related logic,
including the user posting adverts and displaying them to the public

Option 2

User Blueprint (/user/ prefix) Contains user logic and advert logic (adding adverts from the user control panel)
Advert Blueprint (/advert/ prefix) Contains advert logic relating only to advert tasks outside of the user control panel.