Create custom post type

Create a Projects custom post type for the portfolio so I can separate case studies from blog posts. Include support for title, editor, featured image, excerpt, custom fields for client, budget, and completion date, and enable the admin list to show client and date columns. Make sure permalinks use /projects/slug and add the post type to the main site search. Walk me through how to register and where to put the code so it survives theme updates.

Before I add this custom post type, make the content reviewer’s life easier. Propose field names and an editor layout that keeps the essential approval info — client, outcome, project URL — up top, hides rarely used fields, and makes featured image selection mandatory for listing cards. Flag any capabilities that could cause content to be accidentally published and suggest user roles to restrict that.

I’ve just registered a Projects post type so case studies are separate, and now authors are publishing incomplete projects by mistake. I own the content workflow and the head of creative is furious. I’m unsure whether the problem is capability settings, confusing editor layout, or training. What is the most likely cause and the fastest fix so we stop live half-baked projects while keeping publishing easy for trusted authors?

Every client gets a slightly different custom post type for the same concept, and that fragments exports, plugins, and training. I manage multiple agency sites and want to stop reinventing the same post type every time. Which two practices will standardize creation so types are reusable across sites and simple for non-devs to use? Give steps and a short policy I can give account managers.