Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 9 months ago.
Improve this question
I'm hoping someone can point me in the right direction. I would like to add the Metaplex/candymachine function to an existing website that was originally built to work with metamask. Just trying to save myself from having to redo the website. Thanks
There's no real easy way to do this unfortunately unless you have some prior HTML/CSS/and JS knowledge.
What some people do is take the logic from the CandymachineUI which can be found here CandyMachine.ts which is a type script file and port it over to their own website. You could also attempt to remake the UI calling to these functions and data, or failing that pulling the existing Mint area out the CandymachineUI site (built on React) and attempting to slot that into your existing site. I'd recommend if you took that approach that you swap out the MUI components for div's and your own CSS to save adding MUI to your site adding some bloat (unless your site already uses MUI then you good to go).
Bare in mind you'll also need the supporting dependecies too.
There are also other community built UI's out there but you are going to run into the same issues of porting over all the js/ts to your own site.
I always say it's generally quicker to rebuild a site around an already made mint template than it is to put the mint function into an original.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 days ago.
Improve this question
I'm currently building a website in Next.js and I've gotten to the Blog page which got me thinking about how to handle this page but also whether or not I should approach the rest of the pages differently too. I am just hard-coding all the content (text and images) and I was wondering if there is a better/smarter way to do this? Or should I keep going like this and also hardcode blog posts into my website.
I'm not that experienced so I wouldn't really know how this affects performance or other aspects.
Better or smarter way is very subjective in my opinion. But I will give you some options:
Hardcode it just like the way you do right now. It won't affect performance but you will have to write the code, push it to some version control (if you use one), trigger the build, and make sure it works.
Use Markdown file for every post and have next.js automatically build routes of it. See this tutorial if you wanna take a look. The pros are it's simple (doesn't need a database), and you don't have to write the entire code -- just write the content in a markdown syntax. But you still need to push your changes and trigger the build.
Use headless CMS like Strapi, etc. Personally this is the most convenience way. Write your content, click that Save button, and you're done. But it needs more setup then the other options.
Create your own backend and database setup.
Hope it helps.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 months ago.
Improve this question
I need a little advice before I start work.
So I have been developing a site under React for a client for 2 years now.
My client wants to duplicate this site to create 3 additional brands, the architecture, the design is the same, just the content and the logos change.
So for you is this:
1 - I duplicate in several github repos
Where
2 - I simply create several branches
Thanks
It really depends.
Option A, copy-paste your project to X other projects will make it easy to start and you can finish it in a day, BUT... every time you'll have to fix a bug you will need to do it in each repo and they'll diverge.
Option B, is to build front-end and an API.
The UI will be the same for all the projects but the API will return different data based on the client.
Option C, create a configuration file that you can modify based on the customer.
I believe that Option A will be the simplest & fastest one to get started with. You'll pay the price as you grow, but if you don't need to maintain the projects in the future I would go with it.
If you're going to maintain those projects for a long time you might want to consider refactoring the projects to a dynamic backend that returns the data based on the client.
Option C, it's a pretty good compromise between A and B.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 11 months ago.
Improve this question
I created a project with React, but now I'm thinking of SEO
My project is very simple, although it shows 3D Models using React Three Fiber
But it also shows pages that are defined depending on some videos obtained from Vimeo (using an API), making the site a little dynamic, since we don't previously know which pages will be shown
The question is, can this site be successfully built using Gatsby, as a Static Sites Framework, or do I have to use an SSR Framework like Vercel's Next, because of the pages that will be generated from an API
Yes Gatsby is a good solution. If you realize in the future that you might need to be re-building the app a little more than you are comfortable with, then you can re-hydrate the browser on the users end to query data that you get from an api. This keeps the benefits of SSG (speed, robustness, and SEO), but adds some flexibility and dynamic nature to your application. You can set it up with the Gatsby docs (which are great for any problems you might have with Gatsby in the future). Extra info below: https://www.gatsbyjs.com/docs/reference/config-files/gatsby-ssr
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I have a moderate level experience on HTML, PHP, CSS, Javascript and WordPress development. So I decided to create my own theme for my personal blog. I'm writing tutorials, snippets and tech news on my blog.
In fact I prefer using new design trends like single page apps. Letting users to navigate between homepage to a post or a post to another post without reloading whole page. I think using WordPress Rest API and AngularJS would be adequate.
My actual question; is it creating a SPA theme for a simple blog is sensible? Can using WP REST API for this purpose increase or reduce my server load and page load time?
Is it sensible? Sure, if that's how you want it to work.
Can using WP REST API for this purpose increase or reduce my server load and page load time? Yes it can either increase or reduce your server load time. It comes down to your actual implementation, which until you implement it wont do either.
Most blogs are fairly simple with very little html/css/js and most of the content (i.e. bytes that must be transferred over the wire) is in any media that is included as part of your articles. If you are only considering it for the purposes of reduced server load or page load time, there are a lot of other techniques that would probably prove more beneficial than converting your entire app to SPA (e.g. optimizing your static content or serving it from a CDN). Of course I don't know your exact situation and without knowing more, no one is really going to be able to help you much more.
If you have a specific change to an existing you would like for us to compare, that's something Stack Overflow would be much better at for you. Right now we're just guessing what your situation is.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
Im just begining to use polymer and i was testing to make a demo website using polymer components but i felt difficulty on making the pages responsive ?
Should i use css?
Thanks
Yep, you could use CSS. However, web components can be a bit tricky to get responsive because of their nature of re-use and possibly different locations.
Unfortunately, while CSS/media-queries are one solution, it's not the perfect solution. Why? Because the same component, depending on it's location/container may be desired to look/behave differently. For instance, a "voting" component in a primary content section (800PX wide) may display additional information vs the same component in a right rail (200PX wide) where just the question/answers may be displayed.
What we as web developers really need are "element queries", which allow components to react based on their occupying space (rather than the page-level layout). There are articles and polyfills regarding this that may be of interest to you. One can be found here:
http://www.smashingmagazine.com/2013/06/25/media-queries-are-not-the-answer-element-query-polyfill/
IMO, you should focus on Web instead of Mobile, because the native Android browsers before Android 4.4 doesn't support Polymer, even with Polyfills!
Anyway there is a core-drawer-panel, which is a responsive layout you can start with.
https://www.polymer-project.org/docs/elements/core-elements.html#core-drawer-panel