|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Doc Bug #73698 It's hard to find standard PHP library functions in Function Reference
Submitted: 2016-12-09 07:56 UTC Modified: 2018-06-24 16:31 UTC
From: Assigned:
Status: Open Package: Documentation problem
PHP Version: Irrelevant OS:
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
Block user comment
Status: Assign to:
Bug Type:
New email:
PHP Version: OS:


 [2016-12-09 07:56 UTC]

I started a non-biding discussion on /r/php regarding ways we could improve PHP Manual experience. One of complaints (which I also heard before) is that it's hard to find PHP standard library functions.

I think that I know the reasoning behind that. Moreover, I think is valid. There is hard to define what exactly "PHP Standard Library" is (I'm talking about SPL). One version of PHP can have `php-src/ext/calendar/` bundled and other can not. Extensions can also be excluded when compiling etc, etc.

But let's focus on `php-src/ext/standard` for now. Those are basic functions which are always available, but finding them in the manual using TOC's is rather difficult.

Let's take `file_exists()` as an example - pretty basic function. (or even -> Documentation -> English) -> Function Reference -> File System Related Extensions -> Filesystem -> Filesystem Functions -> file_exists()

Not only it's very long way to get there, I think that most of these people is lost on "File System Related Extensions". I doubt they treat `file_extists()` as any kind of an extension (once again, I do understand, why we treat it as such in terms of manual structure).

So, what I would propose is either:

1) Restructure phpdoc/reference/ to contain /standard/ directory, then divided into /strings/, /array/, /filesystem/ etc. (what exactly should be included there is another part of discussion, I think).

That sounds good, but I'm not even sure whether our current build system would allow that. It's all about xml:id's and their hierarchy, what defines our TOC's, right?

2) Don't change the hierarchy and structure at all but somehow hardcode URL's to them on top of "Function Reference". Something like:

Function Reference
- Standard library
-- Arrays
-- Filesystem
-- Strings
- Affecting PHP's Behaviour
- Audio Formats Manipulation
- Authentication Services

I'm willing to take care of implementing that, but I'd like to know opinions of more experienced Doc Team's members.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2018-06-24 16:31 UTC]
> It's all about xml:id's and their hierarchy, what defines our
> TOC's, right?

Well, the structure is defined by[1], and could be
changed (or perhaps augmented).

[1] <>
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Sun Jul 14 14:01:27 2024 UTC