PerceptionTime VS pages-gem

I would like to disagree. Spikes have everything to do with intelliegence. Perception to be exact. Here are my arguments: https://github.com/rand3289/PerceptionTime

Over the next five years I kept thinking about a theory that would not use symbols during computation. Came up with some arguments but they weren't convincing enough. Now I live in my own world. All I got is this Idea that's not even an architecture but explanation why spiking NNs is the way to go: https://github.com/rand3289/PerceptionTime

Qualia can not be expressed symbolically. I have a theory that qualia can be expressed as a point in time though. A spike. This point in time is "formed" when an agent detected a change within itself. The change was caused by its environment. Here is more info: https://github.com/rand3289/PerceptionTime

I would argue that spikes are points in time and are NOT symbolic in nature. They can be expressed as symbols (timestamps) however. Here is more info: https://github.com/rand3289/PerceptionTime

Perception becomes subjective when there is a body. Here is more info: https://github.com/rand3289/PerceptionTime

I completely agree! This is how I belive we can bring time into the model of consciousness: https://github.com/rand3289/PerceptionTime

Here are some of my own ideas: https://github.com/rand3289/PerceptionTime

It's super easy to publish a static site like the resume with GitHub Pages. Just check out the docs.

GitHub Pages: Host your static websites directly from your GitHub repository.

As per many other comments, it sounds like a static site generator like Hugo (https://gohugo.io/) or Jekyll (https://jekyllrb.com/), hosted on GitHub Pages (https://pages.github.com/) or GitLab Pages (https://about.gitlab.com/stages-devops-lifecycle/pages/), would be a good match. If you set up GitHub Actions or GitLab CI/CD to do the build and deploy (see e.g. https://gohugo.io/hosting-and-deployment/hosting-on-github/), your normal workflow will simply be to edit markdown and do a git push to make your changes live. There are a number of pre-built themes (e.g. https://themes.gohugo.io/) you can use, and these are realtively straightforward to tweak to your requirements.

Ideal for open source projects, docs sites, and portfolios. GitHub Pages

Github Pages: Link to Github Pages

Once you have all the documentation worked out a place to host it will be necessary. Some documentation generation may have ties in with specific hosting sites. Read The Docs' support for Sphinx and other documentation tools is one example. GitHub pages can be useful for GitHub hosted projects as it integrates well with GitHub Actions CI/CD deployments.

If you use GitHub and need to host a static website, consider GitHub Pages. Free for one site Stored on a GitHub public respository Deploy via web interface, or Git 100GB/month free bandwidth

https://pages.github.com/ https://docs.github.com/en/pages https://docs.github.com/en/pages/quickstart https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll

There are plenty of other hosting options you could use instead, such as GitHub Pages.

Functionally github.io just presents whatever you throw into the repository as the root directory of a site, github themselves host a very good, basic outline of how to set up a site on github.io.