Today:
- A collection of Markdown JSX files (mdx) go in, and a static website bundle comes out.
WIP / "Tomorrow":
- A collection of Markdown JSX files (mdx) go in, and a static website bundle ✨ powered by content-aware conversational artificial intelligence ✨ comes out.
The Markdown JSX files support a novel sub-page format like so:
# Welcome to my page!
I like <FlowersLink />!# Flowers
I sure do like flowers. My favorites are roses and tulips :)The <FlowersLink /> JSX element will automatically be generated by the "framework"; it goes by filename and appends Link. The <FlowersLink /> appears as flowers and when clicked causes the webpage to navigate to a sub-page using React Router
There's a wiki! Additionally, Joe is cataloguing additional AI research material here.
Here's a cool page from the wiki showing the control flow diagram for updating the knowledge base for the large language model, as well as keeping parity with existing documents across the vector database and storage solution.
- Vite - https://vitejs.dev/ - An alternative to webpack; provides a development environment with hot module reloading, and bundles all html/javascript/css/assets into a static web bundle.
- MDX - https://mdxjs.com/ - A cool abstraction that wraps markdown with JSX component support.
- React, React Router
We are working on integrating large language model support for the documents, so that a user of the client may ask the document questions about itself. For more information, see:
- Austin Rafter -- austin.rafter14@gmail.com
- Code repo clone url:
git@github.com:austinrafter/interactive-resume.git
- Code repo clone url:
- Joseph Burger -- candyapplecorn@gmail.com
- Code repo clone url:
git@github.com:candyapplecorn/interactive-resume.git
- Code repo clone url:
Joseph's gone and forked this repo. In order to push commits to a fork, he's found this as the most convenient method.
Assuming two remotes,
A: git@github.com:austinrafter/interactive-resume.git
B: git@github.com:candyapplecorn/interactive-resume.git
- Push the commits up to the current remote
A. - Change the current remote to
B:git remote set-url origin git@github.com:candyapplecorn/interactive-resume.git - Merge the previous remote's code into local:
git merge origin git@github.com:austinrafter/interactive-resume.git main
(not 100% sure this command is right) - Push the local up to remote
B
And that's how you can keep a fork up to date with another branch! Don't forget to switch the remote back to the original branch when you're done 😊
List remotes with their URL's: git remote -v
candy/interactive-resume git@github.com:candyapplecorn/interactive-resume.git (fetch)
candy/interactive-resume git@github.com:candyapplecorn/interactive-resume.git (push)
origin git@github.com:austinrafter/interactive-resume.git (fetch)
origin git@github.com:austinrafter/interactive-resume.git (push)This is handy because it shows which remote is currently set as the default remote.