WordPress Versions archive template

[carl-alberto]

No description provided.

[carl-alberto]

This will be a separate template file that have to call the related child terms for the major release term. Eg. 4.5 page has to call get_terms to get 4.5.1 4.5.2 etc

@Kenshino do you have sample posts that contains those terms that you mentioned?

[Kenshino]

WordPress Versions have already been migrated.

Do you mean those when you said sample posts?

[atachibana]

WordPress Versions Archive is the summary page of version information.
Already HelpHub defines custom post type for version document

Custom Post Type page
https://wp-helphub.com/wp-admin/edit.php?post_type=helphub_version

Example document.
https://wp-helphub.com/wordpress-version/version-4-5-2/

This issue expects summary pages that is similar to
https://codex.wordpress.org/WordPress_Versions

I will take this issue with help of #126 Archive.

[atachibana]

Version archive design.

• Ordered by Major version from New to Old. (4.8 -> 4.7 -> 4.6 ...)
• In each Major version, ordered by minor version from old to New (4.8.1 -> 4.8.2 -> 4.8.3 ...)

[psaikali]

I'd be happy to help with that.

A couple of questions, to be sure the way I see this is the good way :

1. We need to have 2 more meta fields for Changelog and Blog links, as we don't have them yet, is that correct ?
   

2. I'd rather work in the archive-helphub_version.php template file, as it feels "more native" to do so. Should we just hardcode the intro text in the template itself ?
   
   Otherwise we could have a specific page template for that page, and a metabox/field for the intro text, but I feel that this kind of flexibility is not needed right now ?

[atachibana]

@psaikali
Thank you for the support and your suggestions are definitely the same ones that I have :-)

1. Yes. We should have additional fields as you say.

2. I think we can hard code those statement in the template. As you say, no other parts will use it.

[atachibana]

@psaikali
As John said in the HelpHub meeting, I close this issue and opened new issue #246 under the Epic #249.
Please take the #246. Thank you.