• CTRL B to make selected text bold
• …

The cache populates wrong entries when using search or tags

Steps to reproduce:

• Go to overview, take any blog post and on any tag
• Go to a different blog post with different tags and use a different tag
• --> Old search is shown

Problem: Blazor only allows one HeadContent at the time. As OgData and StructedData use HeadContentonly the latest will be rendered. Both data should be put together into one HeadContent- probably inside OgData.

Currently all timestamps when a user navigates to a page are saved as DateTime.UtcNow including the timestamp.
That is not really necessary as the Date part would be sufficient enough.

DateOnly would fulfill this requirement. Unfortunately, it isn't natively supported by EF in its current state (EF 7.0.1)

Upserts are currently throwing an exception.

How to solve:
[ ] Decouple create / update into new component which gets called from outside
[ ] Component returns new BlogPost to parent

Cahce throws exception when adding a new blogpost due to the missing Id.

It can happen, thanks to copy&paste, that the preview image URL and the fallback image URL are literally the same.
That doesn't make much sense and should either pop up a warning message or even a validation error.

## Possible Solution
We can create our own attribute to do that:

[AttributeUsage(AttributeTargets.Property, AllowMultiple = false, Inherited = true)]
public sealed class FallbackUrlValidation : ValidationAttribute
{
    protected override ValidationResult IsValid(object value, ValidationContext validationContext)
    {
        var model = validationContext.ObjectInstance as CreateNewModel;

        if (model.PreviewImageUrl == model.PreviewImageUrlFallback)
        {
            return new ValidationResult("PreviewImageUrl and PreviewImageUrlFallback should not be the same");
        }

        return ValidationResult.Success;
    }
}

As the owner I want to give the blog a better branding than just my name / title.

Therefore we should address the ability to also add a „brand“ image into the navbar.
If we have a brand image url and the blog name/title we always prefer the image over the title.

Still the title is used for meta tags.

Points to consider:

• Adding brand-image-url to the appsettings.json as well as AppConfiguration object
• Extend the Factory to map those fields
• In the navbar check if we have the brand image. If so use this otherwise just the title
• For responsiveness we should give the image a max dimension to preserve the current navbar behavior

Patreon is a famous choice for continuous monetary support. This can be added to the current Donation Section.

Currently version 5.3-alpha.1 is used that brings some bugs with it:

• Navigation for Admin Panel does not work

As soon as there is a (more) stable version, the Blog should use that version.

Expected:
50-50 ratio

The current implementation of "hasLiked" is global. Therefore an user is not able to like one blog post and then like another.

Current behavior

• The user likes any blog post
• The user goes to another blog post
• The user can only "unlike" the page

Expected behavior

• The user is able to like multiple pages

Current Situation

When a new blog post is created where IsPublished is false the blog post is still visible in the archive. The same holds true for blog posts which are „unpublished“.

Target Situation

Unpublished blog posts should only be visible in the admin area

Steps to reproduce:

1. log in as a dummy admin on my dev machine
2. Write a blog post.
3. Save it as a draft.
4. Edited the draft and published it. Exit app to save the cache.
5. Reopen app and log in as dummy admin.
6. Edit the post adding markup, specifically ##
7. Publish the post, exit app.
8. View the post by reopening app and clicking Read the Whole article. The ## shows up as a literal instead of being changed to html.

Discussion

Workaround

Happens with SqlServer

Steps to reproduce

• Open the blog and navigate to a blog post in admin mode (or create one and navigate afterwards)
• Edit the blog post and change the tags
• Save the blog post
• Edit the blog post again
• Check the tags in the overview page. They are doubled now

Possible Root cause

• CachedRepository does give a wrong version when editing the second time

The current introduction card needs some smaller re-ordering and styling of the components to look a bit better

Option: use inputfile

Two get directly awaited which are independent

Currently the VisitCounter expects an instance of BlogDbContext.

This will lead to issues when trying to access the page via RavenDB or InMemory.

How does it work

You can give a thumbs up when you thing the blog article was good

Technical Requirements

• At the end of the blogpost give the opportunity to thumbs up
• Display how many thumbs up there are
• Save thumbs up per blog post
• Save thumbs per blogpost per user so that they can not vote multiple times

Notes

For saving and reading state: https://www.nuget.org/packages/Blazored.LocalStorage/

See more details here: https://aspnet.github.io/quickgridsamples/

Add Postgresql support (for example via Entity Framework).

hey,
Instead of id for the blog post URL can we use title? replace spaces with - (Hyphen)?
Or all writer to create a URL.

Idea: Use In-Memory cache to reduce the initial waiting time. Everytime a user hits the package we can check if the cache is up to date.

Found a weird issue, instead of coma(,) while adding the tags I mistakenly added a semicolon(;) and saved the post. when I realize my mistake I try to update it, and it is not working.
could be an issue with EF core, but I am looking into this.
two things I am looking into

1. the bug
2. adding a helper text on blog post page to let user how to add the tags

Enabled at least Syntax Highlight for C#

Sometimes it is desired to save a current blog post but don't necessarily publish it directly. Especially for longer blog posts where on works longer. Therefore a possibility should be created to save a blog post but make it not visible to others.
Tasks:

• Hide unpublished Blog Posts
• Create Toggle in Create / Update Page
• Make it visible for the content creator in the overview

After updating a blog post the Id and the object stays the same.
This can lead to potential unwanted override. The page looks like "create a new blog post" but still holds all reference to the updated blog post.

Example: https://steven-giesel.com/search/.NET5

This will lead to an 404. It will not result in an issue when navigated via clicking on page or searchbar

With the current setup only one mode is allowed at a time (dark mode with version >4.1)

There should be a toggle for the user to change that.

• Toggle between light and dark mode
• Save the preference
• Use OS default as standard

When updating a blog post and changing the tags, after change those tags are not visible in the overview page nor in the search (for tags).

Root-Cause

When entering the update blog post page, the blog post is retrieved from the cache rather than the underlying repository.
That leads to the problem, that the children are not tracked anymore and therefore don't get updated.

Test to reproduce

[Fact]
public async Task GivenBlogPostWithTags_WhenLoadingAndDeleting_ThenShouldBeUpdated()
{
    var bp = new BlogPostBuilder().WithTags("tag 1").Build();
    var sut = new CachedRepository<BlogPost>(Repository, new MemoryCache(new MemoryCacheOptions()));
    await sut.StoreAsync(bp);
    var updateBp = new BlogPostBuilder().WithTags("tag 2").Build();
    var bpFromCache = await sut.GetByIdAsync(bp.Id);
    bpFromCache.Update(updateBp);
    await sut.StoreAsync(bpFromCache);

    var bpFromDb = await sut.GetByIdAsync(bp.Id);

    bpFromDb.Tags.Single().Content.Should().Be("tag 2");
}

Should include an url, title and Date

Create a global color palette which could also easily adopted for new themes.

It should make it also easier to customize the whole appearance

Instead of dismissing the whole work, we can just put the whole blog post into the local storage (or give the option to save the draft to local storage).

This can also be done for already created blog posts where we additionally save the ID to make the mapping happen.

Create a global color palette which could also easily adopted for new themes.

It should make it also easier to customize the whole appearance

When using an Azure serverless Database the first request to the database is very likely to timeout due to the rampup face.

Solution

• Implement retry-logic for the initial connection

It is good to have MySQL Support as well.

Ideas:

• having a wiki page how to set up everything
• Interactive setup when the blog is loaded the first time

For the second one we need way more stuff beforehand.

Submit button while writing a new blog is always disabled.
I checked the code and found that canSubmit variable is set to true.
I think it should be false by default. what do you think?

Candidate: https://giscus.app/

Images should be lazy loaded so the initial page hit is smaller

Show in the overview (ShortBlogPost) a rough estimate of the read time in minutes.
We want to give the user a rough estimate how long / how detailed the article is. If we know the reading time is 15 minutes we know it is a longer blog post with more in depth knowledge.

According to google the average reading tempo is roughly 200 words per minute.
For every image we might want to add just flat 15 seconds.

So if we have 300 words and 2 picture, we have 1.5minutes from words plus 0.5 minutes from pictures = 2 minutes.

Due to the two-way binding and latency it can happen that input gets "lost" because we enter multiple characters which get send to the server. The server evaluates the two-way binding while the next one comes in. Now we are in a race condition.
The longer the content the more likely we encounter missing characters.

Add vertical timeline with professional events. This should give the reader a rough overview of the professional experience one made.

Open Questions

• Is it part of the.AboutMe Page?
• How much in detail should the timeline go? Do we want to allow to click on an entry and navigate to a kind of „detail“ Page?

In the current state only one image is allowed as preview.
This can lead to the smallest denominator in terms of filetype and quality.

For example: LinkedIn does not support webp/avif but other sites do.

Dropdown menu instead of single a href