Seems to be building successfully!
https://dev.azure.com/cobalt-org/cobalt-org/_build?definitionId=2&_a=summary
I went to the extreme on testing combinations. I need to consider where to scale back
Hi there, I'm going to be the elephant in the room and ask a "rude" question: Where is cobalt heading? Obviously, Ed don't have the bandwidth to work on it :( In the meantime, I see Zola flourishing and we're even seeing people migrating to it and I have to admit it begins to annoy me a little bit :-/
I love working with you Ed, though, you teach me a bunch of stuff on Rust and even in computer engineering (even it's my fulltime job for 17 years now)
So I would be sad to give up on this
liquid has potential that despite it not being the most ideal template language, it is one of the few Rust runtime template engines that lets you fully customize it which I know at least
cargo-generate has appreciated
As for cobalt, I have project ideas that zola can't handle and I'm thinking tuning cobalt to be able to handle. I can't remember off my head what those features are for my "private, family focused facebook" but I remember coming across them
While family changes have limited my time quite a bit, another challenge is the number of projects I'm involved in. I am trying to identify pause points for those projects and work towards them.
committed: conventional 1.0 support before pausingtypos: benchmarks ran and formal announcementassert-rs: effectively at a pause pointcargo-release: reduce the number of commits and improve "is a release needed?" detectionstager/cargo-tarball: This is the area of most work needed
Whats not listed are some ideas I have around improving the licensing landscape. Those will also be a relatively big distraction if I move forward with them.
and I hope people are more excited by
typos than they were for committed
(
typos is a source code spell checker targeted at being run in CIs)
Funny enough,
typos was originally going to be my second Rust project for learning the language until Cobalt took over all my time
So that ideas has been sitting around for years
Especially when the goal it to automate Changelogs Oo
which is super duper great
Some people are against auto-generated changelogs. Sometimes it is because people are unfamiliar with how conventional helps. Other times, its because they aren't considering the size of the project, how thinly spread maintainers are, and that sometimes something is better than nothing (looking at you, all those Rust crates that broke compat without any changelog for me to reference to know how to update).
For the people anti-changelog generation, I'm tempted to add a feature to
committed that will error if a fix, feat, or BREAKING CHANGE commit does not include a change in the changelog.
apart from having a standardised format that ease the reading
To go back to cobalt, what do you think will happen to it? For a blog, shall I move to Zola as well?
Geobert and I have also been doing some direct messages
Cool. I was looking at redoing www.xenrelay.com in cobalt. Looks like I need the paginator to get the sidebar working. Is the paginator still an alpha feature that requires installing from source?
Current status of cobalt: On pause for a little bit.
I got unblocked on some other programs so I'm trying to get that out of the way so I won't be distracted from cobalt development.
For when I'm back, my focus is on the next branch where I'm doing a major re-architecture. The primary goal is to make it easier to add new features but I hope to also get a performance boost
@proegssilb cool. I'm curious, how did you hear about cobalt and what made you choose it? We haven't exactly been doing a great job on marketing :)
....I have a nasty feeling sticking this in one of my includes won't work:
---
pagination:
include: All
per_page: 5
order: Desc
sort_by: ["published_date"]
---
<div class="sidebar ">
<h2>Recent Posts</h2>
<ul>
{% for ppost in paginator.pages limit:5 %}
<li><a href="{{ site.base_url}}{{ ppost.permalink }}">{{ ppost.title }}</a></li>
{% endfor %}
</ul>
</div>
<div class="sidebar">
<h2>Tags</h2>
<ul>
{% for ptag in paginator.indexes %}
<li><a href="/{{ ptag.index_permalink }}/">{{ ptag.index_title }}</a></li>
{% endfor %}
</ul>
</div>