-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🚀 : Better Footer Design #48
Comments
should be added.
|
@jakebogan01 i think you can deal with this issue as well :) |
@xuelink Yeah, no problem I can take care of this one as well. |
@jakebogan01 Thank you very much ! |
@xuelink No problem |
@jakebogan01 As a reminder, please test it with mobile version and narrow browser as well, its kind of tricky when you are doing it :) Let me know if need any help or further questions, thank you ! |
@xuelink Thanks for the tips, I'll try my best to make sure the new footer design update looks good |
Hey @jakebogan01, I hope you're doing well! I've been thinking about our website lately, and I'm really excited about the idea of creating a v0.3 version with a fresh perspective. I believe there's so much potential to enhance the user experience and overall aesthetics. I'd like to propose a collaborative effort where you can take the lead on redesigning all the components from your unique viewpoint. Your creativity and expertise could truly breathe new life into our website. To facilitate this process, I'm more than happy to grant you admin rights to the repository. This will give you the freedom to work on a new branch and implement your vision without any constraints. I understand that you're familiar with the general structure and functionalities of the website, which will undoubtedly expedite the development process. Let's embark on this journey together and create something remarkable. Your input and dedication will be invaluable in shaping the future of our online presence. Looking forward to hearing your thoughts and kicking off this exciting project! |
@xuelink Thank you for the offer, I am honored to be apart of the journey. I would like to help continue to improve the success and growth of the site. I will try me best to spare as much spare time I can and help with the front-end redesign. I would like to point out a few things. I'm not sure if you are aware of Tailwind CSS, it is a common and most popular utility CSS framework that I would highly recommend to use in the v0.3 of your site (only if you approve of course). It makes the styling much quicker and cleaner. Also, you can combine this with a UI library such as Skeleton UI. Skeleton UI only works with Sveltekit and is an amazing UI made with Tailwind CSS. Although it might be a hit or miss trying to implement it into an already existing project. Usually you are meant to create a new project built by Skeleton. However, it is still possible to implement itself into existing projects. With that being said, if you choose to not use Tailwind, that is 100% fine. I can help maybe create a few mockup redesigns of the website and we can collaborate on changes to be made before I implement them into the code myself. |
@jakebogan01 Tailwind CSS library is indeed very successful and widely used, feel free to use it. No issues, no problem. It would be great for me to get experience and learn about tailwind through this process as well. Additionally, benefiting from your knowledge will surely accelerate and guide us. Thank you! |
@xuelink No worries, adding Tailwind to the project is very easy. I never added Tailwind to a project that already has SCSS, so if it doesn't work out then its not a huge problem, we would just stick with the SCSS you already have. I can continue to make design adjustments, especially from the issues tab, as well as normal adjustments. I can make some mockups/prototype designs and share them with you and get your opinion on any components that may need some help. |
@jakebogan01 Ok, feel free and its also ok to convert them all if needs, no worries! You have a part of |
@xuelink Thank you, I'll do my best |
Also, we can move out blog to Medium? @pizofreude suggests that it's time to open a Medium page and migrate our blog there. What do you think @jakebogan01 ? It makes this repo more comfortable to work if we wont have inline blog feature, but at the same time, its not helpful for SEO, i dont know :) What do you suggest ? |
@xuelink just to make sure I understand, your thinking of making a separate page or website for the blog? |
@jakebogan01 I mean to make outsource blog here: https://medium.com/ or keep it within the webpage as we currently have |
@xuelink Oh okay. I'm not really sure, personally I never made nor owned a blog nor managed a business blog before, so I wouldn't know the best company strategic strategy to go with to be honest. |
I would highly advice to maintain our current subdirectory blog: https://langx.io/blog/ and only create a new subdomain and linked it to Medium when we create an official one for LangX. This does two things: Keep current SEO and improve it via the new subdomain re: blog.langx.io for our official Medium blog. It would be very intuitive if we can add auto-publish from our subdirectory blog to our subdomain blog. I know this feature is available as plugin in Wordpress. However, Angular is totally new tool for me and currently I'm not well-versed on how to implement it. For blog structure with SEO optimization, my proposal is still WIP (not enough time to work on it now, need to clear more on my pipeline). We can add backlink of this subdomain blog in the footer of LangX as follows: |
I like that idea to keep up with both of them. Automation is no problem i can donit but is there any danger zone here because im worried about SEO, google spiders may decrease our website value because we have duplicate content with Medium? 🤷🏻♂️ When we add backlink within Footer section then it may work perfectly as you said @pizofreude |
Regarding SEO for republishing blog content from our subdirectory to subdomain, I have seen many companies do it. If memory recalls correctly, we have someone from our Discord who is a master SEO. I can't recall his/her name though. Do you know who I'm referring to? Republishing content from your website's subdirectory to a Medium subdomain can indeed have implications for SEO, particularly concerning duplicate content. Here are some key points to consider:
In summary, while republishing to Medium can help with visibility and reaching a broader audience, it's important to carefully manage the SEO aspects to ensure that your website's value isn't diminished due to duplicate content issues. Using canonical tags and considering the strategic goals of your SEO and content marketing efforts will be crucial in navigating this potential danger zone¹²³. Source: Conversation with Bing, 4/18/2024 May Canonical Tags be in our force. |
@pizofreude OK, i got the point. If you remember that you see some of the companies do blog for both, its ok, no need to overthinking about it aha. Besides that, i remember that SEO Guy but i dont want to ping him, he is trying to start a new career in US so nowadays he is super busy. It's ok, Medium is the best for blogging and SEO as well but we should have enterprise solution i think. it costs 5bucks a month :D |
Custom domain and blog repost automation isn't really necessary for now. We can opt for the free tier Medium and manually republish the canonical link there. Once we hit >5 blogs weekly basis, then we'll think about the enterprise solution. |
@pizofreude Sounds great! But can't open any publicitaions with a free tier, it redirects to https://medium.com/plans |
No need to create our own publication, just publish without publication. It makes more sense to apply for "language-related" existing publications in Medium instead for better reach. Creating our own publication starts from 0, unless we have existing email list for it. We don't want to create a dead publication like LingQ and hence wasting resources. |
@pizofreude they have both By the way i changed my username to langx :D is it ok ? |
By the way, i liked the design of lingq.com , it reminds me duolingo.com. You are free to do but its just for your information @jakebogan01 |
correct, so does many other companies I've seen. They always use both subdirectory and subdomain for blog as noted before. Medium uses email as sign up option, it would be better if we use the official LangX email. Then you can use your personal Medium account to like and save it for algo. Is it possible for you to update the email for LangX to [email protected] from the old email? And then use it for the Medium. This way, it looks more professional and we have extra personal account from you. Which email hosting you currently used for the [email protected]? Disroot allows custom domain linking for email hosting with the cost of 12 coffee --lifetime. |
It's the last issue langx/langx#654 about our old domain i just took the username |
@jakebogan01 fixed with this commit: 1d14b56 Kapture.2024-04-19.at.17.45.58.mp4 |
@xuelink thanks for fixing that, didn't see that issue myself |
@jakebogan01 i coudn't centered second line, if you are able to do, appriciated :) |
@xuelink no worries I'll look into it |
Is your feature request related to a problem? Please describe.
The current footer design lacks clarity and organization, making it difficult for users to navigate and find relevant information easily.
Describe the solution you'd like
Implement a better footer design that clearly categorizes sections such as Product, Learn, Resources, and About. Each category should be easily distinguishable and clickable, leading users to the respective sections of the website.
Describe alternatives you've considered
One alternative could be to revamp the entire website layout, including the footer, to ensure a more cohesive user experience. However, a focused improvement on the footer alone might be a quicker and more targeted solution.
Additional context
Attached is some example screenshots illustrating the desired footer design.
If you want speed up process of this issue, please send 🚀 as a reaction.
The text was updated successfully, but these errors were encountered: