It’s been a while since the last blog post about the XML Sitemaps feature project. Today I’d like to summarize the developments since last month, and also post the agenda for our upcoming meeting.
- Version 3.0 (#181)
A pull request has been opened to add the change log for our next release, which includes a good amount of improvements over the last version. The goal is for this to be one of the last releases before we put our efforts into a merge proposal.
Most notable changes: important refactorings, rewrite rule fixes, removal of
- Custom elements in sitemap (#151)
There is no consensus yet about what the API An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. for adding custom elements (beyond
priority) could look like, especially when dealing with custom namespaces.
- Custom elements in stylesheet (#152)
There is still an open PR that tries to make the XSLT stylesheet more dynamic so it automatically displays sitemap elements added by plugins. That means there’s some overlap with the issue mentioned above.
Interesting side affect: the PR proposes a new
esc_xml() function that might be worth looking into.
- Road towards WordPress core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. (#164)
We’re full steam ahead on improving the source code so it better aligns with WordPress core standards, as well as getting feedback from various core teams on the plugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party (i.e. polyglots, accessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility), docs). Also, there is now a Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticket Created for both bug reports and feature development on the bug tracker. to reference! See #50117.
Agenda: May 12th
The next meeting will be held on Tuesday, May 12th at 16.00 CEST.
Items on the agenda so far:
- Version 3.0 (#181)
- Custom elements
- Currently open issues and pull requests. Including:
- Removing trailing slashes on URLs (#134)
- Sanitizing object subtypes for use in URLs (#166)
- Adding filter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. for
WP_Query args (#131) (needs owner)
- Current roadmap status
- Open floor
Want to add anything to the above? Please leave a comment here or reach out on Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..
This meeting is held in the #core-sitemaps channel. To join the meeting, you’ll need an account on the Making WordPress Slack.