fernandocelmer / mkdocs-simple-blog Goto Github PK

I followed the mkdocs manual for deploying a search feature through plugins: search, but the theme ignored that part.

I did some tests and managed to implement a rudimentary search.

If I focus on bringing this feature to the theme, can I count on your help with some questions?

I think it would be a cool feature to persist the theme selection in local browser data, to pass this information to all pages, not just the current selection, as a default feature of mkdocks-simple-blog.

Where do you think is the most appropriate place to persist this information? LocalStorage or some cookie usage?

Describe the feature

Simple code syntax highlighting, just as most of technical blogs.

Use Case

Currently, all code blocks are in black and white. As a minimalist blog, it seems necessary to have a simple syntax highlighting setting. I hope it can be made into an option, so that those who need it can enable syntax highlighting, while those who don't need it can continue to keep their code blocks in black and white.

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

SDK version used

Any

Environment details (OS name and version, etc.)

Any

Hello all,

I found a small design issue with the <code> blocks in this theme (you can also see it on the current preview image).

The code indentation on multi-line code blocks currently has a slight error:

• For single-line blocks, using single backticks, applying a padding is fine, as is done in theme.css
• For multi-line blocks, using triple backticks, since the very same padding as above is applied, this will break correct indentation; Multi-line blocks only use a single <code> block inside a <pre> block, especially for multi-line code

In the preview image, you can see that the mkdocs.yml-line is indented not by the code itself, but by the padding applied to the <code> block surrounding it. However, this padding does not translate over to the other \n's, hence the docs/-line beneath is not aligned.

My current fix is simply to override the css:

pre code {
    padding: 0;
}

For each <code> block nested inside a <pre> block, as is the case in multi-line blocks, the padding is reset. Alternatively, you may still add vertical padding, as it does not impact the indentation. In my personal blog, I have added this rule, and it seems to be fixing the issue.

Thank you for your time, please let me know what you think about this.

Your theme is just amazing!

It will be very nice if the color of the theme can be changed in any page by a click.

Pull Request:

• #20

Describe the bug

next and previous arrows appear but are not clickable because there is no next or previous page

Expected Behavior

we should not see a next or previous arrow if there is not a next or previous page

Current Behavior

next and previous arrows appear but are not clickable because there is no next or previous page

Reproduction Steps

this issue is present in any example

Possible Solution

in the standard style the next or previous arrow become greyed out to indicate there is no page before or after

what could be used to indicate the arrow is disabled ?

SDK version used

mkdocs-simple-blog==0.0.9 & mkdocs==1.5.3

Environment details (OS name and version, etc.)

macOS Sonoma Version 14.3 (23D56) & Python 3.12.1

• Option to remove components
• Language
• Font Styles

Hello,

I'd like to change my 404.html page's content to something else, but I couldn't figure it out on how to do so.

I tried some things:

• Changed the configuration according to this discussion on material theme repo: squidfunk/mkdocs-material#5018
• Changed mkdocs.yaml file as suggested by this issue on material theme: squidfunk/mkdocs-material#575
• Added the custom file on the root of the project as suggested by this page: https://docs.readthedocs.io/en/stable/reference/404-not-found.html

But without success. Could you please help me out?

PS: Maybe a tutorial/guidance could be added to the documentation?

TIA