When you try to drag the map on the middle, it doesn't work but when you drag from the side/corners it works.

This issue occurs as there is a hidden element on top of the map. Needs fixing.

Would you consider updating the license to MIT? GPL seems a bit weird for this use case; I imagine lots of people want to keep their wedding websites private for awhile. I would otherwise use this project

add node_module folder in gitignore file

Email backend won't work. Tried following https://github.com/dwyl/learn-to-send-email-via-google-script-html-no-server. Console reports "success", but nothing ever comes into my mailserver. No connections. Nothing.

Would it be possible to get the bootstrap versions bumped up to v4 or even v5? There's some new features that I would like to take advantage of in my customization of your project, but I'm not enough of a front-end guy to get it working myself.

I've tried updating the files myself but it causes some alignment issues, buttons to not be colored correctly, and a few other issues.

If you could give some tips I'd definitely be willing to continue trying it myself

Thanks!

Trying to run locally in a macOS Catalina.

Error: Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (83)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.13.1
    at module.exports (/Users/gandarez/Development/marriage/wedding-website/node_modules/node-sass/lib/binding.js:13:13)
    at Object.<anonymous> (/Users/gandarez/Development/marriage/wedding-website/node_modules/node-sass/lib/index.js:14:35)
    at Module._compile (internal/modules/cjs/loader.js:1075:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1096:10)
    at Module.load (internal/modules/cjs/loader.js:940:32)
    at Function.Module._load (internal/modules/cjs/loader.js:781:14)
    at Module.require (internal/modules/cjs/loader.js:964:19)
    at require (internal/modules/cjs/helpers.js:88:18)
    at Object.<anonymous> (/Users/gandarez/Development/marriage/wedding-website/node_modules/gulp-sass/index.js:162:21)
    at Module._compile (internal/modules/cjs/loader.js:1075:30)

Hi, I found your site because I'm getting married and I want to make my own static site. I wanted to look for open-sourced examples first, and I appreciate that you were willing to share the code for your site with the world. It looks great.

There is one major issue, but it's a huge one... the GPL-3.0 license that you chose to include with your source code forces all derivative works to also openly publish their source code. This means that all source code for all derivative works must be made publicly available, which means that hiding wedding details from the public is impossible.

Unfortunately, this is a showstopper for me. I'm planning to put my own static site behind a password-protected gateway so that the world doesn't know all the details about my upcoming wedding. I only want to share these details with family and friends that have the password to the site. While I could clone your site and put it behind a password-protected gateway, it wouldn't really be private since anyone could find the source code (since it must be made public).

It's possible to password-protect static sites by using a Lambda authorizing function to access Cloudfront distributions in S3, and this is how I plan to make my own static site private (once it's developed).

Maybe you carefully chose the GPL-3.0 license for your own reasons, which is completely fine. It's your code, after all. But I want to bring this issue up because, as it currently stands, your open-sourced project means that anyone that uses your work in any capacity must also open-source their work. You published this source code after your wedding, and you therefore avoided privacy concerns that come with having your wedding details made public. Anyone that wants to use your code to build a wedding site must expose their wedding details to the world.

In my opinion, your project would provide more value to the community if it contained an MIT license, because the MIT license would allow anyone to clone your code, build their own site, keep the source code private, and host it with password protection.

Github pages will fail if you try to deploy with all of the node modules currently in your repo.
Remove all but the necessary ones in the package.json
"animate.css": "^3.7.2",
"font-awesome": "^4.7.0",
"waypoints": "^4.0.1"

and the gulp related ones for development. But you probably should put some gulp info in the README as well so people know how to minimize/compile the js and sass files.

Hey there!

I belong to an open source security research community, and a member (@nithissh200) has found an issue, but doesn’t know the best way to disclose it.

If not a hassle, might you kindly add a SECURITY.md file with an email, or another contact method? GitHub recommends this best practice to ensure security issues are responsibly disclosed, and it would serve as a simple instruction for security researchers in the future.

Thank you for your consideration, and I look forward to hearing from you!

(cc @huntr-helper)

Error on opening psd files

Opening '/psd/favicon.psd' failed:

Error loading PSD file: Unexpected end of file

• favicon.psd
• logo.psd
• logo-lg.psd

Is there a way to support multiple languages?

Currently, this uses the traditional deploy to github pages method (you can see it in Settings > Github Pages). However, Github has introduced a new Workflow feature (still in Beta) that allows us to have more control of the deployment process. This task is to move to this new Workflow approach.

I have taken a stab at it here - https://github.com/rampatra/wedding-website/blob/master/.github/workflows/npm-gulp.yml, however, there are some issues that need to be resolved and should be done as part of this ticket. Once done, we can get rid of the fallback approach in index.html for node_modules.

Hi, thanks for your sharing, I have encountered the 'CORS' problem, how to fix it? Is it caused by the wrong setting of deploying google script? I'm the green hands to web developing.

Access to XMLHttpRequest at 'https://script.google.com/macros/s/xxxxxxxxxxxxxx/exec' from origin 'http://localhost:63342' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.