0 / 20 answered

1. 1. What is the main purpose of Lubinik?

   What is the main purpose of Lubinik?

   Modify WordPress core Provide a reusable WordPress foundation across projects Replace PHP with a page builder Store every site in one database
   Hint

   Use Lubinik responsibility boundaries and documented extension contracts.

2. 2. What is the primary responsibility of the Lubinik parent theme?

   What is the primary responsibility of the Lubinik parent theme?

   Every addon data model A project-specific booking domain Generic site structure and presentation mechanics Remote deployment credentials
   Hint

   Use Lubinik responsibility boundaries and documented extension contracts.

3. 3. What is the primary responsibility of the Lubinik core plugin?

   What is the primary responsibility of the Lubinik core plugin?

   A single accommodation catalog Child-theme color choices Shared domain-agnostic plugin and addon infrastructure One client brand identity
   Hint

   Use Lubinik responsibility boundaries and documented extension contracts.

4. 4. What should a Lubinik addon normally own?

   What should a Lubinik addon normally own?

   All parent-theme templates The identity of every site A structured domain model and its domain behavior WordPress core updates
   Hint

   Use Lubinik responsibility boundaries and documented extension contracts.

5. 5. What should a Lubinik child theme normally own?

   What should a Lubinik child theme normally own?

   Shared addon registry infrastructure Site identity and project-specific presentation WordPress database access Every reusable support engine
   Hint

   Use Lubinik responsibility boundaries and documented extension contracts.

6. 6. What should a reusable support plugin contain?

   What should a reusable support plugin contain?

   Hard-coded rules for every future site The reusable engine, with project rules supplied through configuration One client secret committed in JSON A copy of every addon
   Hint

   Use Lubinik responsibility boundaries and documented extension contracts.

7. 7. Does every Lubinik site require a domain addon?

   Does every Lubinik site require a domain addon?

   No, a small site can use the parent theme and core without one Yes, WordPress cannot load otherwise No, because addons are deprecated Yes, the parent theme is an addon
   Hint

   Use Lubinik responsibility boundaries and documented extension contracts.

8. 8. Which requirement most strongly suggests creating an addon?

   Which requirement most strongly suggests creating an addon?

   Repeatable domain entities with dedicated fields and behavior Changing the logo color Editing one paragraph Adding one CSS margin
   Hint

   Use Lubinik responsibility boundaries and documented extension contracts.

9. 9. Where should a proven domain-agnostic facility used by several addons move?

   Where should a proven domain-agnostic facility used by several addons move?

   Into a page title Into shared core infrastructure Into one client child theme Into WordPress core files
   Hint

   Use Lubinik responsibility boundaries and documented extension contracts.

10. 10. Should the first project-specific need immediately be added to the core plugin?

    Should the first project-specific need immediately be added to the core plugin?

    Yes, if the file is small No, core cannot be extended No, prove that the abstraction is reusable first Yes, core must contain all code
    Hint

    Use Lubinik responsibility boundaries and documented extension contracts.

11. 11. Who should own the entity-specific query and markup behind a domain list?

    Who should own the entity-specific query and markup behind a domain list?

    An unrelated child theme The database server WordPress core The addon that defines the entity
    Hint

    Use Lubinik responsibility boundaries and documented extension contracts.

12. 12. A change only expresses one site’s visual identity. Where does it belong?

    A change only expresses one site’s visual identity. Where does it belong?

    The child theme wp-admin core files Every addon The core plugin
    Hint

    Use Lubinik responsibility boundaries and documented extension contracts.

13. 13. Several addons need the same registry and renderer. Where should those live?

    Several addons need the same registry and renderer. Where should those live?

    Each child theme independently The core plugin One page template A media attachment
    Hint

    Use Lubinik responsibility boundaries and documented extension contracts.

14. 14. Where should accommodation booking fields live?

    Where should accommodation booking fields live?

    A universal child-theme stylesheet The generic parent theme A booking or BnB addon The core plugin settings screen
    Hint

    Use Lubinik responsibility boundaries and documented extension contracts.

15. 15. Who should normally provide project-specific rules to a support engine?

    Who should normally provide project-specific rules to a support engine?

    The WordPress update server The addon, theme, or project that owns the behavior An unrelated plugin The browser cache
    Hint

    Use Lubinik responsibility boundaries and documented extension contracts.

16. 16. Where should API secrets be stored?

    Where should API secrets be stored?

    Protected runtime configuration, never committed public JSON A theme screenshot A public manifest A frontend data attribute
    Hint

    Use Lubinik responsibility boundaries and documented extension contracts.

17. 17. What should happen before changing a Lubinik architectural boundary?

    What should happen before changing a Lubinik architectural boundary?

    Copy a legacy site blindly Edit production first Read the relevant repository documentation and loaded implementation Create a parallel loader immediately
    Hint

    Use Lubinik responsibility boundaries and documented extension contracts.

18. 18. What does scaffolding alone prove?

    What does scaffolding alone prove?

    The expected files were generated, not that the feature works end to end The database is migrated All integrations are tested The feature is production-confirmed
    Hint

    Use Lubinik responsibility boundaries and documented extension contracts.

19. 19. A legacy child theme contains domain logic. Is that automatically the modern convention?

    A legacy child theme contains domain logic. Is that automatically the modern convention?

    No, legacy files can never run Yes, child themes own all domains No, inspect current documentation and architecture before copying it Yes, all existing code is canonical
    Hint

    Use Lubinik responsibility boundaries and documented extension contracts.

20. 20. Which summary best describes the Lubinik split?

    Which summary best describes the Lubinik split?

    Core for colors, child theme for databases, addon for WordPress updates All layers should duplicate each other Theme for generic presentation, core for shared infrastructure, addon for domain, child theme for site identity Parent theme for every business rule, core for logos
    Hint

    Use Lubinik responsibility boundaries and documented extension contracts.