belaplatform / bela_newblog Goto Github PK

As mentioned by Andrew.

https://disastrid.github.io/bela_newBlog/category/instruments/
example:

This is the meta property that tells facebook which pic to pick for the link preview.

Blog posts used to get that path wrong:

<meta property="og:image" content="{% if page.image %}{{ page.image }}{% else %}{{ site.default_img }}{% endif %}">

this was giving a wrong relative path, like e.g.:

<meta property="og:image" content="bela-mini-launch/header.jpg">

as a consequence, facebook was picking the first pic instead of the header pic.

Now I fixed it so it actually gets the right URL pics for the header pic 01f6671 . Would it be appropriate to have an option for the author of the post to pick a different pic from the header one? With some other optional param maybe? Just asking

<ul><li> and <ol><li> have list-style-type set to none (so you see no circles nor numbers).
I think this should be removed.

Also, there is a weird css rule (it is in the compiled main.css, got it from the chrome inspector):

.post p:first-child {
    font-size: 1.25em;
}

which makes the test of list items look larger. I think this should be removed.

it currently states

We are still finalising the design of the audio capelet but the most likely scenario will be second-
order filters on each input and output.

This is on Safari version 8.0.8

Tested on Chrome and Firefox and rendering fine.

e.g.: on [this page](https://disastrid.github.io/bela_newBlog/category/instruments/] if you move your mouse between the top and the bottom post, the image in the sidebar will flicker. Is it because you can potentially have different pics in the sidebar for each project? That'd be great, so we could show here a preview of the post's image.

Right, the jekyll documentation states your blog posts need to have a filename of the format:

YEAR-MONTH-DAY-title.MARKUP

but Y-M-D will be overridden if there is a date specified front matter at the top of the file.
One valid solution to avoid confusion and stale dates in filenames is to use the following format for the filename:

0000-00-00-title.MARKUP

and specify the date in the front matter

See this nice table here:

Unfortunately it does not look as nice here, though it surely is interpreted as a table.

Would be useful for page navigation and for sharing specific parts of posts

When vimeo links are embedded in the page the window is slightly smaller than it should be. See for example videos embedded on this page: http://blog.bela.io/2017/09/29/till-bovermann-bela-supercollidor/

Should be an easy fix for Astrid, will make post with vimeo videos look much better.

Any easy way to have custom image width?
These are a bit too wide!

https://disastrid.github.io/bela_newBlog/2016/04/07/bela-analogue-vs-audio/

For personal websites, projects etc.

Is there a way to make bold?

*myBoldText* and _myItalicText_ both translate into an <em> tag which is rendered by default as italic.

I vote for *this* to render like this, for compatibility with github, but anything will do.

e.g.:

loading https://blog.bela.io/2018/05/02/salt-a-programmable-eurorack-syntesizer// (note the two // add the end) will cause the image https://blog.bela.io/assets/images/salt/salt-front.jpg to be loaded from https://blog.bela.io/2018/assets/images/salt/salt-front.jpg instead.

e.g.:

 <meta property="twitter:image" content="steim-7.jpg">

but it is wrong (the image lives somewhere else). It should be either absolute or relative.

e.g.:

A possible solution would be to add

.highlighter-rouge{
  overflow-x: auto;
}

so that you obtain this:

and you can scroll the box content horizontally.

Note that the next thing I would ask for is make it obvious that the content is scrollable (i.e.: always show scrollbar when there is something to scroll).

So that. e.g.: the Axis team can be properly credited

To recreate visit https://disastrid.github.io/bela_newBlog/2016/11/28/saber/ and then click on the Sound Design Category under the main title.

Would be nice to have image captions to explain what's in each photo / credit where necessary.