background
While blocks are very helpful, sometimes admins believe that certain users should only be blocked on components of a project. For example, a contributor may make really great edits, but doesn't respect the universal code of conduct for talk pages. In this case, they may want to block the user for talk pages. Or, a user may know a lot about Subject A, but say profane things on Subject B. In this case, we'd want to block the contributor from subject B pages.

user story
As an admin, I need more granularity in my blocking mechanisms, so that I can help contributors add value where they're best.

requirements
Given that I'm an admin, when I am ready to make a block, then I should be able to set a sitewide or partial block, and when I select partial, I should see

• a text field to set a page-level block
• a text field to set a namespace block
• Checkboxes to upload files, move pages or files, give thanks, or create new pages
• if deselect partial block, then the fields should collapse
• if I reselect partial block, then the existing selections should be preserved

When partial block is selected, pages field, namespaces field and other related checkbox should toggle accordingly.

In this task we include the checkboxes that are shown when the partial block option is selected.

The block type field should look and feel as defined in Figma file