About this website
Here can be found meta-information about the website: initial ideas and concept development, resources used to build its features, roadmap for wished implementations.
Also, a further resources section for stuff and comments which doesn't fit previous sections. Possibly, just to record trashed ideas and outdated comments on implemented features, unless I decide to strike-through bullet points in the roadmap list instead -everytime I manage or discard them...
Why creating this website
Some reasons are already presented at random in the main "About" page, ...
...
How I'm building this website
This website aims to be as open-source (actually FLOSS aka Free/Libre Open Source Software) as possible as its source code can be found here.
Its contents are mostly released under a Creative Commons license (specifically the CC BY-NC-SA 4.0 or Attribution-NonCommercial-ShareAlike 4.0 International) unless otherwise specified, meaning it's free to share-reuse-remix with same license and without commercial purpose, as long as proper credits are given to the author(s) of the source materials (code, text, images etc...) -me included, please, as a lot here will be personal stuff I share in this corner of the Web.
Fundamental resource has been the italian website and community of LeAlternative. Their project is aimed at disseminating beginner-level open-source and privacy-friendly alternatives to proprietary software while also raising awareness on the ethics of electronics. Along with insightful resources on these topics (such as PrivacyGuides, EticaDigitale and The512KBClub LINKS!!!), thanks to them I've discovered the Neocities platform, which propted me to finally experiment into building my own basic website.
Other resources used can be found below:
What I'd like this website to have (next)
Basically the roadmap for features I'd like to improve and/or to implement in the future. Some require but a little digital gardening from time to time while others are just out of reach of my current skills (so I either learn how to do it myself or ask for help).
Roadmap (click to expand)
Here they are, sparse and annotated mostly, but the idea is the first ones have priority:
- update this roadmap constantly [last update: 2025-10-27]
- merge notes between Joplin and the about/This-website.html
(exporting as HTML directly from Joplin!)
Most important stuff first:
- Fix menu
- Fix spacing
- paragraphs
- line breaks
- space from headings
- justify/align
- space from lists
Strictly content-related stuff:
- gallery entry "focal fossa" ubuntu background
- blogpost on tool for newpipe music:
write down procedure just link to github and copy procedure from there as it's very clear -for downloading music via NewPipe and CLI tool- then publish it on Tech blogpost https://github.com/Quasolaris/NewPipePlaylistExtractor
- blogpost on basic developing tools, to also add to Fundamental Resources in about/this-website, from Mozilla MDN to w3 validating tools (https://www.w3.org/developers/tools/ html and css specifically) as well as desktop Firefox DevTools function and mobile Browser Console debugging with https://eruda.liriliri.io/
- blogpost on notification unificator/aggregator other than google/iOS [unify notifications on mobile to 1 aggregator service active only (to reduce battery consumption but getting all notifs)]
- blogpost for import to Joplin process (from StandardNotes) in Tech (note already written down)
- add to Digital humanities resources blogpage digital humanities Climate coalition toolkit on github from fediverse post dhh sas-dhrh.github.io/dhcc-toolkit and dhd-greening.github.io; add these to Archaeogaming section: https://avikhalil.com/2022/05/12/how-we-are-playing-category-simulation-and-imagination/ ; https://www.saveancientstudies.org/archaeogaming-education
- blogpost of me, planning to get this set up seriously instead of going on with local copies, and the ethics of DRM-free purchases music to truly support a better alternative to streaming monopolies (copy/feature the blog at https://murtezayesil.me/buy-music-to-support-musicians-but-why/); closed with the meme images and description "Oh and remember: If you can't own it, it's not stealing!"
- blogpost on rsync for synchronise/backup local storages in a simple way
- blogpost on finally finding Markwhen for timelines (simple workflow to add and refine while only visualisation)
- blogpost on finally finding NeoDB (after separated media and/or proprietary solutions "a bookwyrm with rate.house dbs")
- update the blogpost about PopOS bootloader with steps from video (noted in 2025-03-19)
- blogpost on setting up (Mullvad)VPN to "bind" qBittorrent client when torrenting (video and resource here https://tohippo.com/bind-vpn-to-torrent-client/ https://inv.nadeko.net/watch?v=XXuc593KtsE then just followed the suggestion from a reddit thread's comment to select the Network Interface from "Any" to the one of the [Mullvad]VPN)
- blogpost for Tech on Nier:Automata theming hunt 2025-05-04
- update blogposts and add contents as specified in single notes here under the #troweltips tag
- UnArchaeology 2023(?) > Make simple blogpost ("I propose this perspective as a tool useful to discipline and social awareness raising..."), wish to contact researcHer for theater labs, complete catching up and link conference
Mixed structural-content stuff:
- add quick comments directly on HTML Templates, to replicate in webpages reusing them, to verbosely explain structural choices or simply explain what they're for (e.g.: nav in header; single blogpost limited nav; to-top non-button etc...)
- research about the "keyword" tag for the "head" element and possibly add to webpages and templates
- improve "back button" and "home" as particular navigation bar in single webpages/blogposts
- fix background and visited-links colours
- "back-button" has a turning arrow symbol followed by the text "go back to category index", aligned left, while "home" button should simply be the website logo followed by the name aligned to center
both are part of a nav tag, part of a sticky-to-top but unintrusive navigation bar to add into the header tag (just like for index webpages which have the complete website navigation bar)
- add "Back to page start" following these guidelines https://jkorpela.fi/www/totop.html (but as a button perhaps?)
- set more space before titles or after paragraphs which precedes titles (that should be possible by modifying related parameters in the main CSS taken from thebestmfwebsite -following the code to extract from https://ultimatemotherfuckingwebsite.com/ for spacing while adding some more accessibility?)
- improve navigation bar --- https://www.makeuseof.com/responsive-navigation-bar-using-html-and-css/ (sticky on top and reducing to icons/collapsed menu on small screens)
- create nice homepage with title-logo (Fate/-like with S;G subtitle as svg/png for the moment) as part of the header tag https://www.w3schools.com/howto/howto_css_responsive_header.asp; https://code-boxx.com/css-responsive-logo/
- add website tab-ico(n) and other icons (navigation bars and footer?)
- add small-and-faded-footer with "Website build by me[link-to/about/Me] with open-(re)source(s)[link-to/about/This-Website]- released under CC-BY...[link-to-license] unless stated otherwise (or others' contents)"
- make index pages with two columns -one for list of direct HTML files in the directory and another for sub-directories (check w3school website-from-scratch example https://www.w3schools.com/howto/howto_make_a_website.asp!)
- check whether to style with div or section+labelsARIA the title for blogposts templates
- add drafted-only contents (in particular about "WHY" section, missing links, archived URL of links)
- add to homepage: internal website-tree(check/merge other notes!) and external link to personal accounts (as a linktree or search for singlelink html templates again)
- make meta-blogpost in /contents directory
- first (and only?) inside the ~~/blogs~~ /contents folder, apart from the index.html, which further explains what I meant this macro-section to be (stemming from the very origin of the word "blog", copying the definition and initial history from https://en.wikipedia.org/wiki/Blog#History, to link as source for further resources on the topic)
- index making this choice of terms (resources and contents, what they're meant to have inside, also consideration vs. "assets") and making clear reference to "blogs" kind mostly but not exclusively
- make explicit (in macro-group index or first blog or tech ones?) that single blogs/internal webpages (not index/directory pages) will only have a "back-to-previous-directory" i.e.: "../" (and maybe also a "home" i.e.: "/") button so to make the maintenance/creation of webpages more sustainable (not having to add/change navbar in each html file); also: navbar is not a site-map (for that I'll provide the tree of directories in dedicated webpage!)
- ultimately made it in order to decide directories structure to rename/change folders and their nested organisation, move files into new folders, then fix src and href links
- e.g.: "~~/blogs~~/archaeology/arch-and-videogames/" and "styles" where to put CSS files
- "blogs" instead of "blog" or RATHER sections without redundant "blogs" macro-group???: main focus of this website is archaeology and tech anyway -the truly "personal website" might come later and either be separate or integrate this one
- home/src/img/ or ~/resources/images/; ~/src/css/ or ~/resources/ styles and images and ... (for any other code and resource not to use indipendently or show as content)
- ~/contents/ archaeology and tech and ... (for any other category of content I create and is shown on the website)
- update/complete following contents:
- improve "Website changelog" webpage or section in about/This-website.html
- simple unordered list with date prepended
- full fledged but simple timeline
- both cases: can take from git updates and related commit+comment history?
- Make page with further "Resources" divided in either categories sub-pages or unique webpage with a clickable table of content per categories, nested, to jump-scroll at section (as for a Wiki) and/or make sections collapsible/accordion summaries (as for Logseq) [again I might use "accordion" summaries like here https://dev.to/tota11ydev/accordions-1-5-and-10-minute-versionsall-accessible-quicka11y-2d3b]
- Decide if to put blog thoughts divided in per-day-date-folders, if better management at hand or if not to avoid splitting personal and public notes, in any case should be simple as in Scribe instances (also take inspiration anyway to better format paragraphs in CSS)
- Add inspirational projects which made me want to have my website [either on the "Why" section of About or in in a section per-se or in "extra resources" for digital stuff-ethics (as digital gardens???: tommi.space etc...)
- add tommi.space
- Add https://meyerweb.com/ui/about.html to inspiration (alt-fancy website-view I was looking for?)
- Add https://jeffhuang.com/designed_to_last/ in good practice/inspirations
- Add https://sadgrl.online/webmastery/ in good inspirations
- Add https://ar.al/2020/08/07/what-is-the-small-web/ in good practice/inspirations
- Add https://growyourown.services/ in good practice/inspiration (and to expand digital space
- Add https://whitep4nth3r.com/blog/html-is-all-you-need-to-make-a-website/ inspirations (but decide: it does not actually says what I expected...)
- Add https://resilientwebdesign.com/ (still to check actually...)
- ...
- Add "FLOSS projects" section (with the ones used, followed, or just suggested)
- Add https://html5up.net/ for site templates (or for other extra resources? Maybe add a nested paragraph with h3 collecting useful resources found but not used/not used for a particular feature)
- add possibility to expand image gallery items into their own description (title, description, licence) page by clicking on them with a simple hover-and-overlay(or fade-slide) effect --- https://www.geeksforgeeks.org/how-to-create-image-overlay-hover-using-html-css/ ; https://stackoverflow.com/questions/18322548/black-transparent-overlay-on-image-hover-with-only-css
- find a way not to heavy too much the image gallery webpage (either by uploading only compressed/thumbnail images there and the full resolution only in dedicated description pages or through an automatic process???) --- https://web.dev/fast/#optimize-your-images
- modify the 'how-to' section of This-website with the two topics (sustainability and ethics) "trying to keep both in mind... philosophy of action... roadmap to self-hosted website/services powered by local renewable energy" --- with links to https://ec0lint.com/ for guidelines and https://www.websitecarbon.com/ for reminding the environmental footprint of technology
- add another main section of the website as a digital-Garden repository for useful-to-others/meaningful-to-me resources (links/materials) and sub-divided in webpages with topics connected with this "digital-" dimension (such as "-Sustainability" "-Ethics" "-Archaeology" and eventual final sections deepening that topic not necessarily connected with digital stuff)
- add section, or subsection(???maybe not convenient for knowledge organisation???) where possible (eg. steins;Gate theme as an art piece in image gallery), of public things I've made and projects I took part to with related links (Steins;Gate theme for firefox ; Amadeus splashscreen ; Things-to-Come translation ; ... )
- publish source code also for having a way to track changes by Git by using either Codeberg or GitLab
- make this a SolarSite (which actually also means self-hosting the website properly)
- simple life-log
- interactive and hyperlinked life-timeline threads (more on this it's written in the ideas and concept section above
- add a switch to render the website in a more fancy way by re-directing to a version with extra-scripts/custom background/fonts --- https://animejs.com/ for eventual animated/styled alter-website to switch to with a button on all webpages (as the dark-mode/high-contrast switcher button in thebestmfwebsite) or as a link to another set of webpages mirroring the others but with css and scripts attached
- (meta-marker for stuff added in batch from JoplinNotes on 2025-10-27)
- add to web design and low-tech projects https://100r.co
- add this privacy-awareness section from Micr0byte's website https://micr0.dev/#privacy-demo (I guess as a dedicated "privacy blogpost with warning of script usage -although in the homepage would be cool or, better, in the index page for Privacy and Security to-be section?)
- add to best practice and web design "Printable website" https://piccalil.li/blog/printing-the-web-making-webpages-look-good-on-paper/
- compress every image actually rendered into blogposts and pages, even in the gallery, but giving the option of clicking on them to be addressed to the link hosting the uncompressed file (to put into a dedicated folder in "Resourses" or as a sub-folder in "src/images")
- I've probably already thought and wrote about that for the lightweight aim of the website (so search note and take previous ideas into consideration before deciding and merging!)
- batches of Archaeogames made for an Archaeogaming course! https://archaeologie.phil-fak.uni-koeln.de/institut/fachgebiete/archaeoinformatik/archaeogaming by Sebastian Hageneuer at https://itsmoreofacomment.com/category/games/
- 2025-01-24: further looking into a better ways to maintain this simple static website (now that I struggle and stuck again with categories and site map folder's structure), I could use a CMS or Static Site Generator after all, just to try out different setups without having to manually change all the links (the menus in particular as well as the crosslinks); I'd like one thing which simply handles the links dynamically offline at site generation (i.e.: at best updating links if changed, at least making checks on broken links and/or having a simple command to fix all, even just a "find-and-replace" all consistently and all bundled together without having to create a setup for folders and templates and profiles on a text/code editor software all the time) while leaving to me all of the HTML/CSS part (or has an exact editor/viewer panel of code... could use Joplin or an IDE after all?); found so far:
- digital detox e privacy tech (anche in Italiano) https://datadetoxkit.org/it/home/
- progetti carini tech e privacy da diffondere (in italiano!) https://socialsicretinino.net/ (scoperto da https://www.lealternative.net/2021/03/02/socialsicretinino/)
- retro web ma anche tech alternativa come progetto di community e blogging federato contro il siloing in italiano! https://www.dmi.unict.it/nfarceri/articles/welcome.eng.html (ita https://www.dmi.unict.it/nfarceri/articles/welcome.ita.html) > da qui il sito https://www.dmi.unict.it/nfarceri/main.php
- low tech e digital garden in italiano! https://www.giardino-punk.it/harvesting-the-net/
- tech and sustainability good examples https://eco.kde.org/handbook/ and Infomaniak report admitting they pollute anyway
- security/privacy tech and sustainability good resource project
- aesthetically pleasing small website, Italian, to discover how it is developed as seemingly compiled static AND wordpress CMS ??? https://sitoctt.octt.eu.org/index.html ; CSS pesante ma impegno per compatibilità: approfondire questa cosa come soluzione anche per il mio sito? > "Oltre al fatto che (nel possibile) voglio supportare sistemi vecchi, 'ste maledette rogne si presentano anche su dispositivi meno popolari ma attuali, tipo il Kindle! Insomma, per i troppi browser che non includono un'impostazione per disattivare completamente il CSS, era d'obbligo fare quello che ho fatto: al percorso /Plain sui miei domini del clearweb c'è una root parallela, e pagine con uguale contenuto ma CSS ridotto all'osso."; anche il modo in cui NON-gestisce i cookies (e relativi banners) avendo comunque un statistica di visite tramite FLOSS goatcounter.com potrebbe fare al caso del mio sito (assieme al banner come per WuMing Giap che rimanda alla spiegazione)
- clean homepage and homepage+site structure like i did for mine as per 05-07-2024 https://alexschroeder.ch/
- for privacy section https://switching.software/
- for privacy collection and nice website https://awesome-privacy.xyz/ and from the same author (as gamification of privacy steps) https://digital-defense.io/ (and to check all of her stuff as open-source advocacy catchy projects)
- nice personal website inspiration (watchlist tables!) and good tech resources/principles https://hacktivis.me (found after digdeeper.club -which on the other side I recommend to check too BUT WITH CAUTION as ONLY if one isn't paranoid and has a strong source-checking method as well as being proficient in not being influenced by the way stuff is expressed rather than the actual content and an overall firm resistance to fall into toxic persecution patterns... otherwise you have to already have expert knowledge in IT as well as a very based opinion on geopolitics, as the author often lets it permeate in all of the contents, so that then you're free to draw your own based conclusions)
- added folder for self-hosted fonts >>>now update svg image and related handles to display correctly!
- (check if already added!) somewhere in principles/ideas/good web guidelines https://jeffhuang.com/designed_to_last/
- idea for formatting and dark theme as well as web design and chill web presence https://daudix.codeberg.page/about
- idea and guidelines for the RSS (+ suggestion of nice website, blogs on tech and music, with sound web principles: https://minutestomidnight.co.uk/feed.xml); further inspiring web design choices in restructuring the website by dropping WordPress https://minutestomidnight.co.uk/blog/website-minutes-to-midnight/
- lunr search on github static website:
https://github.com/BLE-LTER/Lunr-Index-and-Search-for-Static-Sites
- inspiration for personal/public project, single-page, particularly gave me the idea for the half-transparent navigation bar (on mobile at least https://woodpeckersnest.space/)
- yet another good example, for contents and similar website-making philosophy, as well visual structure and ideas to implement https://www.alexmolas.com/2024/02/05/a-search-engine-in-80-lines.html
- another useful tool/project used for development from mobile https://github.com/liriliri/eruda
- yet another good resource (with further references in-text) https://www.staticguide.org/
- find a way to display the site-map/structure/contents: (first check this https://bobbyjack.medium.com/generating-a-sitemap-for-a-static-site-356fa3c26074) everytime I change or add to it I could run "tree" in terminal from the website's root folder, copy the output into an html (and possibly making it auto-link?), publish it into a dedicated site-map webpage and/or add relevant chunks to each section's (folder) index.html page; I should nonetheless keep the navigation-bar updated with all collapsible sections AND a general site-map webpage always visible
- make this website able to easily add blogposts and webpages: I would have gone with an easy html template to fill each time then upload, but 1° I'm still not so confident with directly using Git and 2° then I wouldn't have the chance to have an auto-updated list of contents >so the idea, I've searched for already and landed on headless-CMS as I didn't want nor need a easy but heavy CMS like WordPress while still wanting to make this as easy to replicate by anyone (and other good reasons, among others, the most recent found https://dev.to/lizziekardon/what-are-the-benefits-of-using-a-static-frontend-27f9), landed of building with something like Jekill or Hugo ---> https://stackoverflow.com/questions/46263785/i-cant-edit-jekyll-index-html ; https://jekyllrb.com/tutorials/convert-site-to-jekyll/ ; https://jekyll.github.io/jekyll-admin/ ; https://plenti.co/ ; https://zwbetz.com/convert-your-plain-old-html-site-to-hugo/ ; https://stackoverflow.com/questions/53338741/how-to-convert-a-html-css-js-template-into-a-template-for-hugo-static-website -searched and to search under "most minimal headless cms" and "migrate static html pages to hugo" and "best headless CMS for personal blogging" and "headless CMS with git integration codeberg" - Hugo vs. Jekill: https://www.freecodecamp.org/news/hugo-vs-jekyll-battle-of-static-site-generator-themes/ ; https://draft.dev/learn/hugo-vs-jekyll ; https://discourse.gohugo.io/t/is-it-possible-to-use-hugo-in-codeberg-page-repositories/31012/3 ; https://abf.li/posts/migrating-to-codeberg-pages/ ]
- BUT then I'd still have the need to create an pre-established directory structure, so to avoid issues in wanting to change it later and having to re-link/break internal sections', or can headless CMS do that and I've forgot in the meanwhile (some half a year+ has passed since previous idea so it's possible)? If I'm right, then I had another idea, namely: using WordPress.org to create simple webpages and manage their data locally (so as a backend only) then export only a static version of that to upload online for visit (html/css only frontend)! Currently (2024-01-09) checking it's a possible and feasible thing... after asking around, it's probably faster to get an idea by installing WordPress and try to develop the site locally, then try to export with plugins/static-site-generators-from-wordpress-files and upload it to Codeberg pages or the like (https://www.neuralword.com/en/article/how-to-create-a-local-wordpress-site-step-by-step-guide) -[update 2024-01-15] too much of a hassle with WordPress.org, needs for plugins which are freemium for full functionality, and I'd need to change folders and structure just the same (+learning php or rather copy pasting without learning more code) so: as it is not different from learning a probably simplier headless-CMS like Hugo or Jekill, then I either use one of those two, or go plain html and change it later if it will ever be needed... -[update 2024-01-16] I'm probably going with plain html/css and create a "templates" folder inside /blogs/tech/ to keep 1-EvenBetterMFWebsite; 2-blog templates (with version progressively numbered and/or with date of creation/update)
- was thinking: if I leave it all as plain html/css, and have an exact mirror of all the content in the repository to be the content seen and reachable on the website, then I have a "What You See Is What You Have" without the need for a repo for the source code -everything can be examined and copied from web-inspector or wget; in this case the sense of still using Git and a repo like Codeberg (apart from putting it online for free hehe) is just to have a versioning for myself and a streamlined method of cloning/forking for others -while the code availability should be self-guaranteed even without;
- make a blogpost or similar [Glossary of technical terms or "git the repo of the distro"] about tech glossary and/or the necessity for translation in common-talk to be understandable for non-tech-savvy folks; that's why I want to link every term and acronyms to the related wikipedia page, but could also maintain my own glossary copying definitions as I add terms into the articles; might make it switchable to other languages (italian) [Glossario dei termini o "inverti lo screenshot nel drive"] >>> potrebbe essere fondamentale un blogpost simile anche nella cartella "archaeology" per gli articoli sull'archeologia;
- anyway, nonewithstanding the linking to wikipedia, I should be able to add a bubble-on-hover giving a quick definition and/or extended acronym
- change main.css as I reflect upon setting pitch black dark background to white text for OLED (less screen luminosity battery consumption) or better the grey background for design and less eyestrain reading (midway compromise might be lessening the contrast by using pitch black background but with not pure white text?)
- add life-timeline as in my blueprints (scans) with basic HTML/CSS (https://www.w3schools.com/howto/howto_css_timeline.asp) though it seems this is something which requires a minimun of js/html5 to be done as I wish to > closer is Aeon Timeline [PERÒ Vorrei cercare un'alternativa FLOSS a https://timeline.app/, e che sia il meno possibile 'derivata' con l'obiettivo di non rimaner bloccato con un programma, quindi già un plugin per un software proprietary (come per Obsidian) mi sa troppo... :/ Intanto condivido che ho trovato queste, che si avvicinano a quello che cerco, ma dovrei provarle per essere sicuro: - https://thetimelineproj.sourceforge.net/index.html - https://markwhen.com/ - https://codepen.io/clintabrown/pen/DQmPbp ; https://metalblueberry.github.io/post/howto/2021-02-28_hugo_timeline_shortcode/
- found Markwhen cascading visualization, almost that, if i can make it vertical... (more on MyLifeTimeline note and MyTimelineProject)
- inspect https://bbbhltz.codeberg.page/ for how to blog without CMS (?) on CodebergPages ]
- make a changing typewriter effect for the about/Me.html page with "I'm a fake " (reference ex.: https://jgthms.com/), contextualise it with part of the explanation in the old-about page, add details on notes/paper notebook about the origin and sense of the 'faker' in the fate series (resources: https://www.sitepoint.com/css-typewriter-effect/ ; https://codeconvey.com/html-typing-text-effect-animation-css/ ; https://freefrontend.com/css-typing-text/ )
- add to inspirational (technical design CRUCIAL ONE) https://jgthms.com/web-design-in-4-minutes/
- add inspirational (be weird and fancy eye-candy layout ideas) https://weirdwidewebring.net/
- on using or not a CMS for the website https://createdbycocoon.com/post/blogging-without-cms
- make a blogpost or folder in Tech with the different links to MFWebsites and their story (just like the Ilyvakfhjkk github repo )
- making contextual sections explaining each "fake-" role I assigned ex.: "Fake-music maker: MAGIX; AlterEgo (by Plogue https://www.plogue.com/products/alter-ego.html and ALYS by VoxWave https://labs.phundrak.com/ALYS/ALYS): not even with a MIDI external device, just via laptop keyboard by virtualising the connections, with VMPK Virtual Midi Piano Keyboard (instructions at https://vmpk.sourceforge.io/) and LoopBe1 (at https://www.nerds.de/)" > I may link and land on the one-pager section explaining each term by clicking on temporary apparition of the terms?
- for FLOSS projects section on Music: https://signalsandsorcery.org/ ; [that-other-one-from-LeAlternative-beat-pad???]; https://hakim.se/; neon29(?) experiments; expand this to "Weirder internet" links
- make a section with "experiments" (heavier in data and possibly broken just to test html/css things for the website like: animated background https://www.foolishdeveloper.com/2022/04/create-animated-background-using-css.html ; animated rain effect https://www.foolishdeveloper.com/2022/04/css-rain-effect.html ; etc...)
- Add Vids below to TrowelTips (instead)?:
Videos yt below? (link there or migrate to a PeerTube account or add as direct files[this better not for space...]? Anyway add previous yt creations -as Dante and GSV videos- to gallery)
- digitalize/scan drawings of old and calligraphies/miniatures Even if incomplete
- Add archived articles from GruppoStoriaVera (directly and web.archive links)
- Coding likings (followed, made, contributed):
Publish EDET kde store through github and ARCHAEO cursor set (to update with planned notes and cooperative call)
Magic-circle generator [if to add then search for more on txt file note]
- Add (on page "about me") some sort of "character building sheet" as yet another way I'm trying to define myself (with my skills and all: "skill trees" for things I've tried and/or "titles" for things I've achieved -just like missions/titles/achievements in BDO log)
Further resources and comments
What-why-how I've done and/or discarded ideas and features. A sort of digital dump for record adding some stratigraphy to this site ;D
IF I'll actually fill this section here probably goes all of the changes of mind about where to host the website, which tools to develop it or not, and why. I should actually add timestamps to make it a nice timeline of my failures and a useful record for further fail-safes...
This might be just a quick list, while for the "failing gloriously" purpose I should better make dedicated webpages further explaining the context and process behind relevant choices, linked here from summarised bullet points.
Ultimately this might serve as a commented website changelog.
-
2025-10-27
- fixed the Gallery css to have both the internal one for specific image styling and the main one for texts
- added navigation bars to the Home, About, Gallery (the main navbar) and to the About sub-pages (the blogpost navbar)
-
2025-02-02
Migrated all images and descriptions from Deviantart to this personal website's Gallery, implementing the ability to click on images there to open dedicated blogposts, BUT !didn't actually add all the features listed in the Gallery webpage index!
-
2024-04-12
added folder for self-hosted fonts (for banner-title to display properly as svg without converting fonts to paths -which made the svg file weight more and slow down the homepage!)
-
2024-03-09
Published first (incomplete) blogpost in the archaeology (and Narrative Medias section) category! Not exactly relevant for the weblog, but worth noting anyway, and also marking the first considerations about how and which class to give to sub-sections with momentary thoughts (or "archaeo-logs" as explained further in the Tech category)
-
2024-02-22_2024-03-07
Trying to settle in the code decisions over navigation bar and website structure with related styling; creation and publication of first TrowelTips homepage banner; discussion over creating one-pager categories instead of nested directories and single webpages for sub-categories (e.g.: not creating a "arch-and-games" folder, but putting it all into the "archaeology" folder, so only nesting and sub-nesting sectioning elements as indexes lists for blogposts in the general category index webpage)
-
2024-02-21
Change yet another html structure for blogposts and indexes following standards at https://html.spec.whatwg.org/multipage/sections.html#the-section-element (improved discovering the "hgroup" tag...)
-
2024-02-19
Finally made up my mind about how to semantically (or not) divide single blogposts and index pages through https://css-tricks.com/how-to-section-your-html/#dont-swap-div-for-a-section (with sections, divs, classes or headers)
-
2024-02-09
- Added first navbar
- Tried timeline for website changelog
add a "Website changelog" webpage or section in about/This-website.html > put there changes in hosting and content uploading methods [from NeoCities to CodebergPages; manual commit via git (add simple guide)... idea to move to headless CMS/Hugo (more info and resources on what I tried or want to try for the website in about/This-website.html ]
- simple unordered list with date prepended
- full fledged but simple timeline
- both cases: can take from git updates and related commit+comment history?
-
2024-02-06
Actually remade website's directory structure and file placing
-
2024-02-03
- Decided final directory structure by drawing site-map on paper notebook, choosing this website not to be the personal one meant at first (not yet at least), rather a blog focused on few topics and hosting some personal content to later merge in an eventual bigger website (or main domain with sub-domains for different stuff/services)
- ultimately decide directories structure to rename/change folders and their nested organisation, move files into new folders, then fix src and href links
- e.g.: "~~/blogs~~/archaeology/arch-and-videogames/" and "styles" where to put CSS files
- "blogs" instead of "blog" or RATHER sections without redundant "blogs" macro-group???: main focus of this website is archaeology and tech anyway -the truly "personal website" might come later and either be separate or integrate this one
- home/src/img/ or ~/resources/images/; ~/src/css/ or ~/resources/ styles and images and ... (for any other code and resource not to use indipendently or show as content)
- ~/contents/ archaeology and tech and ... (for any other category of content I create and is shown on the website)
- meta-blogpost anyway
- index making this choice of terms (resources and contents, what they're meant to have inside, also consideration vs. "assets") and making clear reference to "blogs" kind mostly but not exclusively
- first (and only?) inside the ~~/blogs~~ /contents folder, apart from the index.html, which further explains what I meant this macro-section to be (stemming from the very origin of the word "blog", copying the definition and initial history from https://en.wikipedia.org/wiki/Blog#History, to link as source for further resources on the topic)
- make explicit (in macro-group index or first blog or tech ones?) that single blogs/internal webpages (not index/directory pages) will only have a "back-to-previous-directory" i.e.: "../" (and maybe also a "home" i.e.: "/") button so to make the maintenance/creation of webpages more sustainable (not having to add/change navbar in each html file); also: navbar is not a site-map (for that I'll provide the tree of directories in dedicated webpage!)
- quick blogging commentary serie on "Archaeology in anime-manga, videogames, and popular culture in general" [description] "S-parsed digital notes and considerations on archaeology as featured and represented in anime-manga, videogames, and popular culture in general!
I know it's nothing so original, but still I wanted to compile and share my list of encounters between these topics, as I can't deny anymore I'm a nerd (for both things).
I start this as a personal project, no expectation but to have a somewhat ordered list of observations whenever I feel like commenting these encounters, so it's by no mean a complete nor a proper research work. It may end up like a hunt for crossovers on the topics with commentaries, some written at length and some just drafted, some complete blog posts and some fragmented notes with day-by-day reactions.
That's the idea." >>> tried anew on another website (to lift the trial off)
-
2024-01-30
- make lists in about/This-website.html (and everywhere else) collapsible/accordion for better readability
- for this: I've discovered I can use "accordion" summaries like here https://dev.to/tota11ydev/accordions-1-5-and-10-minute-versionsall-accessible-quicka11y-2d3b
- but see also https://www.w3schools.com/howto/howto_js_collapsible.asp and https://stackoverflow.com/questions/24977965/collapsible-lists-using-html-and-css
-
2024-01-15
Getting back to the idea of a truly static and HTML-CSS pure website and finally tidying up the Codeberg repository to start adding contents
-
2022-12-05 - 2023
- Notably: my confusion whether to use WordPress, headless CMS or else, or not
- Decided to drop updating Neocities as main hosting in favour of Codeberg as providing better access to source code and chance to train with git versioning
- Tried some Jekyll and Hugo
- Also dropped static website generators as still too 'abstracting' processing (far less than CMS tho)
- Another try to use WP only as a back-end, only for database management and flexibility in changing contents' categories, failed
-
2022-12-05
Created first two (meta-)blogposts on html templates to reuse inside the website and on git basics to update the repo
-
2022-11-25
- Registered account on Codeberg.org and migrating the static website to the "pages" repository to use their automatic hosting service
- Moved to codeberg and its "Pages" service: mention I'll eventually update the neocities' page, as it's a nice project, and easier for everyone to get started if not interested to learn Git!) [also: update the "about" section when writing about git- and versioning and move to things as done]
-
2022-02-18
Registered account on Neocities.org and created the "TrowelTips" static website with webpages drafts for Home, About, Gallery
-
2021-06-03
- Note on a paper notebook with a story-telling idea, sketches of website structure, and webpage contents for a blog on archaeology named "TrowelsTips"
- Idea dropped in favour of an simplier micro-blogging on Mastodon (short-lived...)
-
2020-04-19
Reconstructed date of a paper draft with pencil sketches for my personal website's structure
-
2019 - 2020
Semester when I had IT classes at Bachelor, discovered Linux, and started thinking about actually creating a personal website
-
YYYY-MM-DD
Example of a changelog