On 15/07/16 09:56, Robbie Gemmell wrote:
On 15 July 2016 at 09:16, Justin Ross <[email protected]> wrote:
I've been working with the security pages recently, and there are two
things I propose.
First, I'd like to simplify the way we include the full CVE content.
Instead of embedding it in the CVE table as a show/hide element, I'd like
to link out to an independent page. I think this will make it a little
easier to author, avoid what will become a giant page, and give the CVE its
own URL.
Under this plan, the tables would remain as they are now, but the full CVE
would be hosted at a standard location. The table would simply link to the
CVE page.
input/cves/CVE-2016-9999.md
output/cves/CVE-2016-9999.html
Second, a small thing. I will add links from the component pages to their
contained security pages. Right now you have to navigate from the
top-level security page.
Sounds reasonable to me.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
Fine by me.
In this case, I think it is worth considering to change the code to use
markdown tables instead of embedded html.
I originally used embedded html because markdown tables are horrendous with
large tables but with the proposed change they should become quite simple
and small, I guess.
Kind Regards,
Lorenz
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
