theoludwig/.profile
1
1
Fork 0
mirror of https://github.com/theoludwig/theoludwig.git synced 2025-05-29 22:37:44 +02:00
Code Issues Releases Activity

fix: better resume

Browse Source
This commit is contained in:
Divlo
2022-11-19 20:24:13 +01:00
parent 014044573a
commit c88887a322
14 changed files with 1429 additions and 2348 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
posts/hello-world.md
View File

@ -35,18 +35,11 @@ In this section, I will explain what technologies I used to make this blog, and
The code of this website is open source on [GitHub](https://github.com/Divlo/Divlo), so you can see the code and contribute to it.
I decided to keep things simple, here are the 2 main features missing on my blog:
- Comments (you can interact with me on my Twitter account)
- Views counter
That not mean that these features will never be implemented, but to avoid the need of a database now, I dropped out these features.
### Technologies
- [Next.js](https://nextjs.org/)
It allows to have a server-side rendered website, that means that it is faster and easier to have a good SEO (Search Engine Optimization) than a SPA (Single Page Application).
It allows to have a server-side rendered website, that means that it is faster and easier to have a good <abbr title="Search Engine Optimization">SEO</abbr> than a <abbr title="Single Page Application">SPA</abbr>.
- [MDX](https://mdxjs.com/)

4
posts/thream-v1-0-0.md
View File

@ -53,9 +53,7 @@ Since the project is mainly developed during free time (mainly on weekends), the
- The **client** part, called **frontend**, what **the user sees on the screen**, such as forms, buttons and all the **graphic elements** with which the user can interact from a browser.
<span className='flex flex-col items-center justify-center'>
![HTTP Communication Schema](../public/images/posts/thream-v1-0-0/http-communication.png)
</span>
![HTTP Communication Schema](../public/images/posts/thream-v1-0-0/http-communication.png)
This design allows the separation between the client and the server, as long as they both structure their communication according to the <abbr title="Representational state transfer">REST</abbr> architectural guidelines, using the <abbr title="Hypertext Transfer Protocol">HTTP</abbr> protocol, they will be able to communicate with each other, which makes it possible to work independently on the backend and on the frontend using different technologies and skills, really useful in teamwork.