Make some small improvements

[Moosems]

I wonder if there’s a way to create a base page and then just modify certain sections similar to how flask does it.

[not-nef]

i am currently in the middle of making the dynamic member list, can i wait with this until thats done? there will probably be a lot of merge conflicts

[Moosems]

i am currently in the middle of making the dynamic member list, can i wait with this until thats done? there will probably be a lot of merge conflicts

Just make it into a js script that puts it into in a div with the id members. I can integrate that easily.

[not-nef]

im already pretty much done ill just have to do some testing, but i exceeded my api rate limit and have to wait a bit

[Moosems]

All you need to do is make tons of these divs and then paste it into the document 😉.

[not-nef]

i think you get what i want to do when you see it

[Moosems]

If it's just a JS modification you can add to landing.js and it should work fine 😄.

[not-nef]

https://github.com/Futura-Py/futura-py.github.io/blob/main/scripts.js

you see what i did?

[not-nef]

it dynamically generates the divs which is cool

[not-nef]

what do you think?

[Moosems]

I like it.

[not-nef]

i do want to keep the modern feel for this so i want to make some adjustments once you are done

[Moosems]

Have my changes not been modern looking?

[not-nef]

i think the boxes and the text shadows (especially on the paragraphs) dont look that great, although i get why you made the boxes, but well see

[Moosems]

I thought the shadows looked nice 🙁. The boxes were made cause of contrast issues

[not-nef]

i was aware of the contrast issues and was just gonna make the links another color, but the shadows look pretty confusing on the paragraphs, they can stay on the other elements but i dont like them on the paragraphs

[not-nef]

let me know when youre finished with this pr so that i can make some adjustions

[Moosems]

Ok, you're free to mess around with it for a bit.

[not-nef]

im done with coding for today, ill look at it tomorrow

[im-coder-lg]

Can we soon change to Astro? I have tried it, and it is robust and very fast. I think we can integrate some cool features with it. Of course, someone gotta know CSS.

[Moosems]

Y'all really love making simple things complicated, huh?

[im-coder-lg]

I don't know, it just happens in my case. All the time. But then I would have clarity, and I don't know a deuce about how that happens too. But I have used Astro, and it is kinda simple. The main files use JSX if I am not wrong, and it actually allows HTML in the code, if laid properly. I use it on my Astrosite. It is the literal repo name btw.

[not-nef]

Can we soon change to Astro? I have tried it, and it is robust and very fast. I think we can integrate some cool features with it. Of course, someone gotta know CSS.

i see no need for it

[im-coder-lg]

Well, I do. My idea isn't fully formed yet, but the way I see it, if we make the website out of Astro, it would be loads faster. Plus, there are many plugins for Astro out there, we can use them. HTML and JS are used in the same file, mind you. Same with Markdown, we can use Markdown and JavaScript. So, any cool embeds that we have to script can be done immediately along with running HTML side-by-side. I will try this idea later, it is prone to work.

[not-nef]

well you can try it on a different branch and ill look at it

[not-nef]

i need some help: i cant get the "about us" and "projects" to align left. i have been messing around with the css for about half an hour and couldnt get it to work. can anyone of you help me?

[Moosems]

Well, I do. My idea isn't fully formed yet, but the way I see it, if we make the website out of Astro, it would be loads faster. Plus, there are many plugins for Astro out there, we can use them. HTML and JS are used in the same file, mind you. Same with Markdown, we can use Markdown and JavaScript. So, any cool embeds that we have to script can be done immediately along with running HTML side-by-side. I will try this idea later, it is prone to work.

Please tell me how adding extra bloat would make it load faster then barebones html 😄.

[not-nef]

and html is just markdown on crack so why would we need it

[sumeshir26]

Well, I do. My idea isn't fully formed yet, but the way I see it, if we make the website out of Astro, it would be loads faster. Plus, there are many plugins for Astro out there, we can use them. HTML and JS are used in the same file, mind you. Same with Markdown, we can use Markdown and JavaScript. So, any cool embeds that we have to script can be done immediately along with running HTML side-by-side. I will try this idea later, it is prone to work.

Why do we need to over-engineer such a simple website? I dont see any speed problems now, and the codebase isnt that hard to work with.

[sumeshir26]

i need some help: i cant get the "about us" and "projects" to align left. i have been messing around with the css for about half an hour and couldnt get it to work. can anyone of you help me?

Maybe using <div allign="left">?

[not-nef]

well that would be embarrassing if i missed that, i will try it today

[Moosems]

Why do we need to over-engineer such a simple website? I dont see any speed problems now, and the codebase isnt that hard to work with.

When I say I dislike a suggestion, this is how k feel 95% of the time by the way. I don't dislike y'all's suggestions but y'all really have a knack for over complicating the applications.

[im-coder-lg]

Well, I am not trying to overcomplicate stuff. I think you are thinking we get a template. We are absolutely NOT doing that. Instead, we could just use the present code in the Astro files. Oh, I almost forgot. Astro files have a .astro extension, and by using a plugin, we might be able to transcribe the HTML/Markdown/JSX into Astro files on build.

And Astro doesn't complicate stuff. Rather, I believe the code built will be just HTML and JS that is very rapid. Astro wouldn't have to play a part in the build files, it plays a part in the source code. You can see my most recent website's source code - it is rapid even with that many files.

Yeah, still a work in progress. But that is with a template. Imagine the speeds we could get if we create our own theme and add our type of icons? I'm speaking Font Awesome(I heard there was a free edition?), MUI, and our custom SVG icons if we want. That is where JS could help. But this is my pitch, you guys should decide.

[not-nef]

i need some help: i cant get the "about us" and "projects" to align left. i have been messing around with the css for about half an hour and couldnt get it to work. can anyone of you help me?

Maybe using <div allign="left">?

didnt work. @Moosems you have any idea

[im-coder-lg]

https://github.com/Futura-Py/futura-py.github.io/issues/2#issuecomment-1719326873

And yeah, I'm testing Astro for this website. It will work, and I know it. On my fork, on another branch in it.

[not-nef]

ya boy is 15 now

[sumeshir26]

ya boy is 15 now

Happy Birthday!

[im-coder-lg]

ya boy is 15 now

Happy birthday bro!

[Moosems]

Happy birthday my dude!

[im-coder-lg]

Oh, and a bit of a side note, which ofc can be checked later: https://github.com/Futura-Py/futura-py.github.io/pull/2#issuecomment-1719326873

I'm testing Astro as well as recreating the website we are using, with CSS and JS, plus some interesting goodies I found, like a card view that seems similar to the one used in Next.js, and more. I'll test and show my results later. It is still snappy.

[Moosems]

@not-nef I'm fine with the logo being to the side but can we have the different items centered and keep the sticky header? I worked really hard getting the sticky header in particular and want to keep it. To be honest, could we just keep it how it was (I'm fine with the color change)?

[not-nef]

thanks yall for the birthday wishes! i just liked the nav bar being like over the banner your know? we can change it back if you like. i do want the items to align left you know. it would be awesome if you could get it to work. but if you dont thats fine. well find a solution

[Moosems]

I'm updating the sticky header now, please don't touch it afterwards.

[Moosems]

I recommend taking a look at apple.com and their navbar.

[not-nef]

I'm updating the sticky header now, please don't touch it afterwards.

alright, tell me when i can lay my hands on it again

[im-coder-lg]

Uhh, guys? The astrosite's going well... I'll try to furnish it to make it look like the present version of our site, then add some more stuff once this PR is merged. I used just HTML if I think about it. Yeah, CSS and JS are included.

[Moosems]

@im-coder-lg You're keeping my navbar right?

[im-coder-lg]

Well, hell yeah. You guys finish this PR. @Moosems see, when I was creating the website with Astro, I realised that the Astro files for site generation use HTML, JS and TS.

There is the frontmatter-like part where you put your JS code, perhaps imports to use later, then you use HTML, and wherever needed, use JS or TS. The way I have done is taking most of the code from here, using it there, and slowly but surely refactoring it so that it not only becomes a 1:1 copy of this, but also can use some neat features like Astro Cards, which is basically the Card UI in HTML(tell me if I am warm) and more. There is an unseen advantage to this: adding JS scripts are much more easier, less painstaking, and moreover, we can add plugins like buttons, icons, symbols and more. I have tested this out on multiple websites on my profile. There are so many, I seem to have lost count(my most memorable one was my Jekyll blog, until I deleted that. It had over 200 commits.) I saw my Next.js course blog, and I saw this: https://dub.sh/EUAhImA

Had to shorten it, so that I can now refer to it anywhere. Anyway, it's my website, where I learnt basic Next.js. Anyway, what I want you guys to know is that although the website might be statically generated, I think the API renders along with the server, making it a tad slow. But hey, :shrug: it's your decision now, I gave the idea. What do you guys think about this?

[not-nef]

should we maybe get rid of the banner for the base and only keep it for that main page? it takes up like half the screen

[not-nef]

also can i mess around with it a bit?