You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we create a custom post type, we can have the swagpaths appear under its own page and have its own menu item in the admin menu, rather than being mixed in with the pages. We would also be able to eventually customize the UI, so we can make it "swag specific". E.g. rather than manually entering shortcodes we could do it via a button (add swagifact), and rather than manually entering the "requires" and "provides" custom fields, this could also be done via a UI. This would make it easier to create and manage swagpath, and would ensure that it is done correct, so that nothing ends up outside the [course] shortcode for example.
But the first step would be to create a custom page type. There is information on how to create custom post types here:
It doesn't go into depth when it comes to explaining how to create and customize the UI. Actually there is no information about that at all, so some more research is needed.
The text was updated successfully, but these errors were encountered:
If we create a custom post type, we can have the swagpaths appear under its own page and have its own menu item in the admin menu, rather than being mixed in with the pages. We would also be able to eventually customize the UI, so we can make it "swag specific". E.g. rather than manually entering shortcodes we could do it via a button (add swagifact), and rather than manually entering the "requires" and "provides" custom fields, this could also be done via a UI. This would make it easier to create and manage swagpath, and would ensure that it is done correct, so that nothing ends up outside the [course] shortcode for example.
But the first step would be to create a custom page type. There is information on how to create custom post types here:
https://codex.wordpress.org/Post_Types
It doesn't go into depth when it comes to explaining how to create and customize the UI. Actually there is no information about that at all, so some more research is needed.
The text was updated successfully, but these errors were encountered: