about summary refs log tree commit diff
path: root/users (follow)
Commit message (Collapse)AuthorAgeFilesLines
* add a script to deploy the siteFranck Cuny2022-05-112-8/+15
| | | | | Instead of using the Makefile, move the content to a script. This will be executed by drone later.
* remove GitHub action workflowFranck Cuny2022-05-111-18/+0
|
* remove atom from the list of outputsFranck Cuny2022-05-111-9/+1
|
* update gitignoreFranck Cuny2022-05-101-0/+1
|
* nix: add tagsFranck Cuny2022-05-101-0/+1
|
* go: replace lsp-mode with eglotFranck Cuny2022-05-101-66/+15
|
* nix: start documenting what I'm learningFranck Cuny2022-05-101-0/+21
|
* content: update PCIe docFranck Cuny2022-04-031-1/+4
|
* site: remove unnecessary elementsFranck Cuny2022-04-038-116/+40
|
* delete some contentFranck Cuny2022-03-287-238/+0
|
* convert blog to notesFranck Cuny2022-03-2811-116/+117
| | | | Separating the two sites so I can customize them differently.
* note: update list of chipset for alder lakeFranck Cuny2022-01-301-2/+11
|
* build: use more recent version of hugoFranck Cuny2022-01-231-1/+1
|
* notes: remove some columns for the various CPUsFranck Cuny2022-01-231-20/+22
|
* CSS: improve readabilityFranck Cuny2022-01-231-6/+9
| | | | Using Firefox' accessibility tool as a guide.
* CSS: adjust some font sizesFranck Cuny2022-01-231-2/+2
|
* CSS: switch from class to idFranck Cuny2022-01-232-14/+14
| | | | These elements are unique on each page.
* layout: no need for a class to element 'article'Franck Cuny2022-01-233-3/+3
|
* css: TOC location based on display's sizeFranck Cuny2022-01-231-19/+82
| | | | | 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.
* layout: proper TOCFranck Cuny2022-01-231-4/+13
| | | | | | | | | | | | There's a need for two TOCs in the layout: one for when the page is on mobile; one for non mobile. When we are on mobile, we display the first TOC, before the article. When we're not on mobile, we hide that TOC and display one after the document. We restructure a bit the layout so that's it's a bit more readable too, and close tags properly.
* layout: wrap content in an "article" tagFranck Cuny2022-01-232-0/+8
|
* layout: drop the div 'main'Franck Cuny2022-01-231-6/+4
| | | | | The div 'main' is not needed, we are creating an element named 'named' in the main block.
* css: change style for tablesFranck Cuny2022-01-231-4/+8
|
* css: update color for the linksFranck Cuny2022-01-231-3/+3
| | | | Use a light blue.
* nav: use 'fcuny.net' instead of template variableFranck Cuny2022-01-211-1/+1
| | | | | Otherwise it's the name of the site, which is not what I'm looking for here.
* css: major cleanupFranck Cuny2022-01-211-76/+84
|
* nav: align the menu items to the rightFranck Cuny2022-01-211-2/+7
|
* post: change formatting for the dateFranck Cuny2022-01-211-4/+4
|
* nav: drop one item from the menuFranck Cuny2022-01-211-7/+0
|
* blog: leaving twitterFranck Cuny2022-01-151-0/+10
|
* css: more tweakingFranck Cuny2022-01-131-29/+21
|
* index: rephraseFranck Cuny2022-01-101-1/+1
|
* index: update current jobFranck Cuny2022-01-081-1/+1
|
* blog: add content about PCIeFranck Cuny2022-01-081-0/+196
|
* blog: notes about AMD and Intel CPUsFranck Cuny2021-12-291-0/+120
|
* css: change colors for some sectionsFranck Cuny2021-12-291-7/+13
|
* css: adjust line heightFranck Cuny2021-12-291-4/+1
|
* css: highlight links with a background colorFranck Cuny2021-12-291-2/+13
|
* blog: article on how to use tailscale + traefikFranck Cuny2021-12-291-0/+121
|
* config: add author informationFranck Cuny2021-12-291-0/+4
|
* layout: add a link to the RSS feed in the menuFranck Cuny2021-12-291-1/+10
| | | | | Specify the weight so that the items in the menu are listed in the order I want.
* RSS: fix the templateFranck Cuny2021-12-291-3/+5
| | | | | Generate correctly the content of the RSS feed. I only want the blog articles, not the notes.
* css: improve the color and fontsFranck Cuny2021-12-201-116/+47
|
* index: re-organize the main pageFranck Cuny2021-12-201-9/+11
| | | | Add a "contact" header with my information under it.
* menu: simplify the menuFranck Cuny2021-12-202-9/+10
|
* build: push git branches / tags after deployFranck Cuny2021-12-061-0/+2
| | | | After a successful deploy, push all the branches / tags to origin.
* CSS: drop custom fonts + colorsFranck Cuny2021-12-061-19/+22
|
* resume: updateFranck Cuny2021-11-121-0/+0
|
* static: add my resumeFranck Cuny2021-11-121-0/+0
|
* build: be explicit about the image to useFranck Cuny2021-10-211-1/+1
| | | | | If we're not explicit, we're trying to run the image tagged `latest', but there's no image with that tag.
* static: add ssh-key from desktopFranck Cuny2021-10-021-0/+1
|
* build: get the proper version for taggingFranck Cuny2021-09-091-5/+2
| | | | | | | | | | | | We were evaluating the version of the app when the rule was evaluated, while we need to get the version after we run `flyctl deploy`. Since we're tagging a release, let's also annotate the tag. Remove the `--build-arg` argument to `flyct deploy` since it's being ignored (same with `docker build`). Closes #1.
* blog: update elisp for git/sourcegraphFranck Cuny2021-09-091-3/+12
|
* static: add profile pictureFranck Cuny2021-08-261-0/+0
|
* blog: git-link and sourcegraphFranck Cuny2021-08-241-0/+40
|
* blog: sort pages in reverse orderFranck Cuny2021-08-241-1/+1
|
* build: sleep before taggingFranck Cuny2021-08-241-0/+1
| | | | | | | The last deploy was tagged v13, while the version deployed was 14. It's possible that running `fly info` too quickly after a deploy returns the incorrect version. Adding a `sleep 5` before running the command for git tag.
* CSS: various small fixesFranck Cuny2021-08-231-2/+2
|
* index: drop the main headerFranck Cuny2021-08-231-2/+0
| | | | It's ugly.
* CSS: use decoration on headers only for articlesFranck Cuny2021-08-232-6/+10
| | | | | | | | | | 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.
* CSS: rename the class for the tagsFranck Cuny2021-08-231-4/+6
|
* CSS: makes the menu more readableFranck Cuny2021-08-232-23/+39
| | | | Move the title to the left and the menu items to the right.
* build: tag the repo after a deployFranck Cuny2021-08-151-2/+7
| | | | | | | | If the deployment is successful, tag the repository with the version being deployed on fly.io. Don't deploy unless the repository is clean (this is done with the target `worktree-clean`).
* blog: working with go - initial contentFranck Cuny2021-08-151-0/+264
| | | | This note captures things that are useful when working with go for me.
* blog: add tags to firecracker notesFranck Cuny2021-08-151-1/+2
|
* layout: don't use header tag in listFranck Cuny2021-08-151-1/+1
|
* CSS: make the content more readableFranck Cuny2021-08-151-15/+24
| | | | | | | | | | 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).
* CSS: support table of contentFranck Cuny2021-08-152-0/+19
| | | | | If an entry has the parameter `#+toc` set to `t`, we will enable the table of content in the page.
* CSS: use a class for the menuFranck Cuny2021-08-152-8/+7
| | | | | We will have more use of the tag `nav` and we will need different styles for it.
* blog: replace github with git.fcuny.netFranck Cuny2021-08-141-1/+1
|
* blog: add link for containerd-to-vm codeFranck Cuny2021-08-141-1/+1
|
* css: reduce the size of the fontFranck Cuny2021-08-141-1/+1
|
* css: bigger font and highlight colorsFranck Cuny2021-08-052-6/+18
| | | | | Increase the font size and change some of the colors used for highlighting code.
* blog: update descriptionFranck Cuny2021-08-051-1/+1
|
* blog: add SSH public keysFranck Cuny2021-08-052-0/+2
|
* blog: add humans.txtFranck Cuny2021-08-052-0/+11
| | | | See humanstxt.org for more information.
* hugo: enable git information againFranck Cuny2021-08-051-1/+1
| | | | | Now that we're using a more recent version of the Docker image for hugo that comes with git, we can enable again git information.
* build: add a MakefileFranck Cuny2021-08-051-0/+29
| | | | | Add a Makefile to take care of most common operations (build, deploy, etc).
* build: add DockerfileFranck Cuny2021-08-051-0/+7
| | | | | | | | The Dockerfile used by fly is relying on an older version of hugo ([1]). We can use a newer version and provide our own setup, and configure with the flags we want (e.g. promote to HTTS automatically). [1] https://github.com/superfly/flyctl/blob/3eb204909fbecd5fd2b1ba4517cdbce2abd9f74a/internal/build/imgsrc/builtins/defaultbuiltins.go#L89
* hugo: TLS by defaultFranck Cuny2021-07-191-1/+1
|
* github: deploy to fly.io instead of GH pagesFranck Cuny2021-06-201-17/+5
|
* hugo: don't enable git infoFranck Cuny2021-06-201-1/+1
| | | | | | | The docker image used by fly.io to deploy a static website with hugo does not come with git, which prevents us to use the option `enableGitInfo`. This is not critical for now, so let's disable it so we can deploy.
* fly: add configuration for fly.ioFranck Cuny2021-06-201-0/+40
|
* blog: update to containerd articleFranck Cuny2021-05-191-1/+1
| | | | Fix boot options
* css: add a scroll bar if the content overflowsFranck Cuny2021-05-181-1/+1
|
* blog: containerd to firecrackerFranck Cuny2021-05-171-0/+567
|
* layout: add a navbarFranck Cuny2021-04-229-38/+75
| | | | | | | | | | | | | 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.
* toml: re-configure markupFranck Cuny2021-04-131-1/+18
|
* css: switch to sans-serif; add tables; other tweaksFranck Cuny2021-04-131-5/+28
|
* css: remove extra white spaceFranck Cuny2021-04-111-1/+1
|
* blog: google doc failureFranck Cuny2021-04-111-0/+56
|
* css: change font to roboto slabFranck Cuny2021-04-111-5/+5
|
* taxonomy: add pages for tagsFranck Cuny2021-04-113-20/+48
| | | | | | | We want to have pages that list all the articles related to a given tag. Update the configuration to add support for tags and the permalink structure.
* layout: add date and tags to single pagesFranck Cuny2021-04-062-1/+42
| | | | | | | We want to show the tags and the published/updated date for the articles. Add to the CSS the classes for these new elements.
* css: update style for links and headersFranck Cuny2021-04-061-4/+8
| | | | Indent properly the CSS
* css: set background color for code blockFranck Cuny2021-04-061-5/+9
| | | | Indent properly the CSS for the `pre` tag.
* css: change the default fontFranck Cuny2021-04-061-5/+5
|
* layout: fix format for the dateFranck Cuny2021-04-061-1/+1
|
* layout: clean up empty spaceFranck Cuny2021-04-061-1/+1
|
* add action to publish to GH pagesFranck Cuny2021-03-071-0/+30
| | | | | | Add a workflow configuration to publish to GitHub pages. This is using the standard configuration from https://gohugo.io/hosting-and-deployment/hosting-on-github/
* initial site with hugoFranck Cuny2021-03-0711-0/+180
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.
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-12-25 18:52:52 +0000