This document discusses using WordPress Multisite as a development environment. Some key benefits include having a single database and location for plugins/themes, allowing for rapid deployment of new sites. To set it up, some code is added to wp-config.php and .htaccess to enable Multisite and handle subdomains/subdirectories. New sites can then be easily created and each functions independently while sharing plugins/themes network-wide. The process for exporting and importing sites to a live location is also outlined.

1. Using WordPress Multi Site as a Development Environment Jeff McNear plasterdog.com jeff@plasterdog.com @plasterdog 847/849-7060

3. Hosted at a controlled location

4. Control over user permissions

5. Quick deployment & modification

7. The activated plugins

8. The actual content portion of the siteAll other aspects can easily be shared across a Multi Site deployment

10. Can be activated in four steps

11. Fast deployment of new sites

12. Single database

13. Single location for themes & plugins

15. Sub directory (multisiteURL/sub) – scheme for local or shared hosting

16. Verify mod_Rewrite is active

17. Best with fresh install

19. Delete sample page

20. Delete sample comments

21. Delete sample links

22. Verify site name & slogan

23. Set permalinks scheme

24. Set screen preferences

27. If you are in a VPS or dedicated hosting environment, you are given the option to select sites as sub-directories or sub-domains. If you are working locally or on a shared host, this selection has been made for you.

29. Insert additional code into the wp-config.php file

30. Insert a piece of code into the (root) .htaccess file(code is dynamically generated based on install)

32. The purpose of the blogs_dir insertion is to provide a location for the media library structure. A folder for each site is dynamically created.

34. Plugin upload

35. Updates

36. Site creation

37. Some aspects of user administrationEverything else is controlled on a site by site basis!

38. A single complaint: The navigation to the network admin panel is not immediately evident!

39. Themes are uploaded into the multisite “root” and must be “network enabled” before they can be applied to a site

40. Plugins are also uploaded into the “root” and can also be “network activated” but can be selectively activated on a site by site basis:

41. You now have a completely stable development environment for multiple individual wordpress sites. Any network enabled theme can be used. Any uploaded plugin can be accessed.

42. To create a new site: => Sites => Add New => Create a New Site

44. Access site controls via “root”:=> Sites => All Sites => Select “Dashboard” for desired site Access controls directly: rootURL/sub/wp-admin

46. Only those plugins inserted via the Network admin can be used

48. Additional option in multisite: “Add existing user”

49. Once a user exists in the structure, that user can be associated with multiple sites – and with different permissions

51. Make note of plugins used

53. Export

54. All Content

57. Upload and activate developed theme

59. Import

60. Navigate to saved .xml file

61. Import/absorb author(s)

64. Page (and post) template assignments

65. Media library contents

66. Categories and their definitions

67. Created menus

69. Site title & slogan

70. “Blogroll” inserted links

71. Text widgets inserted via widget panel

73. A single place for updates

74. Centralized plugin depository

75. Ability to apply certain plugins by default

76. Rapid site deployment

77. Perfect location for site archives