got basic site working with extism for using enhance wasm in go

Author: Benanna2019

Dockerfile

@@ -27,4 +27,5 @@ COPY --from=build /bin/main /
 COPY --from=build /src/web/static /web/static
 COPY --from=build /src/web/custom-elements /web/custom-elements
 COPY --from=build /src/wasm/enhance-ssr.wasm /wasm/enhance-ssr.wasm
+COPY --from=build /src/content /content
 ENTRYPOINT ["/main"]

Taskfile.yml

@@ -67,7 +67,8 @@ tasks:
         --build.bin "tmp/bin/main" \
         --build.delay "20" \
         --build.exclude_dir "node_modules,data,public" \
-        --build.include_ext "go" \
+        --build.include_ext "go,mjs" \
+        --build.include_dir "routes,handlers,web,content" \
         --build.stop_on_error "false" \
         --misc.clean_on_exit true
 
@@ -80,7 +81,7 @@ tasks:
         --build.delay "100" \
         --build.exclude_dir "" \
         --build.include_dir "$STATIC_DIR" \
-        --build.include_ext "js,css"
+        --build.include_ext "mjs,js,css"
 
   live:
     deps:

content/2020-08-13-coding-bootcamp-begins.md

@@ -0,0 +1,31 @@
+---
+_id: "511fdb02-998a-4d86-9abb-128654f00c02"
+title: "Coding Bootcamp Begins"
+published: "August 13, 2020"
+slug: "coding-bootcamp-begins"
+description: "I started coding bootcamp with Jack Russell Coding School"
+categories: ["Career Changer", "Coding Bootcamp"]
+author: "Ben Patton"
+authorImage: "https://cdn.sanity.io/images/nfspldzq/production/3ceeda54221c7c0614ecc51f955c7be39a1da34e-512x512.jpg"
+type: "Blog"
+---
+
+_This is an article that I originally wrote for my Wordpress site but have moved here._
+
+I started a new thing on August 3rd. So consider this a journal of sorts.
+
+I started coding bootcamp with Jack Russell Coding School. I had been waiting for this for months to start a coding bootcamp so it is no surprise that I am late on this blog. I will detail the process of settling on a bootcamp in a later blog.
+
+As is the nature of a bootcamp, from what I hear, we were welcomed to the class and began learning code immediately. This bootcamp is teaching us to be Full-stack Web Developers. That does mean something but I will define it later.
+
+We started with HTML. Whether it is important or not to you, dear reader, html stands for “hyper text mark-up language.” The best way to think of html is like writing a word document that is housed on the inter-webs. A word doc. is formatted uniquely, therefore a html file must be formatted in a specific way. Here is a sample document and the boiler-plate (necessary formatting) for it.
+
+_\*I took out the boiler plate info here._
+
+If that looks strange, it is ok. This is just basic and necessary code for beginning an html document. HTML feels very like writing a word doc meaning it can feel very tedious for very little reward. That does all change but it will take time to learn the other code to make it all look nice.
+
+Point is, learning to code, even though I had done a far amount of coding before, is challenging.
+
+The next blog I will get into CSS.
+
+– Ben

content/2020-08-18-css-and-div-s.md

@@ -0,0 +1,34 @@
+---
+_id: "7180c247-be59-40f2-90ac-c75cd6d3c7b6"
+title: "CSS & Div's"
+published: "August 18, 2020"
+slug: "css-and-div-s"
+description: "...in the beginning stages of learning how to do web development, we learned that there are so…many…div’s"
+categories: ["Coding Bootcamp", "Career Changer", "Junior Developer"]
+author: "Ben Patton"
+authorImage: "https://cdn.sanity.io/images/nfspldzq/production/3ceeda54221c7c0614ecc51f955c7be39a1da34e-512x512.jpg"
+type: "Blog"
+---
+
+_This is an article that I originally wrote for my Wordpress site but have moved here._
+
+Day two through the end of Week one we were learned how to write efficient html and CSS. Since we were in the beginning stages of learning how to do web development, we learned that there are so…many…div’s. A div is an element that essentially divide’s the page into sections. It can get super confusing, when using just basic code and not templates, because your html page can start to look like the matrix.
+
+To the div you can assign classes which help to style the layout of your web page through the use of CSS. A div with a class or id is written as follows: `_div class=”my-div”></div_`
+
+Then in your CSS, either in a new file called filename.css or in the html file using _style_ tags, you can style your code. Coder’s have a love hate relationship with CSS. If you enjoy making things look nice, CSS will not frustrate you as much. If you want to make things work, CSS is beyond frustrating. It is not that it is too hard to learn, necessarily, there is infinite possibilities for how you can style things. So if you like fonts, colors, etc, (think graphic design even though graphic designers might not like me saying that) then CSS is your cup of tea but you can add any sweetener and doctor up your tea however you like, or drink coffee. Hopefully the point has been made. My last comparison, if you are an artist, in the realm of painters because everyone can consider themselves and artist, then you would enjoy CSS. Color wheel’s and spectrums and the like.
+
+So after we learned a bit of CSS we created the basic first page of a website. For day 3 this was a feat for most of us. It took us the majority of the day but using html and CSS we knew we made it look about as close as possible.
+
+By the end of the week we had learned enough to recreate a the landing page of a website. We did this by recreating the Airbnb landing page.
+
+Reflections:
+
+- Even though it was a lot of tedious work using basic HTML and CSS, it was nice to see what we were able to do with not a lot of tools.
+- Personally, it is very nice to be doing something that takes a lot of time to complete. Obviously the goal is to get better and more efficient but it is nice to know what I am to be doing and work at it till it is completed. This is how I like to work and it took me a long time to figure that out before coding bootcamp.
+- As my next blog will deal with some Javascript, I can go ahead and say I am excited to become more proficient with this stack and learn frameworks that serve to help us become better developers.
+- Someone might ask the question, “why not just learn the frameworks and then not have to deal with all the frustration without them?” My understanding is that if we went straight to frameworks we would not understand most of what we are using the frameworks for. So we are building a very foundational level of understanding and then getting into frameworks. Once we do, even though there will be a learning curve, it will be a lot smoother than if we just tried to understand a framework before knowing the basics. My best analogy at this point, which I am sure someone could refute, is that it is like trying to be a mechanic without understanding anything about cars.
+
+Till next time.
+
+– Ben

content/2020-08-23-javascript-beginnings.md

@@ -0,0 +1,46 @@
+---
+_id: "681d45fb-c392-4f19-aa7c-8f47664312b3"
+title: "Javascript Beginnings"
+published: "August 23, 2020"
+slug: "javascript-beginnings"
+description: "I am now seeing the value of having kept this blog up either on a daily"
+categories:
+  ["Coding Bootcamp", "Career Changer", "Junior Developer", "Javascript"]
+author: "Ben Patton"
+authorImage: "https://cdn.sanity.io/images/nfspldzq/production/3ceeda54221c7c0614ecc51f955c7be39a1da34e-512x512.jpg"
+type: "Blog"
+---
+
+_This is an article that I originally wrote for my Wordpress site but have moved here._
+
+So we just finished week 3 of bootcamp and I am now seeing the value of having kept this blog up either on a daily, every other day or weekly basis. The nature of the immersive bootcamp is that where we are now, all I know is I know more than I knew three weeks ago.
+
+Anyways, at some point towards the end of week 1 and by the start of week 2 we began to learn Javascript. Javascript, like most other languages, is incredibly vast. I will list a few things about Javascript, that go with what we learned in week 2 because week 3, which will be the next blog, was quite intense (Asynchronous Javascript anyone?).
+
+So, week 2, the basics of Javascript.
+
+- Strings and numbers (literally words and numbers)
+- Booleans (uses evaluators like `>`, `<`, `<=`,`>=`, etc to determine true or false)
+- Variables (holds something like a ‘word’ or number or eventually lines upon lines of code)
+- If-else statements (if ‘this’ then do this, else ‘do this’) (you can add if conditions within if conditions which are labeled as ‘else if’ statements)
+- Loops (while loop – while ‘this condition’ do this) (for loop – for ‘this condition’ do this). This is an incredible over simplification.
+- Functions – take everything above into a function and every time you want to use that function you can just call the function. The functions definition is all the code you give it (again and incredible over-simplification).
+- Array’s and Objects (Array’s are a list of values which are placed inside [ ]).
+- Objects need their own line and sub-line.
+- Objects are recognized by `{ }`. So the most confusing thing is that Objects are Array’s.
+- Array’s have values [1, 2, 4, 24, 465].
+- The first value in an array is 1. 1 is at an index of 0.
+- So if you want to pull 1 from the array it looks like array[0].
+- If you were to type the array by index it would look like Array[0:1, 1:2, 2:4, 3:24, 4:465]
+  HOWEVER!
+- That format is what an Object is. Object `{Key: value, Key: value}`.
+- Array’s do not get formatted/typed by index. The index is understood
+- Confused? Me too, google it.
+- Putting html, css and javascript together.
+- Made a calculator. A lot harder than it sounds.
+
+So, that is most of week 2. Like I said, next week will be a little deeper but it might end abruptly due to the complexity and melting of the brain when thinking about Asynchronous programming.
+
+Till next time,
+
+– Ben

content/2020-08-31-coding-bootcamp-week-3.md

@@ -0,0 +1,35 @@
+---
+_id: "e4b8fd6d-3e40-45c5-8fa4-acf860bae08d"
+title: "Coding Bootcamp - Week 3"
+published: "August 31, 2020"
+slug: "coding-bootcamp-week-3"
+description: "This week was one of the more difficult conceptually"
+categories: ["Career Changer", "Coding Bootcamp"]
+author: "Ben Patton"
+authorImage: "https://cdn.sanity.io/images/nfspldzq/production/3ceeda54221c7c0614ecc51f955c7be39a1da34e-512x512.jpg"
+type: "Blog"
+---
+
+_This is an article that I originally wrote for my Wordpress site but have moved here._
+
+This week was one of the more difficult conceptually. I say that because I also started writing my functional programming blog which takes the concepts of conceptuality and gets more complex conceptually (if that was hard to follow….you understand).
+
+_\*If someone reads this, wants to correct me/help me with this, feel free._
+
+Anyways, this week we looked at the call-stack and asynchronous functions.
+
+What I am about to say is my best attempt at explaining async functions as a newbie. You’ve been warned.
+
+So, remember, all of this is within Javascript. Javascript reads all of its code synchronously. That means it reads it top down. This never changes within Javascript.
+
+So async programming is basically programming that is being run somewhere else while Javascript finishes running its synchronous code. Asynchronous code is executed in the browser and even though it maybe finished running before all the synchronous code is finished, it is placed into the callback queue. This means that it will not run until all the synchronous code is finished and then the first async code in the queue will be executed first (FIFO – first in first out).
+
+There are also these things called promises within all of this. Promises are more important than your typical async code and will be placed into the 'microtask' queue which is run before the callback queue.
+
+So right now, as we are still very new to learning, our code can get a bit muggy trying to think through this whole call-stack, call-back, 'microtask' queue flow. But it’s part of the fun of learning to code (look for that blog to come soon).
+
+The next blog in the bootcamp series will be the reflection on week 4 followed by “The Fun of Learning to Code.”
+
+Til next time,
+
+– Ben

content/2020-09-01-coding-bootcamp-week-4-functional-programming-part-1-and-part-2.md

@@ -0,0 +1,43 @@
+---
+_id: "cee85c0a-67c0-4ffd-856f-1201637685b4"
+title: "Coding Bootcamp: Week 4 - Functional Programming Part 1 & Part 2"
+published: "09-01-2020"
+slug: "coding-bootcamp-week-4-functional-programming-part-1-and-part-2"
+description: "So my goal is to keep this super, I mean incredibly super, basic"
+categories: ["Coding Bootcamp", "Career Changer"]
+author: "Ben Patton"
+authorImage: "https://cdn.sanity.io/images/nfspldzq/production/3ceeda54221c7c0614ecc51f955c7be39a1da34e-512x512.jpg"
+type: "Blog"
+---
+
+_This is an article that I originally wrote for my Wordpress site but have moved here._
+
+Functional Programming Part 1:
+
+🤔
+
+Functional Programming Part 2:
+
+For anyone who reads this who is like “oh no, another perspective on functional programming” just know that I am not necessarily offering guidance but just reflections on a week of learning it so feel free to comment or help understand.
+
+So my goal is to keep this super, I mean incredibly super, basic.
+
+Of the few things we have learned so far, one of the seemingly most important is this:
+
+In functional programming you must use pure functions. What this means is that a function cannot be dependent upon anything outside of the function for its ‘functionality.’ If so it isn’t pure. The common comparison used is comparing functional programming to calculus. Functional programming is highly mathematic so it makes sense (and here we are talking about the way functional programming works is mathematical but you do not necessarily have to have a deep understanding of math to use it).
+
+So far it seems that functional programming is a paradigm of programming that seeks to make code more readable. You can put functions within functions but the goal in mind is always readability and understandability for our code.
+
+Back to the use of the word conceptual, if what I am writing seems very conceptual, thats because it is. It can be highly practical but functional programming is a mind-bending endeavor.
+
+A much clearer explanation of functional programming as well as a deep dive into it can be found at the link below. Kyle Simpson makes functional programming reasonably understandable for ‘the other guy’ (me).
+
+The main point and take-away of this post is this:
+
+As coders, programmers, software-engineer’s, web-developer’s, etc, a great goal to have is readable and reasonable code. A bunch of for loops `(for (let i = 0; i < arr.length; i++)` with if statements in adds line upon line to files and makes it difficult to understand. If we can create functions that explain themselves and put functions within other functions so that we can see what we are doing on a SINGLE line of code, that is a much better alternative for those that may read our code whether on the job or just our repositories of code out there for the world to see.
+
+I might say more about Functional Programming at a later time so there is no soon-to-be part 3. I know how much that bums anyone out who reads this 😏.
+
+Til next time,
+
+– Ben

content/2020-09-07-coding-bootcamp-week-5.md

@@ -0,0 +1,35 @@
+---
+_id: "d26f50fa-9d37-4745-919e-73993aa9cd86"
+title: "Coding Bootcamp - Week 5"
+published: "September 7, 2020"
+slug: "coding-bootcamp-week-5"
+description: "It is honestly hard to believe we are five weeks into our coding bootcamp"
+categories: ["Coding Bootcamp", "Career Changer"]
+author: "Ben Patton"
+authorImage: "https://cdn.sanity.io/images/nfspldzq/production/3ceeda54221c7c0614ecc51f955c7be39a1da34e-512x512.jpg"
+type: "Blog"
+---
+
+_This is an article that I originally wrote for my Wordpress site but have moved here._
+
+It is honestly hard to believe we are five weeks into our coding bootcamp. So two quick things: This will be the typical blog of reflecting on this past week. I mentioned in a previous post that I would write an article on the process of choosing a bootcamp as well as an article on reflecting on the bootcamp so far. I plan to have those done this week and scheduled for Wednesday and Thursday.
+
+Week 5 Review
+
+This week we began learning backend, and in a small way, we are now able to do full-stack applications. Meaning we can implement web applications using both front-end and back-end technologies.
+
+We did this primarily by installing some software that enables us to create our own databases and have api calls to our databases that are then able to be rendered on screen.
+
+So we began creating a blog. Why a blog? A blog shows, on a basic level, that we are able to implement what is necessary for a website to work. We can make our server and create our database that our front-end is able to make calls to and therefore display the information on screen. Specifically for different users we can display their blog and then create more blogs for that user and delete them. We still have a good ways to go on begin able to edit the blog and use authorization and authentication, which we will learn next week, week 6.
+
+By the end of week 6 we will be able to call from databases using Sql and Mongo and other databases as well as implement authorization and authentication for the blog site (we call our Rockbottom blog since we are at rockbottom of our coding journey, feel free to laugh here. There needs to be some way of styling text to indicate laughter when being sarcastic).
+
+After that we will move on to React and then Material UI, and we as a class are counting down the days until we get to use those things. We are doing the work now in the most difficult way SO THAT when we get to those things we know more of what we are doing and can adapt quickly.
+
+This week was a refreshing week after functional programming last week.
+
+So, look for those two blogs I mentioned on Wednesday and Thursday.
+
+Til next time,
+
+– Ben