WordPress.org

Make WordPress Core

Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#29835 closed enhancement (wontfix)

Remove 'wp-' prefix from WordPress files

Reported by: jasdeepharibhajan Owned by:
Milestone: Priority: normal
Severity: normal Version: 4.1
Component: General Keywords:
Focuses: Cc:

Description

As a heavy user of WordPress I can say that the 'wp-' prefix slows me down a lot when trying to find, navigate and modify files and directories via Terminal/SSH.

As a user I really see it as an unnecessary prefix which only serves to make the files and folders more verbose than they need to be. I know the install is WordPress and don't need to be constantly reminded in every file I open.

I think removing the prefix will help make WordPress cleaner and easier to navigate, even though it may be a breaking change (which would have been ideal to introduce into the 4.x family)

This change could also apply to the WordPress API which has a tendency to use the wp_ prefix for classes and functions, however that is a separate discussion.

Attachments (2)

current.png (31.2 KB) - added by jasdeepharibhajan 6 years ago.
Current dir/file structure of WordPress root
proposed.png (29.3 KB) - added by jasdeepharibhajan 6 years ago.
Proposed dir/file structure of WordPress root

Download all attachments as: .zip

Change History (7)

#1 @SergeyBiryukov
6 years ago

  • Focuses accessibility removed

#2 @tmoorewp
6 years ago

  • Resolution set to wontfix
  • Status changed from new to closed

Hi @jasdeepharibhajan! I'd argue for keeping the wp- prefix. In cases where maintainers have WordPress installed alongside another system (ex. an old, static HTML site), it's less likely the maintainer will delete a necessary file.

#3 @SergeyBiryukov
6 years ago

  • Milestone Awaiting Review deleted

#4 @nacin
6 years ago

It should be noted that very few files actually start with wp- — the exceptions are the few remaining files at the root, and the three directories. Hopefully you are always modifying stuff inside wp-content, in which case you can relocate it if you want. http://codex.wordpress.org/Determining_Plugin_and_Content_Directories

@jasdeepharibhajan
6 years ago

Current dir/file structure of WordPress root

@jasdeepharibhajan
6 years ago

Proposed dir/file structure of WordPress root

#5 @jasdeepharibhajan
6 years ago

Hi @tmoorewp! I do agree there is a huge possibility of conflicts with existing systems occurring if this rename was to happen, but this is why this would be communicated as a breaking change.

@nacin - Yes, there's only a few left at the root. It tends to be when modifying wp-config.php and navigating to wp-content which is more of a hassle than it perhaps should be.

Also the reason for my ticket was more aesthetic - just look at the current vs. proposed screenshots - looks way more beautiful to me ;)

Last edited 6 years ago by jasdeepharibhajan (previous) (diff)
Note: See TracTickets for help on using tickets.