![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
Changes between Version 1 and Version 2 of Ticket #1810, comment 7
- Timestamp:
- 08/17/2016 04:35:43 AM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #1810, comment 7
v1 v2 3 3 You would then expose it as a `Readme\Parser::$faq[ $question ] => $answer` property on the object, `CLI\Parser` would then be responsible for storing it however you wanted, which could be a `<dl>` in the post content, or as custom meta fields (as we do with screenshots, etc). 4 4 5 Whichever way you approach it, it's worth remembering that not all FAQ's are using `<h4>`'s some use `<h3>` (`members`) and others use `<strong>` (`share-this`), some include free form data before the headings ( for example,`wp-user-avatar`), others (`cookie-notice`) just include a paragraph, and then there's those who use free-form "invalid" formats (`wpremote` &`jquery-updater`).5 Whichever way you approach it, it's worth remembering that not all FAQ's are using `<h4>`'s some use `<h3>` (`members`) and others use `<strong>` (`share-this`), some include free form data before the headings (`wp-user-avatar`), others (`cookie-notice`) just include a paragraph, and then there's those who use free-form "invalid" formats (`wpremote` &`jquery-updater`). 6 6 7 7 Those plugins were just me opening a bunch of random plugins in the database and looking at their post_content, I'd say it was a 50% hit rate on "edge cases" while looking for examples. Ignoring, truncating, or reformatting plugins like this is fine, we just need to plan that out before we parse stuff.
