I'm thinking through the structured data for our new website, and I've grinded to a halt.
In our new website, we'll have six services we offer, amongst which are Webdevelopment and Online Marketing. All of these have several subservices, for instance Webdevelopment>Front-end, Webdevelopment>Back-end, or Online Marketing>Remarketing.
I figured that, seeing as what we call services aren't really called services, entities like Webdevelopment and Webdevelopment>Front-end should be Creative Works. They're not Services as the schema might imply (delivery service, glass repair service), nor do they have set prices so they can't be Products.
My colleague disagrees, he insists that they're services because it's what we use to make the final product (like a website or a flyer).
Would it make more sense for Webdevelopment>Front-end>Product01 to be structured (with Schema.org) as
CreativeWork>CreativeWork>CreativeWork, or as
Service>Service>CreativeWork? Or should I structure it differently alltogether?
EDIT: Maybe this info will help: we're going to have one page on our website per 'service', and every 'subservice' gets another page, and the project pages too, ofcourse. Which means that if I use CreativeWorks for services, subservices, and projects, I can jump back and forth through the service hierarchy using
hasPart, and their inverses.