solita / solita.github.com Goto Github PK
View Code? Open in Web Editor NEWSolita Developer Blog
Home Page: https://dev.solita.fi
Solita Developer Blog
Home Page: https://dev.solita.fi
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:
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
.
Add gravatar image to each post. Could configure in _config.yml for each author.
I did add tags to my posts. Is there any way to actually support these? :)
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:"
Eli kun postilla on excerpt, sen voisi laittaa meta descriptioniin, eiks je?
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?
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:
The author names are now links to our internal email accounts. Won't this generate spam?
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.
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
After Jekyll 3.0 update the personal feeds have been broken. E.g. http://dev.solita.fi/feeds/rss_rinorragi.xml
jarnopeltoniemi commented 2 days ago
Ei suurta merkitystä, mutta laittaisko tuohon tweet-nappiin tw:via="solitaoy". Tulisipa mainittua Solita jakaessa.
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
.
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!)
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
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
Current "Solita developer blog" is lame.
Maybe something like:
Post your ideas here! :)
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.