The writing is finished. 37 posts are written, checked against their sources and built, with 30 interactive pieces on them, and every one of them runs on the preview store where it can be read exactly as a reader would see it.
What has not happened is the move. Your own blog page still shows the theme's example collections, so none of this reaches a reader yet. Week 17 moves the posts onto your store and puts the blog back in your menu, and that is the single largest thing the week does.
Open for a fortnight, and it shaped how posts get written. It closed on the 1st of August, in the permissive direction.
The standing rule is that free materials are collected by email signup rather than sitting inside the site for anyone to take. What you agreed on the 1st is narrower and does not break it: a post may carry a callout to the free resource matching its subject, provided it leads to the signup rather than to a download.
So a post about scan planes can say there is a free reference on scan planes and send the reader to the existing signup. Nothing is given away inside a post and no second route to a download is created. That is how every one of the 37 posts is written.
Only where it fits the subject. A post with no matching free resource carries no callout rather than a generic one, because a signup box unrelated to what someone is reading makes a page feel like an advert.
Same shape every time, so the blog reads as one voice rather than a pile of articles.
Each post is written on a subject your own study guides and question bank already cover, so it draws on what you have taught rather than research from scratch. It also means every post has a product behind it.
Each post points at the paid resources nearest its subject. Someone arriving from a search lands on a page that answers them and shows where the fuller version lives.
A post whose subject has no matching resource gets listed as it comes up: an obvious subject with nothing behind it is the cheapest signal about what to build next.
Read this as the state of the work rather than a plan, because the writing part is done.
37 posts exist. Every one has been through a fact check against its sources, and 29 of them had a second round of corrections applied at the end of August, which also replaced the old mailing list links with your own signup. They are built as real pages on the preview store, not as drafts in a document, so what you see there is what a reader would get.
No count was ever promised, and that stays true for what comes next. Committing to a number gets met by writing to the number: shorter posts, thinner subjects, and pages that exist because a figure needed hitting. What was committed was that posts led the week, and they did.
Three things happen in the move. The posts go onto your store. The blog goes back into your menu, which it has been out of. And the pay and employment figures on the posts that were already live get brought up to date, because those numbers go stale on their own while the rest of a post keeps, and a reader who checks one and finds it wrong stops trusting the rest.
You asked where in Proton the blog information went. There is a folder there now, and it is a backup rather than the way in.
The blog studio on the dashboard is where the posts were written and reviewed, and it keeps a working copy of each post with its history. Once a post is live on the store, the store holds its own copy, and the studio does not write to it. Changing a live post means changing it in Shopify: Online Store, then Blog posts, open the post, make the change, Save. The studio stays useful for drafting and for review with tracked notes, and the exact paste can be prepared from the studio copy for you or for me to apply in Shopify; what it cannot do is push it to the store by itself.
If the store's own interface accepted content changes from outside, the studio copy could be synced to the live post on a schedule; the check on the 1st showed every content field refused on every credential this side holds, and that access cannot be widened from here.
Every post, in a reader you can edit in place, with your notes and the history. It saves your draft as you type; a live post changes in Shopify. It uses the same sign in as this dashboard, so if you are reading this you are already signed in to it.
Open the studio Every addressSo you are not hunting through weekly pages for the one you want. It is also linked under the title on the dashboard.
Open the links pageTwenty of them have a second, fuller draft, roughly twice the length of what is on the page. In the studio a post with one offers it beside the current text, and taking it saves the same way any other change does. You do not have to; the shorter one is the one built and checked.
Everything loads clean from here, so I need the post you were on. Send me the title and I will find it. If you spot others, the titles are all I need.
One small piece per post, belonging to the subject of that post.
A cost calculator on the degree posts, a readiness check on the exam posts, a program search, a week builder, a tracker for applications. They are in the posts already rather than sitting in a folder, so they move across with them.
Every one is tested automatically each time: that it loads, that it works with a keyboard, that it fits a phone, and that its buttons are big enough to press. 323 checks, all passing. It finds the posts by reading the blog itself rather than working from a list, so a post added later gets checked too.