Right - your three-minute warning. Just enough time to grab a cuppa' and get comfortable before @GavinWilliamson makes his announcement on replacing GCSE and A-level exams this year
We're all ready for @GavinWilliamson's statement (due at 1pm but the PM is running late a little bit). We'll be tweeting updates. Here's a taster of what's potentially on the menu ... https://t.co/Et78NTDQGq
— Schools Week (@SchoolsWeek) January 6, 2021
Ofsted will inspect schools where it has concerns
However details will need to be 'fine tuned'.
Williamson adds: 'Testing is going to be the centre of our plan to return schools back to the classroom as soon as possible'
And that's that (well, on to Qs now)
She says she wanted exams to go ahead, but said a Plan B had to be in place.
Also 'failed to show leadership' on BTECs - leaving it up to schools
Ofqual will launch a "detailed" consultation on the plans next week. It will run for two weeks.
More from Education
Chicago Public Schools are supposed to open for some special needs and pre-K students Monday
The Chicago Teachers Union is now threatening to refuse to return to work in person.
https://t.co/MgDgNe6REj
Meanwhile
https://t.co/FIij8J3r7z
Dr. Fauci: "The default position should be to try as best as possible within reason to keep the children in school or to get them back to school [...] if you look at the data the spread among children and from children is not really big at
UNICEF: "Data from 191 countries shows no consistent link between reopening schools and increased rates of coronavirus
The Chicago Teachers Union is now threatening to refuse to return to work in person.
https://t.co/MgDgNe6REj
Meanwhile
https://t.co/FIij8J3r7z
Dr. Fauci: "The default position should be to try as best as possible within reason to keep the children in school or to get them back to school [...] if you look at the data the spread among children and from children is not really big at
UNICEF: "Data from 191 countries shows no consistent link between reopening schools and increased rates of coronavirus
You May Also Like
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.