Why new “Section” concept and menu problems
-
Why did you choose to create new content “sections” arbitrarily without introducing a new post type or taxonomy?
It seems to fly in the face of Word Press ideals to introduce a new container in an official theme and then to auto-populate exactly 4 of those containers with arbbitrary content.
But what’s weird is that you have “Home”, “About”, “Services”, “Something” as your content sections, but no contact page. Though you can scroll to the contact page on the static home page.
Not only that, but the menu items are done incorrectly, imo. You have services in the menu, and a services section, clicking the menu should scroll to the section. Plus as you scroll through each section, the related menu item should indicate that it’s the active section. The additional CSS field in customizer just hasn’t worked for me yet and the site-logo routine requires cropping which doesn’t work for SVG elements.
Wouldn’t it have been much better to create a custom post type that extended the Page prototype and allow people to set their static landing page to your new “sections” page that would actually act a lot like a sections archive by listing all of the sections in order?
Then, if I wanted to create a new “section” element for my static home page, I could. A new menu item would be created, a new content section would be added, the bg image and related content would be determined in the section post-type meta and it would all look and feel very WordPress.
I am sure you have spent a lot of time on this theme and it looks great. I was just wondering why the new paradigm and content types?
- The topic ‘Why new “Section” concept and menu problems’ is closed to new replies.