3. Before WordPress Era
• One tunnel for posting
• Multi faces, design and feature
• Struggling with SEO
• Hard to be creative or cutting edge
– Limited resources
– Limited sources
2017 wcJkt - Wigid Triyadi 3
6. The requirement
• A.S.A.P
• Multiple authors
• Easy for author to create a news / posts
Also
• Possibility to be customized
• Easy to update
– Security issue
62017 wcJkt - Wigid Triyadi
7. First WordPress!
• As a news based
website
• Multi tunnel posting
• Conservative approach
– Tagging with category
and tags only
• Multi language
72017 wcJkt - Wigid Triyadi
http://blog.cifor.org
8. WordPress!
• Cost
– Started from free
• Ease of use
– Author focus on the atricles
• SEO Friendly
– Support SEO tag minimum
• Support from the community
• Scalable!
– Sky is the limit
82017 wcJkt - Wigid Triyadi
11. First Multisite
• Used on our biggest annual event website
• As subfolder
• Custom post and taxonomy
• Relational post
112017 wcJkt - Wigid Triyadi
14. Why Multisite?
• Single installation
• Single user dashboard
• Isolated backend
• Site branding will be easily achieved
• Share plugins, themes, widgets and data
2017 wcJkt - Wigid Triyadi 14
15. On our outlets
• Research output
– Publication Books, Journals
– Videos -> YouTube
– Photos -> Flickr
– Presentations - > SlideShare
– News -> Articles, blogs
• Projects and research updates
152017 wcJkt - Wigid Triyadi
18. Implementation [cont’d]
• Custom API to store
assets data
• Sharing assets across
sites
• Widget and sidebar
optimization
• Events page builder
• 15 sites and counting
• Search results and
search performances
• Windows based server
– Site performance
– Plugins compatibility
182017 wcJkt - Wigid Triyadi
21. Dos and don’ts
• Network that share one
brand
– University, Government
Events or Community
with different locations.
• Share same Features
• FTP users on specific
site
• Multisite as staging /
development site
• Multisite for different
client / organization
• Users need to install
plugins or themes
• Shared hosting
212017 wcJkt - Wigid Triyadi
Windows MCMS
Classic ASP based website
Migrasi ke TYPO3
Beragam antarmuka
2010
At that time, all the content update had to go to one team, HTML knowledge is require to create a post
We have multiple layout and functionality on each project sites, project sites need to displaying news/latest info on particular topic/project
Started from free
Focus on the article
SEO and XML that Supported by from plugins
Well documented codex
2013
Single site vs multisite
How to post is the same
Plugins and themes can be network activated, cache – seo - jetpack
DB is the same, different table
Option:
Subdomain or subfolder
9 sites is now running there
Within unix enviroment
Branding goals Archived!
That challenge us to have it on Windows
Kembali ke CIFOR,
Single installation meaning once update will apply to all
Maintenance cost reduced
Single user access, bayangkan bila website anda memiliki beberapa orang author, akan jauh lebih mudah bagi anda dan author untuk melakukan setup dan mengingat satu login dibandingkan berada di system yang berbeda
Isolated backend from data perspective and user persective
Domain moving?
Windows based server
Sharing data and functionality
Sky is the limit
WordPress lesson learned
Alternate using page or custom post type
Totally different installation
Multitenancy basically share themes folder ataupun plugin menggunakan windows shorcut atau symlink
Within current approach, the meta information are save as custom field, instead we can compress the db usage by implementing API to save DB size