tencurse / neocities-v2 Goto Github PK

• Create a page for website buttons
• Create my own site button

Following tencurse/symmetras#1, implement the breadcrumb navigation sitewide, using the 11ty navigation plugin

• Use the plugin to create a navigation hierarchy
• Add breadcrumbs to each page (we already have the terminal nav up top as a sort of navigation ?? That means we might need to relocate the theme switcher in case of deeply nested pages)
  • Exceptions should be made for fic pages since they already have their own separate breadcrumbs

This is the first step for tencurse/neocities#15

See: https://bt.ht/improving-tufte-jekyll/

I have a "digital garden" in my local machine via Obsidian, though it's really more used for my story pages and brainstorming. Back when I was refreshing my knowledge on frontend web dev, I also created a bunch of backlinked notes there, which I still refer to now and again.

Thoughts:

Would there be a benefit to making some of these public? My personal site is where I share whatever I want through blog posts, and I don't want to fall into the trap of creating something like this only to abandon it later. I'm also trying to reconcile the idea of posting unfinished thoughts online. (The idea of digital gardens is that these ideas/thoughts evolve over time, as well as doing away with the whole concept of feeds.)

What notes to share? What would be helpful to me and anyone else? Is there a point to creating a guide/tutorial to something that can be easily found online?

There is also the concept of scaling later, ie, just start making notes then organize them later once it grows larger. Which maybe is fine for local file management but might be a nightmare for website navigation. (This would be easy for flat files, aka, just everything in one folder... and just create pages for each tag/topic to "organize" them. <- Would be a nightmare for array filtering.)

Possible tasks, in no particular order:

• Use Johnny Decimal system for the sitemap ??? I use this for my local machine and I'm not sure how effective this would be for a website? Gah!
• Re-think page hierarchy, maybe use 11ty navigation plugin
  • Navigation breadcrumbs can be added at the top, which can help when navigating through notes/pages...
• Add backlinks functionality (which pages? blogs and notes only? all of them?)
• Add a command palette-like search bar to quickly find notes (now this feels like reinventing the wheel when I can do this locally anyways...)

Due to the layout change, I need to re-implement table of contents for blog posts. Low priority for now because my blog posts so far don't have any subheaders.

• Decide on the design and where to put it

https://creativecommons.org/licenses/by-nc-sa/4.0/

Screenshot taken from a Linux machine. Also doesn't work on Android.

Might wanna take a look at https://www.fontsquirrel.com/tools/webfont-generator 🤔

Change blog archive to be a condensed list of titles / subtitles / post date. Explore other blogs on how they do it.

Inspiration:

• https://tympanus.net/Development/MenuHoverEffects/tsula.html
• https://www.typewolf.com/site-of-the-day/msds-studio

What to do with excerpts?

• Retain for home page ("Latest blog post")
  • Kinda wasting a metadata just to use it for one page... Hmm...

Potential issue:

• If the list is too condensed, the design may not scale when tagging system is implemented in the next milestone.

• Add a next/previous post on the bottom

Check out Terminal Hugo theme for inspiration.

Check out the 11ty blog starter and implement whatever's missing in my site!

Some things I find might be useful:

• image optimization
• per page CSS bundles
• post drafts
• accessible deep links to headings done
• feeds for ATOM and JSON #23
• sitemap.xml

Refer to styleguide option. Also look for plugins for the ==markdown highlight style==

Insp: https://glenthpvs.tumblr.com/melodic-wish

• Add tags to blog posts
• Display tags in blog archive list
• Display tags in the blog post itself
• Create tag pages (Zero maintenance tag pages for your blog)

• Re-work the archive pagination into the same design as the blog one (#9)
• Apply changes to chapter pages

Use the 11ty RSS plugin

Use openring

Predecessor:

• #23

Currently (in my local machine), all stories regardless of content are listed in one page. There's a script which notifies the user that the page has mature content, and updates localStorage once they provide consent. This might be good enough, but I'd like to add a layer of separation by adding a page for those stories with a large banner of content warning.

• Create a new filtered collection for mature/explicit stories
• Create a new filtered collection with gen stories
• Create new page for mature/explicit stories
• Update fic archive to show link to separate page, and only display gen stories
• Add a banner of content warning to the separate page