atla5 / personal-site Goto Github PK

Ideally I'd like to have a left panel for each page, and for this panel to be unique.

These should be put into a separate folder and loaded in like the 'main_content' sections will be.

Tentative plans:

Need to have a descriptive readme file introducing the purpose, design, and navigation of the site.

Hate it when sites have the default empty favicon.

• use favicon.cc to design and export a favicon.ico image
• add this image to the project and link to it from includes/header.html.

add google analytics integration to track who is visiting the page.

Add gravatar to the main page.

'Feeds' page should be the FeedReader submodule.

Current site is rigidly Web 1.0 and uses PHP.

To bring it up to speed and allow for gh-pages hosting, all PHP should be removed and replaced with purely html content and javascript controls.

Want to reduce the .HTML pages (and file directory structure) into divs that are loaded into the main body using javascript commands or GET requests. This way the navbar, footer, and possible sidebar remain static on the page and only need to be loaded once.

Krutz has a very good example that he explicitly gave permission to work from, available here. It doesn't sufficiently separate the header and footer as I would, but contains much of the 'routing' control I'd want to emulate.

Expanding the window too far horizontally causes the shaded control on the side to track with the edge of the window and detach from the image.

I often recreate very similar classes wherever i go to develop something. having them all in one place is useful and cuts down on what i include here.

Background

• current set-up does not include tests and requires manually running the deploy command and uploading the resulting files to amazon s3

Success Criteria

• third party CI system is used to run tests on the repository upon creation of a PR
• process for uploading the deployed static app to s3 is automated
• this new process is triggered upon a successful merge into master

Background/Reasons for Change

• options for reusability
  • visualizing github projects with information from the API will definitely be useful
  • ...
• fun: rewriting sites is a good time and will provide some opportunity for experimenting a bit more than what i can do at work
• simplicity: no way such a simple site needs such a large framework
• experience
  • get some additional handle on open-wc and web components
  • demonstrate what experience I already have using the tech
• future/stability
  • web components are a large part of what i want to invest in in the future
  • they'll be more inter-operable over time (proximity to the standards)

Implementation Details

• look at interoperable standards/API integrations
• ...

Description of Changes

• remove old/ #29
• exercise all of the angular code
• replace existing functionality with re-usable components (e.g. 'github-project' or 'atla5-project', etc.)

'about' and 'projects' pages need data to read.

Migrate format from individual pages with #includes for every header and footer to simply exchange the html body.

Nav bar contains broken links and is very poorly structured/organized. Needs to be restructured to enhance navigation and understandability.

Top navbar menu display does not update to show the current (active) page.

Background

• current master branch includes files that are no longer relevant to the existing display

Success Criteria

• a new archive-2015 branch is created preserving the code in its old state
• the old/ and e2e directories have been removed from the main branch

The docker presentation page shows only the slides and not the write-up or its references.

• react will work great with all the json i want to dynamically pipe in (without git submodules!)
• will facilitate the creation of reusable webcomponents if i want to experiment with MicroFrontends
• will make search (#9) very easy and quick
• will bring my website from Web 1.0 to Web 3.0 (more feature-rich, reactive, etc)
• will provide me with meaningful experience in a new technology.
• it'll be fun!

Move data about courses, work, projects, etc. into separate json files and read and display this text via a library, minimizing the amount of HTML I ever have to edit.

Leverage 'handlebar' as per 'learn handlebar in 10 minutes' and 'making a single page web app without a framework'.

Existing file structure is overly complex and rigid. Get rid of unnecessary files and folders, simplify content, and remove what isn't necessary.

Create a page describing 'lib-re' projects/purpose and providing links.

Had to temporarily hardcode the header, navbar, and footer into the index.html to get it to display.

Need to find the HTML5/js equivalent of .PHP's 'include' functionality to allow me to maintain the separation of concerns here.

Change [Philosophy]-(academia.edu) to [Library Science]-(library_resume.pdf)
Update 'Software' link.

text bodies are displaying in plain, unformatted, unstyled html output. looks very bad.

Add the following git components/widgets to the home page where possible:

• Contributions list:

• Repositories list:

• Sidebar (maybe)

Add metadata tags (especially keywords) to assist with future search integration.

My 'atla5/blog' was meant to be displayed through here, but it needs to run.

May need to redo this in pure .js for simplicity and so it runs on gh-pages.

original formulation below:

SCRIPTED BLOG ENTRIES (.txt to .php)

• craft a rather basic shell script to take in a .txt file and spit out a .php usable by the site
  (this will allow me to write freely and prevent me from having to rewrite the includes and html
  tags manually for every new page and blog post)
  • create a basic template .php file (with html tags, include, and open body) and simply parse
    the text inside the file line by line converting it to .html while keeping formatting...
    someone has almost certainly done this already with markup, find and adapt that.
  • create a standardized format for these .txt files specifying type, tags, destination, etc.
  • '-t' tag for adding a custom title to the created webpage. otherwise default to the filename
    before the extension (e.g. "about.txt" -> "Aidan Sawyer | About", "unix-philosophy.txt" ->
    "Aidan Sawyer | Unix Philosophy")...
  • '-i' interactive mode might make some sense for individual files and would save from having
    to format each individual file with the section of the blog it goes to and what tags are
    associated with it.

note: .txt->.php changed to .md->.html