solita / solita.github.com Goto Github PK

Highlighter should be changed to "rouge" and markdown to "kramdown". This seems to have negative effect on our vagrant machine. Please communicate without using here tags while fixing this.

https://github.com/blog/2100-github-pages-now-faster-and-simpler-with-jekyll-3-0

The author names are now links to our internal email accounts. Won't this generate spam?

E.g. if the last word on a line is "in", the theme may add a linebreak between the "i" and the "n".

Avatar pics are clickable, but the href does not point to real content (only #).

Some options for content:

• Filter post based on that writers account (so that pressing my picture you would only see my posts)
• Link to writers homepage
• mailto

We should probably remove AddThis social sharing buttons, as they can be tracking the users (?). The main Solita site is not using AddThis either. We could just copy the main site's share buttons here as well? Does anyone even use sharing buttons in 2022?

https://developers.facebook.com/docs/opengraphprotocol/

There are links to other Solita blogs in the footer. We know they are Solita's blogs, but outsiders won't. So we need to add a description which will the what the links are.

E.g. "Solita's other blogs:"

The new layout uses excerpts on the front page. These are now missing for the new EPiServer posts which were freshly merged.

Excerpt should be on one line in the post meta data. Example: https://raw.github.com/solita/solita.github.com/master/_posts/2012-10-30-coffeescript.md

After Jekyll 3.0 update the personal feeds have been broken. E.g. http://dev.solita.fi/feeds/rss_rinorragi.xml

Eli kun postilla on excerpt, sen voisi laittaa meta descriptioniin, eiks je?

Should we rename the repo? I mean, the url that is currently the name isn't even working, it should be solita.github.io. But since we are using a custom domain dev.solita.fi, this repo doesn't need to be named with an url. So we could just rename this to solita-dev-blog or something.

More about GH Pages and domains: https://docs.github.com/en/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites

Author information is overflowing on top of content. See screen below.

Suggestion: use flexbox to lay out each post.

PS. Greetings from a fellow blogger: https://dev.solteq.com (You inspired us!)

See failed build here https://github.com/solita/solita.github.com/actions/runs/7897753738

Probably caused by GitHub updating some dependencies of the built in Pages builder.
We can be more in control here by starting to use a custom GitHub Action to do the Jekyll build for generating and deploying GitHub Pages instead of using the current zero-config process.

Seems like these issues are related to the problem:

• jekyll/jekyll#9544
• actions/jekyll-build-pages#115

From what I understand it seems the issue manifests when using actions/jekyll-build-pages versions 1.0.10 or 1.0.11 (currently latest and default for GH pages classic build) but you could use older 1.0.9 via custom GH action. The open issue above is in the main jekyll repository so that Jekyll 3.9.4 and 3.9.5 apparently have some issue but that alone doesn't seem to cause the problem in this repo as even those versions seem to work fine in some situations (e.g. when testing locally). Maybe it's a combinations of dependencies that triggers the problem when using those latest versions of jekyll-build-pages.

I did add tags to my posts. Is there any way to actually support these? :)

Current "Solita developer blog" is lame.

Maybe something like:

• Everything from coffee to functional programming"
• Programming motherfucker

Post your ideas here! :)

Blog posts are generated from markdown. It's pretty natural to structure the headings starting from h1 (# heading) in markdown, but this results in bad heading structure in the resulting web page. At the moment we have pages that look like this:

<h1>Blog post title from markdown frontmatter</h1>
<h1># First level heading from markdown</h1>
<p>...</p>
<h2>## Second level heading from markdown</h2>
<p>...</p>
<h1># First level heading from markdown</h1>
<p>...</p>

Correct structure would be

<h1>Blog post title from markdown frontmatter</h1>
<h2># First level heading from markdown</h2>
<p>...</p>
<h3>## Second level heading from markdown</h3>
<p>...</p>
<h2># First level heading from markdown</h2>
<p>...</p>

We should limit the headings generated from markdown to be no higher level than h2. Some posts might start from h2 already, so we cant just do heading + 1.

A tag cloud would make it easier to find posts related to one topic. Surely there is a way to implement them in Jekyll + GitHub Pages? Also, we'll need to add tags to all the old posts.

The tags are case sensitive which means there appears duplicates like "JavaScript" and "Javascript" which doesn't make much sense, at least to me. IMO, they should be case insensitive making the browsing via tags a little easier.

Add gravatar image to each post. Could configure in _config.yml for each author.

jarnopeltoniemi commented 2 days ago
Ei suurta merkitystä, mutta laittaisko tuohon tweet-nappiin tw:via="solitaoy". Tulisipa mainittua Solita jakaessa.