Generally, one is expected to provide a custom theme for one’s pelican website. We’ll set that up with a function that will also build out the editing layout. # Uncomment following line if you want document-relative URLs when developing # Feed generation is usually not desired when developing So as with most python projects, the step-1 is to build a virtual environment and install via pip. And even better it was written in python so if I had to extend things or figure out what was going on I’d be able to do it in a langue I was fluent in. It was simple, supported Markdown syntax, was extensible. Looking through the docs got me convinced that this was, in fact, the way I wanted to render a site. So instead I decided to look at a website I had a guess was built programmatically. That prompted me to think “hmm… do I know do this for markdown and write a converter?” which I really didn’t like the thought of. Even speeding things up using templates and nicer stylesheets could only got me so far. But on the other hand it meant I was writing the raw HTML. html file, exporting all the CSS and image necessary to get things working.Īnd, you know, it worked pretty well. Over time this just got too clunky, though, and I wanted a better system, so I sunk a day’s work into building a system to display that HTML right in the notebook as a listing of cells and export it to a.
My basic process there was to write some block like: $htmlTemplate=Īnd I’d fill it in with various parameters using TemplateApply. For various things I’d needed to host static HTML pages in the Wolfram Cloud. It starts, I suppose, with an HTML templating package I wrote. For this website’s inaugural post I thought I’d detail how it was built.
0 kommentar(er)
