Documentation

Previously of its versions, documentation contains a lot of things. Well, most of the time it contains documents and series of resources that is originally me-made, which is actually kinda nice. Generally I would treat this as a repository for stuff that either I have done, or simply stay there of impotency, or simply there as its sole purpose of presentation. Well, certainly it is.

For the new version, it is where I do my own reorganization of different contents, and the clusters of website and constituent purpose-dependent space where I organize my content of. Think of it as subdivision specialization, but currently without a correct notion for controlling and organizing them. Indeed, the facility, wide and large, is numerous, but then we have to organize them here to reveal what is said about the current infrastructure; and whether I have crossed the storage limit of the landlord.

The main documents

The main documentation site for now, is obviously this site on its own, my personal website. The research hub in which contents will be written down would be organized in this research sub-partition under the domain. There is also AML as a deployment central zone, holding everything together (almost so).

For main projects, we have the now-postponed Neural Network (re)Design document (I will soon migrate it over to GitLab). For other in-progress works, we have a few options, bust most of them are and will be hosted on either eigenmane GitHub, mainly this domain (to be deployed) and for completeness, this repository for a neuroscience topic preparation. That said, as of 2026, it has been migrated to GitLab.

Other documentation flavours would be preferable to be published onto GitLab or Netlify. Specifically, with the domain intrinsic of Netlify, and using their own free plan (might be upgraded later on). THough, I would say that I use Netlify for hosting contents or files rather than works or public organization.

Planned

For planned content, I am exploring options regarding the use of forums, XWiki, and so on infrastructures, for example, lifting myself out of primitive notion and start using Docker, They are there, for the purpose to host a new knowledge sharing and organization idea that I have in mind, and also for documentation of knowledge and projects, much similar to CV and others. Further on, using that, we can also use the infrastructures for hosting frameworks and further research framework that would be detrimental in advancing the theory that is in mind. That is:

  • A presentation website.
  • A XWiki website infrastructures, plus a software-domain deployment of a research network (?) for collaboration, I guess? Right now it is a hurdle because of research communication between fields or so is rather hard at a distance.
  • A CV website and PDF-generation option for offline uses, or legacy stuff.
  • The, tech-stack and tools I want to use that is not available elsewhere.

Not too much, but the list can always go wider.