sel4 / website Goto Github PK
View Code? Open in Web Editor NEWThe seL4.systems website
Home Page: https://seL4.systems
The seL4.systems website
Home Page: https://seL4.systems
https://sel4.systems/news.pml has a lot of news items now, sometime a need arises to link a specific item from the past. There seems no way to create an URL for this. My current case is linking to "13 August 2021: seL4 protects world's most secure drone from DEFCON hackers" together with a link to the presentation video now available at https://youtu.be/X9rsv4YIShY (we could add the link at the news item now).
Creating a HTML anchor manually for each news item might be the most simple solution to solve this for now. Creating an linkable anchor seems easy, just give the div
tag a unique id
made form the date-stamp
<div id="20210813" class="news-item">
13 August 2021: seL4 protects world's most secure drone from DEFCON hackers
</div>
And then https://sel4.systems/news.pml#20210813 can be used. However, there is no easy way to make this link public, the crude way would be embedding a relative link:
<div id="20210813" class="news-item">
13 August 2021: <a href="#20210813">seL4 protects world's most secure drone from DEFCON hackers</a>
</div>
or with an anchor symbol:
<div id="20210813" class="news-item">
<a href="#20210813">⚓</a>
13 August 2021: seL4 protects world's most secure drone from DEFCON hackers
</div>
We need to enable github workflows that will allow contributors and reviewers to be able to easily view the changes they would like to make to the seL4 website.
/var/www/seL4
dir within the container with whatever the PR state is.wget
to snapshot the website from the locally run serverThe link colour specified in the stylesheet is too dark, I can't easily tell where the links on a page are.
Line 6 in 2e3e4ea
(This may wait for the Information Architecture feedback first)
The Foundation substructure should only keep these pages: About, Governance (see point below), Governing board, TSC, Membership and Join.
I would merge the Governance page into the About one; I would remove the "key principles" document (outdated), just keep the Principles paragraph and have a "Two Foundation bodies" paragraph pointing to the Governing Board and the TSC (adding the currently missing link to the TSC page). I would update the About page, removing old info like the original press release.
The following other pages aren't specific to the Foundation and already appear on the main landing page: Summit, TM, Support seL4 / Funding the next big steps..., Commercial support / Endorses providers. I would therefore just remove them from under the Foundation, but we need to revisit the top menu bar do have them appear somewhere (#305).
The following 2 pages only appear under the Foundation: Jobs and Contact the Foundation. The Contact page should be removed and link to the general "Stay in touch" page. The Jobs page is out of date and should be revisited (#306)
On https://docs.sel4.systems/Hardware/ we want to have instructions on what to do if the board you want is not in the list.
Under "What we prove":
" The binary code of the ARM version of the seL4 microkernel correctly implements the behaviour described in its abstract specification and nothing more. Furthermore, the specification and the seL4 binary satisfy the classic security properties called integrity and confidentiality. "
Update the https://docs.sel4.systems/Hardware/ page to make sure it's consistent, up to date, and with an easy high-level take-away for a wider audience.
(This may wait for the Information Architecture feedback first)
Is it still appropriate to have the "Research" tab only going to TS? (other people in the community do research on seL4) and is that TS research page still up to date?
Could we merge this "More information" into the "About seL4" page?
The FAQ and Roadmap are linked to the docsite, which are part of thinking how to link better the 2 sites (#309)
There are some files that become identical under case-insensitive file systems, content/js/tinymce/LICENSE.TXT
and content/js/tinymce/license.txt
git clone [email protected]:seL4/website.git
Cloning into 'website'...
remote: Enumerating objects: 391, done.
remote: Counting objects: 100% (391/391), done.
remote: Compressing objects: 100% (296/296), done.
remote: Total 391 (delta 28), reused 391 (delta 28), pack-reused 0
Receiving objects: 100% (391/391), 19.91 MiB | 1.29 MiB/s, done.
Resolving deltas: 100% (28/28), done.
warning: the following paths have collided (e.g. case-sensitive paths
on a case-insensitive filesystem) and only one from the same
colliding group is in the working tree:
'content/js/tinymce/LICENSE.TXT'
'content/js/tinymce/license.txt'
In various pages we have a "contact us" link that goes to the general contact pages, that has all the various emails. Do we want to be more specific to which address to use for the topic where the "contact us" mention is?
Eg:
Other pages have the specific email, eg:
Having a RSS/atom feed for the ticker at https://sel4.systems/news.pml.html would be a nice-to-have.
Now that the performance page is updated regularly, it would be nice to have a graph available that shows the history of each value and link to the commit that was used to build the images that produces these.
Add news item that there is a new release with seL4 12.1, CAmkES 3.10 and CapDL 0.2.1
... so you don't have to read the source each time you want to reference an item
Navigating to the http://sel4.systems/About/Performance/ results in the following error message
Content Encoding Error
The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression.
Please contact the web site owners to inform them of this problem.
(This may wait for the Information Architecture feedback first)
The links between the seL4 website and the docsite (and github) should be improved.
Currently:
Relating to: #20
A possible solution is to switch back to pull_request_target
, and do something like suggested here: #20 (comment) - that is, figure out what the real PR SHA is, and check that out manually.
The real issue is that forks can't see any github.SECRETS
, which means the 'deploy the generated site to a git repo' doesn't work, and so we need a work around.
(This may wait for the Information Architecture feedback first)
The top menu should be
We should also revisit it once the new information architecture is set (including if we move some pages out of the Foundation's substructure #304)
(This may wait for the Information Architecture feedback first)
The titles on the landing page, top menu and individual pages should be made consistent. It's more confusing than it adds value to have them different.
For instance:
There should be an RSS/atom feed for news, this allows monitoring automation then.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.