New home for all XenForo documentation

Although we still have a little way to go before our vision is fully complete, the first phase of our documentation overhaul is now live!

Previously our manual and developer documentation were stored in two separate sites, powered by MkDocs, and our REST API endpoint documentation was in a page node, right here on this forum!

Now all of the documentation is in one place, docs.xenforo.com, and you can navigate between the Manual, Developers and API documentation from the top navigation.

It now includes improved search powered by Algolia and features much improved REST API documentation including code samples for many common languages.

For the most part the content remains the same as it was, but in the future we will be reorganising, rewriting and extending our documentation to ensure it becomes a valuable resource for new and old customers alike.

All of our documentation is now fully open source (including the manual) and hosted on GitHub! We appreciate the help so far from contributions, especially kind folks such as @QuackieMackie, towards extending the developer documentation. If you have spotted something missing, outdated, or just in need of any sort of improvement, post an Issue or submit a Pull Request and we'll be excited to get it merged.

 

[DigitalME]

@Max Fridman an official WordPress bridge would also be very useful, given that approximately 50% of existing websites in the world are built with WordPress, but obviously there will be the usual response that "these are customizations that are of little interest"...

I agree, we had to make our own.

 

[BikeGremlin]

@Max Fridman an official WordPress bridge would also be very useful, given that approximately 50% of existing websites in the world are built with WordPress, but obviously there will be the usual response that "these are customizations that are of little interest"...

That 50% probably counts all the one-page abandoned stuff as well (not sure about the free hosted Wordpress.com sites - I would not be surprised if those too count as one each).

That aside, how many of those want and need to connect Wordpress to Xenforo?

Every extra supported feature takes time and effort. Those are both costly and limited.

Be careful what you wish for.

 

[Ricsca]

That 50% probably counts all the one-page abandoned stuff as well (not sure about the free hosted Wordpress.com sites - I would not be surprised if those too count as one each).

That aside, how many of those want and need to connect Wordpress to Xenforo?

Every extra supported feature takes time and effort. Those are both costly and limited.

Be careful what you wish for.

Of course, not all 50% of the world's WordPress sites are active, and it's also true that many of the active ones aren't interested in adding a Xenforo forum. However, it's also true that very small percentages of the approximately 1 billion WordPress sites (source: chatgpt) are still huge numbers.
Since Xenforo wants to remain a forum only, it would be very important and useful for them to create a bridge for WordPress so that they could delegate the site to another CMS that then has thousands of other active plugins and therefore indirectly add functionality to the forum as well.
The first thing that comes to mind is a newsletter system, which on Xenforo is very basic, while there are countless excellent plugins for WordPress.
Forums have been hard to attract new users for many years, so either they try to evolve or...

 

[Digital Doctor]

This is good progress.

Ideally each page / section would have an associated discussion thread.
Just like the Resource Manager.

Hopefully when <<something something at xenforo>> resolves, and tiptap comes, hopefully a Xenforo attempt at true Pages will be the result. TipTap looks like a great editor for Pages. My dream is real time collaborative editing.

 

[Chris D]

The documentation will never itself be used as a discussion platform. But it is collaborative already. The documentation is hosted on GitHub at https://github.com/xenforo-ltd/docs, can be edited, or issues discussed via the Issues section of the repo.