I thought I'd just briefly lay out what I do so people don't have to go to the link to my blog post in the question. The packages for all this junk are here, here, and here. Look for the things with Pelican and Py starting their names and the WebSiteDeploy function. The autodoc pages are here, here and here

###Step 1: pelican

I wrote a venv wrapper, installed pelican using that via pip, setup up a Mathematica palette to handle making new sites and posts, made a theme, etc.

###Step 2: Notebook to Markdown

Then I wrote a Notebook to Markdown converter because pelican can handle Markdown. Basically all complex box forms get rasterized. Math forms will be included once I finally get around to writing something about discrete variable representation and need them. Pre-rasterization future file names are checked against existing ones to avoid unnecessary rasterize calls.

###Step 3: Site Deployment

Using that same venv wrapped I call pelican's build process, then deploy the new content using WebSiteDeploy

###Step 4: Palettes / Stylesheets

I also built out a stylesheet that also saves to Markdown when a standard {"MenuCommand", "Save"} is called and a palette for the build processes, new file making, stuff finding, etc.

It's overkill and with a bit of work C.E.'s version is clearly a better way to do the same in the future. But it's good to have out here, I think.

I thought I'd just briefly lay out what I do so people don't have to go to the link to my blog post in the question. The packages for all this junk are here, here, and here. Look for the things with Pelican and Py starting their names and the WebSiteDeploy function. The autodoc pages are here, here and here

Step 1: pelican

I wrote a venv wrapper, installed pelican using that via pip, setup up a Mathematica palette to handle making new sites and posts, made a theme, etc.

Step 2: Notebook to Markdown

Then I wrote a Notebook to Markdown converter because pelican can handle Markdown. Basically all complex box forms get rasterized. Math forms will be included once I finally get around to writing something about discrete variable representation and need them. Pre-rasterization future file names are checked against existing ones to avoid unnecessary rasterize calls.

Step 3: Site Deployment

Using that same venv wrapped I call pelican's build process, then deploy the new content using WebSiteDeploy

Step 4: Palettes / Stylesheets

I also built out a stylesheet that also saves to Markdown when a standard {"MenuCommand", "Save"} is called and a palette for the build processes, new file making, stuff finding, etc.

It's overkill and with a bit of work C.E.'s version is clearly a better way to do the same in the future. But it's good to have out here, I think.

I thought I'd just briefly lay out what I do so people don't have to go to the link to my blog post in the question. The packages for all this junk are here, here, and here. Look for the things with Pelican and Py starting their names and the WebSiteDeploy function. The autodoc pages are here, here and here

###Step 1: pelican

I wrote a venv wrapper, installed pelican using that via pip, setup up a Mathematica palette to handle making new sites and posts, made a theme, etc.

###Step 2: Notebook to Markdown

Then I wrote a Notebook to Markdown converter because pelican can handle Markdown. Basically all complex box forms get rasterized. Math forms will be included once I finally get around to writing something about discrete variable representation and need them. Pre-rasterization future file names are checked against existing ones to avoid unnecessary rasterize calls.

###Step 3: Site Deployment

Using that same venv wrapped I call pelican's build process, then deploy the new content using WebSiteDeploy

###Step 4: Palettes / Stylesheets

I also built out a stylesheet that also saves to Markdown when a standard {"MenuCommand", "Save"} is called and a palette for the build processes, new file making, stuff finding, etc.

It's overkill and with a bit of work C.E.'s version is clearly a better way to do the same in the future. But it's good to have out here, I think.

I thought I'd just briefly lay out what I do so people don't have to go to the link to my blog post in the question. The packages for all this junk are here, here, and here. Look for the things with Pelican and Py starting their names and the WebSiteDeploy function. The autodoc pages are here, here and here

###Step 1: pelican

I wrote a venv wrapper, installed pelican using that via pip, setup up a Mathematica palette to handle making new sites and posts, made a theme, etc.

###Step 2: Notebook to Markdown

Then I wrote a Notebook to Markdown converter because pelican can handle Markdown. Basically all complex box forms get rasterized. Math forms will be included once I finally get around to writing something about discrete variable representation and need them. Pre-rasterization future file names are checked against existing ones to avoid unnecessary rasterize calls.

###Step 3: Site Deployment

Using that same venv wrapped I call pelican's build process, then deploy the new content using WebSiteDeploy

###Step 4: Palettes / Stylesheets

I also built out a stylesheet that also saves to Markdown when a standard {"MenuCommand", "Save"} is called and a palette for the build processes, new file making, stuff finding, etc.

It's overkill and with a bit of work C.E.'s version is clearly a better way to do the same in the future. But it's good to have out here, I think.