-
Notifications
You must be signed in to change notification settings - Fork 6
Open
Description
After spending some time going through the new website, I've some thoughts:
- I think FAQs w/o answers (e.g., in the "relation to ..." section) should be answered or removed from this site;
- they can remain in the TC-Ops repo on GH and answers developed there.
- Need consider balance of content between TC ops and website;
- some things (FAQ) on TC ops might just become links to website, unless we have TC FAQs on the website and internal operations FAQ in the repo
- TC FAQs with answers still in development could remain in TC Ops
Cycle time on the front page banner seems a bit too fast(disabled)- Should methodically check links to externals and
- (i) make sure they work and
- (ii) ensure their content is up-to-date, if ours (particularly the TC and SC pages at OASIS)
- Do we need legend entries for the red and blue arrows on the front page graphic?
- Is it worth turning projects into links on the "What is OASIS?" page
- On the OpenC2 In The News (OC2ITN) page:
- entries w/o links need to be updated or purged; mostly meaningless w/o a link
- All three specs were originally published July 2019, but not all are shown (announcement for all is shown);
- should point to latest OASIS-published versions (and only those)
- should have an entry for the inaugural TC meeting in June 2017
- Generic entries like "Rochester Security Summit" would benefit from more meaningful labels; in general would rather link to presentation videos than slide if available
- Should have entries for F2F meetings (maybe), January 2020 plug fest (definitely)
- Should scrub LinkedIn for openc2-related postings that can be added
Can we compress a bit vertically?(adjusted)Does the left-right placement have to be edited manually if changes are made that affect that?(L/R removed)
From a process perspective, we need to capture how to update various components of the website. (in the updated README.md)
Metadata
Metadata
Assignees
Labels
No labels