| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Add a menu with links to some sections. Tweak the CSS to make the
website a bit more readable.
|
|
|
|
|
|
| |
Stop playing with fonts, just use what ever is the default from the
user. Make the width of the page a bit more tight. Improve readability
of tables.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Get rid of the navigation bar, remove a number of elements, put more
things on the main page. Clean up the CSS.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Remove the configuration for fly.io and the configuration for Caddy
since I'm running this on GitHub pages now.
Remove unused targets from the flake configuration and drop the pandoc
dependency. The resume is just a web page accessible at [1].
[1] https://fcuny.net/resume.html
|
|
|
|
|
|
| |
- reduce the number of colors
- use the default fonts instead of forcing my own
- increase contrast for code snippets
|
| |
|
|
|
|
|
|
|
|
| |
Set the color to something lighter, closer to white.
Increase the size of the font.
Add a small border with color for h2 headers.
|
|
|
|
|
| |
Get rid of the footer and the icons. Set a light background color, and
simplified the listing of the pages.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add my resume to the content, with a dedicated CSS. The resume is in
org-mode format, and I use `pandoc` to convert it to HTML. This is done
when the site is build, and is integrated in the docker image.
It is available at /resume.html, but is not listed on the site, that way
I can give the URL to who ever is interested in the future.
It would be useful to also generate a PDF version of it and store it
with other static content.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The notes will be moved to a different site/repository, with their own
style.
Update the index page to make it more readable. Make the header more
visible with fewer links.
Add a footer, with links using SVG icons.
|
|
|
|
| |
Using Firefox' accessibility tool as a guide.
|
| |
|
|
|
|
| |
These elements are unique on each page.
|
|
|
|
|
| |
Depending on the size of the display, display the TOC either before the
article or on the right of the article and let's make it sticky.
|
| |
|
|
|
|
| |
Use a light blue.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Add an element "article" to the single page template, and change the CSS
to use the decoration for headers only for that kind of content.
Having decoration for all headers is distracting, it's more suited for
actual content.
We also don't need decoration for h1, only smaller headers.
|
| |
|
|
|
|
| |
Move the title to the left and the menu items to the right.
|
|
|
|
|
|
|
|
|
|
| |
The Roboto Slab font is hard to read (at least for me). Switch to Droid
Sans and make the text a bit smaller.
Change the background of the page to white (again), and change the
background color for the code snippets.
Add text decoration for headlines (similar to org-bullet).
|
|
|
|
|
| |
If an entry has the parameter `#+toc` set to `t`, we will enable the
table of content in the page.
|
|
|
|
|
| |
We will have more use of the tag `nav` and we will need different styles
for it.
|
| |
|
|
|
|
|
| |
Increase the font size and change some of the colors used for
highlighting code.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I want to differentiate blog's entries from more general notes. For
this, we create two menu entries, and add a navbar at the top.
The nav bar let us select between the two kind of articles: blogs or
notes. For now we have a single blog entry, and no notes.
The page to list entries is simplified: we use the same layout for all
lists (tags, notes, blogs).
The CSS is updated to support the new nav bar.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
We want to show the tags and the published/updated date for the
articles.
Add to the CSS the classes for these new elements.
|
|
|
|
| |
Indent properly the CSS
|
|
|
|
| |
Indent properly the CSS for the `pre` tag.
|
| |
|
|
Start my website from scratch once more, using hugo to generate it. For
now the layout is pretty simple:
- an index page that will list future notes
- notes should be created under the "content" directory
The theme is custom and I'll try to keep this simple.
|