diff --git a/.github/workflows/azure-static-web-apps-gray-plant-049754e10.yml b/.github/workflows/azure-static-web-apps-gray-plant-049754e10.yml new file mode 100644 index 0000000..3dff393 --- /dev/null +++ b/.github/workflows/azure-static-web-apps-gray-plant-049754e10.yml @@ -0,0 +1,62 @@ +name: Azure Static Web Apps CI/CD + +on: + push: + branches: + - master + pull_request: + types: [opened, synchronize, reopened, closed] + branches: + - master + +jobs: + build_and_deploy_job: + if: github.event_name == 'push' || (github.event_name == 'pull_request' && github.event.action != 'closed') + runs-on: ubuntu-latest + name: Build and Deploy Job + steps: + - uses: actions/checkout@v2 + + # Use GitHub Actions' cache to shorten build times and decrease load on servers + - uses: actions/cache@v1 + with: + path: vendor/bundle + key: ${{ runner.os }}-gems-${{ hashFiles('**/Gemfile.lock') }} + restore-keys: | + ${{ runner.os }}-gems- + + - name: Make build destination directory + run: mkdir -vp ./_site + + - name: Jekyll Build + uses: gha-utilities/jekyll-build@v0.0.4 + with: + source: ./ + destination: ./_site + + - name: Build And Deploy + if: github.event.pull_request.head.repo.fork != true + id: builddeploy + uses: Azure/static-web-apps-deploy@v0.0.1-preview + with: + azure_static_web_apps_api_token: ${{ secrets.AZURE_STATIC_WEB_APPS_API_TOKEN_GRAY_PLANT_049754E10 }} + repo_token: ${{ secrets.GITHUB_TOKEN }} # Used for Github integrations (i.e. PR comments) + action: 'upload' + ###### Repository/Build Configurations - These values can be configured to match you app requirements. ###### + # For more information regarding Static Web App workflow configurations, please visit: https://aka.ms/swaworkflowconfig + app_location: '_site' # App source code path + api_location: '' # Api source code path - optional + app_artifact_location: '' # Built app content directory - optional + ###### End of Repository/Build Configurations ###### + + close_pull_request_job: + if: github.event_name == 'pull_request' && github.event.action == 'closed' && github.event.pull_request.head.repo.fork != true + runs-on: ubuntu-latest + name: Close Pull Request Job + steps: + - name: Close Pull Request + id: closepullrequest + uses: Azure/static-web-apps-deploy@v0.0.1-preview + with: + azure_static_web_apps_api_token: ${{ secrets.AZURE_STATIC_WEB_APPS_API_TOKEN_GRAY_PLANT_049754E10 }} + action: 'close' diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..466d76e --- /dev/null +++ b/.gitignore @@ -0,0 +1,3 @@ +# ignore jekyll output +_site +.vscode diff --git a/404.html b/404.html index 5b9b114..c78e99e 100644 --- a/404.html +++ b/404.html @@ -4,9 +4,8 @@ subtitle: "Whoops! Page Not Found" --- -

Sorry - we're in the process of getting the new Open Live Writer website set up and you appear to have tried to - visit a page that doesn't exist yet.

+

Sorry - we're in the process of getting the new Open Live Writer website set up and you appear to have tried to visit a page that doesn't exist yet.

If you don't mind, please -log an issue +log an issue with the URL you were trying to reach and where you clicked in Open Live Writer to get sent here. Thanks!

diff --git a/CNAME b/CNAME index c219cf4..73ed5c1 100644 --- a/CNAME +++ b/CNAME @@ -1 +1 @@ -openlivewriter.org +openlivewriter.com \ No newline at end of file diff --git a/GSoC/index.html b/GSoC/index.html new file mode 100644 index 0000000..f152e8e --- /dev/null +++ b/GSoC/index.html @@ -0,0 +1,60 @@ +--- +layout: default +title: "Information for Google Summer of Code" +permalink: /GSoC/ +download: true +--- +

Google Summer of Code Information

+ +

How to become a Open Live Writer Contributor

+

+

+
+

Project Ideas

+

These are all popularly requested features.

+ diff --git a/Gemfile b/Gemfile new file mode 100644 index 0000000..97f51f2 --- /dev/null +++ b/Gemfile @@ -0,0 +1,10 @@ +# A sample Gemfile +source "https://rubygems.org" + +# gem "rails" +gem 'jekyll' +gem 'jekyll-feed' +gem 'jekyll-redirect-from' +gem 'jekyll-sitemap' +gem 'octokit' +gem 'stringex' diff --git a/Gemfile.lock b/Gemfile.lock new file mode 100644 index 0000000..5659a8b --- /dev/null +++ b/Gemfile.lock @@ -0,0 +1,60 @@ +GEM + remote: https://rubygems.org/ + specs: + addressable (2.3.8) + colorator (0.1) + faraday (0.9.2) + multipart-post (>= 1.2, < 3) + ffi (1.9.10) + ffi (1.9.10-x64-mingw32) + jekyll (3.1.2) + colorator (~> 0.1) + jekyll-sass-converter (~> 1.0) + jekyll-watch (~> 1.1) + kramdown (~> 1.3) + liquid (~> 3.0) + mercenary (~> 0.3.3) + rouge (~> 1.7) + safe_yaml (~> 1.0) + jekyll-feed (0.4.0) + jekyll-redirect-from (0.9.1) + jekyll (>= 2.0) + jekyll-sass-converter (1.4.0) + sass (~> 3.4) + jekyll-sitemap (0.10.0) + jekyll-watch (1.3.1) + listen (~> 3.0) + kramdown (1.9.0) + liquid (3.0.6) + listen (3.0.6) + rb-fsevent (>= 0.9.3) + rb-inotify (>= 0.9.7) + mercenary (0.3.5) + multipart-post (2.0.0) + octokit (4.2.0) + sawyer (~> 0.6.0, >= 0.5.3) + rb-fsevent (0.9.7) + rb-inotify (0.9.7) + ffi (>= 0.5.0) + rouge (1.10.1) + safe_yaml (1.0.4) + sass (3.4.21) + sawyer (0.6.0) + addressable (~> 2.3.5) + faraday (~> 0.8, < 0.10) + stringex (2.6.0) + +PLATFORMS + ruby + x64-mingw32 + +DEPENDENCIES + jekyll + jekyll-feed + jekyll-redirect-from + jekyll-sitemap + octokit + stringex + +BUNDLED WITH + 1.11.2 diff --git a/README.md b/README.md index b1856f3..c6a3ea9 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,5 @@ -# OpenLiveWriter.org Website -The website for http://openlivewriter.org is hosted on GitHub pages using the source in this repository. +# OpenLiveWriter.com Website +The website for http://openlivewriter.com is hosted on GitHub pages using the source in this repository. Note that issues should only be logged against the website itself - for Open Live Writer application issues or enhancements see the [OpenLiveWriter repo](https://github.com/OpenLiveWriter/OpenLiveWriter/issues/). @@ -30,6 +30,29 @@ For more information see the [.NET Foundation Code of Conduct](http://www.dotnet For developer chatter, head on over to the [OpenLiveWriter Gitter room]((https://gitter.im/OpenLiveWriter/OpenLiveWriter?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge)): [![Gitter](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/OpenLiveWriter/OpenLiveWriter?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge) +### For the people writing posts and news items: + +All the files within **`_posts`** should have this section at the top of the file. + +``` +--- +layout: default +title: 'Initial public release' +version: 0.5.0.0 +categories: [release, news] +date: 2015-12-09 00:00:00 -0800 +author: martinwoodward +download: true +--- +``` +Do not change the `layout`. +`title`: The text that you want to see on the page. +`version`: The version number of OLW about which the post is concerned. +`categories`: Comma separated categories within braces. If this contains `blog` it goes to `/blog`, if it contains `news` it goes to `/news`. If both, then it will be present in both places. +`date`: yyyy-mm-dd hh:mm:ss timezone (timezone is of the form +0530 or -0800, ie. +/-hhmm). +`author` is the GitHub username of the author. Used to link to their profile and show a small gravatar. +`download`: I'm not sure what this does but let it be. + ### .NET Foundation The Open Live Writer project is supported by the [.NET Foundation](http://www.dotnetfoundation.org). diff --git a/Rakefile b/Rakefile new file mode 100644 index 0000000..25c0702 --- /dev/null +++ b/Rakefile @@ -0,0 +1,147 @@ +require "stringex" + +# This rakefile will provide rake tasks to make it easier to manage a Jekyll blog + +## -- Misc Configs -- ## +posts_dir = "_posts" # directory for blog files +new_post_ext = "md" # default new post file extension when using the new_post task + +desc "Generate the website using Jekyll" +task :generate do + puts "## Generating site with Jekyll" + system "jekyll build" +end + +desc "Preview the generated website in a browser and keep watching for changes" +task :preview do + puts "## Serving the generated site to localhost:4000 and watching for changes" + jekyllPid = Process.spawn("jekyll serve") + + trap("INT") { + Process.kill(9, jekyllPid) rescue Errno::ESRCH + exit 0 + } + + Process.wait(jekyllPid) +end + +desc "Begin a new blog post in /_posts. Use as rake new_news_item[title,author,file-extension]. In absence of any of those, the values will be asked for interactively." +task :new_blog_post, [:title, :author, :extension] do |t, args| + if args.title + title = args.title + else + puts("Enter a title for your post: ") + title = STDIN.gets.chomp + end + + if args.author + author = args.author + else + puts("Enter your GitHub username: ") + author = STDIN.gets.chomp + end + + if args.extension + new_post_ext = args.extension + else + puts("Enter the file extension you want to use: ") + new_post_ext = STDIN.gets.chomp + end + + filename = "#{posts_dir}/#{Time.now.strftime('%Y-%m-%d')}-#{title.to_url}.#{new_post_ext}" + if File.exist?(filename) + abort("rake aborted!") if ask("#{filename} already exists. Do you want to overwrite?", ['y', 'n']) == 'n' + end + puts "Creating new post: #{filename}" + open(filename, 'w') do |post| + post.puts "---" + post.puts "layout: default" + post.puts "title: \"#{title.gsub(/&/,'&')}\"" + post.puts "date: #{Time.now.strftime('%Y-%m-%d %H:%M:%S %z')}" + post.puts "categories: [blog]" + post.puts "author: #{author}" + post.puts "download: true" + post.puts "---" + end +end + +desc "Begin a new news post in /_posts. Use as rake new_news_item[title,author,file-extension]. In absence of any of those, the values will be asked for interactively." +task :new_news_item, [:title, :author, :extension] do |t, args| + if args.title + title = args.title + else + puts("Enter a title for your post: ") + title = STDIN.gets.chomp + end + + if args.author + author = args.author + else + puts("Enter your GitHub username: ") + author = STDIN.gets.chomp + end + + if args.extension + new_post_ext = args.extension + else + puts("Enter the file extension you want to use: ") + new_post_ext = STDIN.gets.chomp + end + + filename = "#{posts_dir}/#{Time.now.strftime('%Y-%m-%d')}-#{title.to_url}.#{new_post_ext}" + if File.exist?(filename) + abort("rake aborted!") if ask("#{filename} already exists. Do you want to overwrite?", ['y', 'n']) == 'n' + end + puts "Creating new post: #{filename}" + open(filename, 'w') do |post| + post.puts "---" + post.puts "layout: default" + post.puts "title: \"#{title.gsub(/&/,'&')}\"" + post.puts "date: #{Time.now.strftime('%Y-%m-%d %H:%M:%S %z')}" + post.puts "categories: [news]" + post.puts "author: #{author}" + post.puts "download: true" + post.puts "---" + end +end + +desc "Begin a new release post in /_posts. Use as rake new_release[version-number,author,file-extension]. In absence of any of those, the values will be asked for interactively. The fully formed title becomes 'Open Live Writer version-number is now available!'." +task :new_release, [:version, :author, :extension] do |t, args| + if args.version + version = args.version + else + puts("Enter the version number (The fully formed title becomes 'Open Live Writer version-number is now available!'): ") + version = STDIN.gets.chomp + end + title = "Open Live Writer #{version} is now available!" + + if args.author + author = args.author + else + puts("Enter your GitHub username: ") + author = STDIN.gets.chomp + end + + if args.extension + new_post_ext = args.extension + else + puts("Enter the file extension you want to use: ") + new_post_ext = STDIN.gets.chomp + end + + filename = "#{posts_dir}/#{Time.now.strftime('%Y-%m-%d')}-#{title.to_url}.#{new_post_ext}" + if File.exist?(filename) + abort("rake aborted!") if ask("#{filename} already exists. Do you want to overwrite?", ['y', 'n']) == 'n' + end + puts "Creating new post: #{filename}" + open(filename, 'w') do |post| + post.puts "---" + post.puts "layout: default" + post.puts "title: \"#{title.gsub(/&/,'&')}\"" + post.puts "date: #{Time.now.strftime('%Y-%m-%d %H:%M:%S %z')}" + post.puts "categories: [news, release]" + post.puts "author: #{author}" + post.puts "download: true" + post.puts "---" + end +end diff --git a/WriterRedirect/AuthComplete.html b/WriterRedirect/AuthComplete.html new file mode 100644 index 0000000..97850cf --- /dev/null +++ b/WriterRedirect/AuthComplete.html @@ -0,0 +1,7 @@ +--- +layout: post +title: Blog Authentication Complete +download: false +--- + +

You have successfully authenticated with your blog provider. You may close this browser tab.

diff --git a/WriterRedirect/Copyright.html b/WriterRedirect/Copyright.html new file mode 100644 index 0000000..21999d0 --- /dev/null +++ b/WriterRedirect/Copyright.html @@ -0,0 +1,7 @@ +--- +layout: redirect +title: "Copyright entry from Wikipedia" +redirect_to: + - https://en.wikipedia.org/wiki/Copyright +--- + diff --git a/WriterRedirect/YouTubeRegister.html b/WriterRedirect/YouTubeRegister.html new file mode 100644 index 0000000..e8f2549 --- /dev/null +++ b/WriterRedirect/YouTubeRegister.html @@ -0,0 +1,6 @@ +--- +layout: redirect +title: "YouTube Registration page" +redirect_to: + - https://support.google.com/youtube/topic/3024170?hl=en&ref_topic=3024169 +--- diff --git a/WriterRedirect/YouTubeSafety.html b/WriterRedirect/YouTubeSafety.html new file mode 100644 index 0000000..c0b825d --- /dev/null +++ b/WriterRedirect/YouTubeSafety.html @@ -0,0 +1,6 @@ +--- +layout: redirect +title: "YouTube Safety page" +redirect_to: + - http://www.youtube.com/yt/policyandsafety/safety.html +--- diff --git a/WriterRedirect/YouTubeTOU.html b/WriterRedirect/YouTubeTOU.html new file mode 100644 index 0000000..bab21ad --- /dev/null +++ b/WriterRedirect/YouTubeTOU.html @@ -0,0 +1,6 @@ +--- +layout: redirect +title: "YouTube Terms of Use page" +redirect_to: + - https://www.youtube.com/static?gl=US&template=terms +--- diff --git a/_config.yml b/_config.yml index 35a9e26..a52b890 100644 --- a/_config.yml +++ b/_config.yml @@ -4,6 +4,9 @@ url: http://www.openlivewriter.com title: Open Live Writer subtitle: Turning blogging up to 11 since 2007 +# RSS Feed config +description: Open Live Writer is like Word for your blog. + # Google Analytics google_analytics_tracking_id: UA-57261022-2 @@ -14,4 +17,4 @@ google_analytics_tracking_id: UA-57261022-2 gems: - jekyll-redirect-from - jekyll-sitemap - \ No newline at end of file + - jekyll-feed diff --git a/_includes/download.html b/_includes/download.html deleted file mode 100644 index 8cb9332..0000000 --- a/_includes/download.html +++ /dev/null @@ -1,7 +0,0 @@ - -

- Download -

click to begin

-

5.2MB .exe

-
diff --git a/_includes/download_exe.html b/_includes/download_exe.html new file mode 100644 index 0000000..dd97e93 --- /dev/null +++ b/_includes/download_exe.html @@ -0,0 +1,5 @@ +
+ Download +

Click to begin

+

5.2MB (.exe)

+
diff --git a/_includes/download_source.html b/_includes/download_source.html new file mode 100644 index 0000000..5f18d67 --- /dev/null +++ b/_includes/download_source.html @@ -0,0 +1,5 @@ +
+

Download Source

+ + +
diff --git a/_includes/footer.html b/_includes/footer.html index 9d9bfbd..c39b5a9 100644 --- a/_includes/footer.html +++ b/_includes/footer.html @@ -1,2 +1,9 @@ -

Copyright © {{ site.time | date: "%Y" }} .NET Foundation.

- + diff --git a/_includes/google_analytics.html b/_includes/google_analytics.html index 14f5fbc..6fdb069 100644 --- a/_includes/google_analytics.html +++ b/_includes/google_analytics.html @@ -1,15 +1,15 @@ {% if site.google_analytics_tracking_id %} {% endif %} diff --git a/_includes/head.html b/_includes/head.html index 36bfeaa..8c025eb 100644 --- a/_includes/head.html +++ b/_includes/head.html @@ -6,10 +6,21 @@ {% endif %} + {{ page.title }} {% if page.keywords %}{% endif %} - + + + + + + + + + + + diff --git a/_includes/header.html b/_includes/header.html new file mode 100644 index 0000000..05dffb7 --- /dev/null +++ b/_includes/header.html @@ -0,0 +1,25 @@ + +
+ {% include google_analytics.html %} + +
+
+ View on GitHub +

Open Live Writer

+ {% if page.subtitle %} +

{{ page.subtitle }}

+ {% endif %} +
+
+ + + + {% if page.download == true %} + {% include download_exe.html %} + {% endif %} diff --git a/_includes/news_item.html b/_includes/news_item.html new file mode 100644 index 0000000..802c20a --- /dev/null +++ b/_includes/news_item.html @@ -0,0 +1,19 @@ +
+

+ + {{ post.title }} + +

+
+ + {{ post.date | date_to_string }} + + + {{ post.author }} avatar + {{ post.author }} + +
+
+ {{ post.content }} +
+
diff --git a/_layouts/default.html b/_layouts/default.html index 2ccc495..d269bbc 100644 --- a/_layouts/default.html +++ b/_layouts/default.html @@ -1,29 +1,64 @@ {% include head.html %} - - - {% include google_analytics.html %} - -
-
- View on GitHub -

Open Live Writer

- {% if page.subtitle %} -

{{ page.subtitle }}

- {% endif %} -
-
- -{% if page.download == true %} -{% include download.html %} -{% endif %} - + + {% include header.html %}
-
{{ content }}
-
- - - +
+ +{% include footer.html %} + + + + diff --git a/_layouts/post.html b/_layouts/post.html new file mode 100644 index 0000000..ce233ad --- /dev/null +++ b/_layouts/post.html @@ -0,0 +1,14 @@ +--- +layout: default +--- +
+ +
+

{{ page.title }}

+
+ +
+ {{ content }} +
+ +
diff --git a/_posts/2015-12-09-initial-public-release.md b/_posts/2015-12-09-initial-public-release.md new file mode 100644 index 0000000..6dcf247 --- /dev/null +++ b/_posts/2015-12-09-initial-public-release.md @@ -0,0 +1,25 @@ +--- +layout: post +title: 'Initial public release' +version: 0.5.0.0 +categories: [news, release] +date: 2015-12-09 00:00:00 -0800 +author: martinwoodward +download: true +--- +First open source release of Open Live Writer! + +### Installation + +Install from http://www.OpenLiveWriter.com + +You can install the latest version of Open Live Writer alongside an older version of Windows Live Writer. + +### Details + +For a list of known issues see GitHub or take a +look at the roadmap to see what the current plans are. + +For the latest news and updates about Open Live Writer, you can follow us on Twitter +(@OpenLiveWriter), by keeping an eye on the website +http://www.OpenLiveWriter.com or by watching this repo and subscribing to notifications. diff --git a/_posts/2015-12-17-blogger-v3-api-support.md b/_posts/2015-12-17-blogger-v3-api-support.md new file mode 100644 index 0000000..1cc93e1 --- /dev/null +++ b/_posts/2015-12-17-blogger-v3-api-support.md @@ -0,0 +1,12 @@ +--- +layout: post +title: 'Blogger V3 API Support' +version: 0.5.1.2 +categories: [news, release] +date: 2015-12-17 00:00:00 -0800 +author: martinwoodward +download: true +--- +This release provides the initial version of Blogger support using their latest API to unblock users of Blogger. + +To force an update, visit [http://openlivewriter.com](http://openlivewriter.com) then download and run the installer. Otherwise if you start Open Live Writer and wait a minute or so, next time you restart Live Writer you should be running the latest version (go to Help, About Open Live Writer to see what version you are on) diff --git a/_posts/2016-01-16-Contributing-to-Open-Live-Writer.md b/_posts/2016-01-16-Contributing-to-Open-Live-Writer.md new file mode 100644 index 0000000..0591bc5 --- /dev/null +++ b/_posts/2016-01-16-Contributing-to-Open-Live-Writer.md @@ -0,0 +1,31 @@ +--- +layout: post +title: 'Contributing to Open Live Writer' +categories: [blog] +date: 2016-01-16 00:00:00 -0800 +author: kathweaver +download: true +--- + +I have been using the original Live Writer since it came out, and loved it. I was +an avid user of the plug-ins too. + +As soon as I heard about Open Live Writer, on December 9th, I downloaded it and set up my blogs. Immediately I read the documemtation +and saw that they were looking for contributors. + +My bachelor's degree is in computer science, my master's in education with an emphasis on online learning. Both +before and after my teaching career I worked in industry, most recently on a Windows phone app as a contractor. I also +write my own software both mobile and web apps when I need to. + +I will admit to a huge learning curve with GIT, but I'm getting there. I've used SVN before, and have it set up on my own server. +While I am not currently comfortable with the code, I'm doing what I am comfortable with -- working on documenation and test plans. +The developers have been super supportive of my efforts, and one of the reasons I'm writing this, is to urge other people to come on +board like me. This is probably one of the most supportive open source projects I've seen, and I would love some help. + +Those test plans have typos, and may be missing some spots. That's a really good way to get handle on the whole project and I've already +even found some problems and helped fix them. + +Here are some other things that people can do before they get comfortable with the code: the best is examining any new issues, trying to reproduce +them and encourages reporters to be helpful. I've even set up blogger and wordpress test blogs to help in that effort. + +And of course, if you can code, jump in and do so! diff --git a/_posts/2016-02-05-Contributing-to-documentation.md b/_posts/2016-02-05-Contributing-to-documentation.md new file mode 100644 index 0000000..9bf888f --- /dev/null +++ b/_posts/2016-02-05-Contributing-to-documentation.md @@ -0,0 +1,28 @@ +--- +layout: post +title: 'Contributing to Documentation' +categories: [blog] +date: 2016-02-05 00:00:00 -0800 +author: kathweaver +download: true +--- +I've expanded my contribution. I've been posting blog posts to the website. I've also +created a tutorial and I will be doing more as we all get more comfortable with the process. +I would also like some help. + +The Open Live Writer website is at http://www.openlivewriter.com and is maintained and +hosted with Github and Jekyll. + +Jekyll is pretty easy to use once you get the hang of it. I started out by creating +my own Github/Jekyll website. That way I wouldn't have to worry about screwing anything up. + +I installed Jekyll by following the directions on this website: http://jekyll-windows.juthilo.com/ +which creates a web server on your machine so you can see what you have done. + +Now my blog posts are in markdown. However, my tutorial is in html, as that is what I +am most comfortable with creating. I've taught computer science and web design for several +decades and have created tutorials for both students and adult coworkers, and so that's +the tool I'm most comforable with. Besides, I could then use Open Live Writer -- though I think +markdown is in the plans. + + diff --git a/_posts/2016-02-11-Contributing-testing.md b/_posts/2016-02-11-Contributing-testing.md new file mode 100644 index 0000000..be1b181 --- /dev/null +++ b/_posts/2016-02-11-Contributing-testing.md @@ -0,0 +1,52 @@ +--- +layout: post +title: 'How to contribute by testing' +categories: [blog] +date: 2016-02-11 00:00:00 -0800 +author: kathweaver +download: true +--- + +One of the best ways to contribute is testing. There are test plans and some +information in the source, under the directory test plans. Also feel free to +check those and update them if you find an issue. + +They are basically check lists that go through every function of the software and tell +what should happen when you do them, including images. We came up with this on my last +programming gig, and they helped everyone. + +The programmers then knew what we were expecting and so did QA. I often had QA help me with +them so that they would have some ownership. + +So what do you test and how? + +Each time a developer makes a pull request, you should go through the new functionality +and make sure it behaves as expected. Then you should go through the rest of the software +making sure that something wasn't accidently broke. + +At least two different people should go through the process, but the more the better. It also +helps if someone goes through it that has a fresh eye on the software. + +So where do you find the executeable? To do the last build in the pull request, +scroll down to the point where you see "All checks have passed", and click on "Show All Checks". +Click on "Details", then "Artifacts", and will see OpenLiveWriteSetup.exe -- download +that and run it even if you get messages from Windows saying it isn't safe. + +If you do find an error, give the developer as much information as you can. Screenshots, error messages, +log files, you name it. The more complete you are, the less time the developer has to spend tracking +the error down. + +----- + +You can also test the nightly build. It will contain everything that has been merged. + +You can setup OpenLiveWriter to always run the nightly build: +Go to regedit, find the registery key: HKEY_CURRENT_USER\SOFTWARE\OpenLiveWriter\Updates +Then you need to create a dword key for CheckForBetaUpdates 1 = beta, 0 = regular. + +You can also pull the nightly build manually by going to this link: +https://ci.appveyor.com/project/dotnetfoundation/openlivewriter/build/artifacts + +Or click on the build button from the readme and then click on latest build, artifacts + +Again, if you find a problem you'll need to raise an issue and give as much information as you can. diff --git a/_posts/2016-02-11-GitHub.md b/_posts/2016-02-11-GitHub.md new file mode 100644 index 0000000..e44dda3 --- /dev/null +++ b/_posts/2016-02-11-GitHub.md @@ -0,0 +1,19 @@ +--- +layout: post +title: 'Brief overview of GitHub' +categories: [blog] +date: 2016-02-16 00:00:00 -0800 +author: kathweaver +download: true +--- + +For those new to GitHub, and I am one, it's very well documented. First a quick overview of the process. + +Open Live Writer has two different repositories (a repository is just a place to store things). One for the program itself and a second one for the documentation. If you are reading this, you are reading documentation. + +The code is at [https://github.com/OpenLiveWriter](https://github.com/OpenLiveWriter) and the documentation is [https://github.com/OpenLiveWriter/OpenLiveWriter.Github.io](https://github.com/OpenLiveWriter/OpenLiveWriter.Github.io) + +The two best places to learn about Github, is Github itself. Help is at [https://help.github.com/](https://help.github.com/) and [https://www.codecademy.com/](https://www.codecademy.com/) There is a walkthrough there. + +Unfortunately if you are adding to documentation or code, you do have to use both GitHub desktop and Git Shell, again the process for both are very well documented, with a tutorial loaded into Github Desktop. + diff --git a/_posts/2016-02-14-version-0-dot-6-now-available.md b/_posts/2016-02-14-version-0-dot-6-now-available.md new file mode 100644 index 0000000..0fa9360 --- /dev/null +++ b/_posts/2016-02-14-version-0-dot-6-now-available.md @@ -0,0 +1,66 @@ +--- +layout: post +title: "Open Live Writer Version 0.6 Is Now Available" +date: 2016-02-14 05:22:23 +0530 +categories: [news, release] +author: hashhar +download: true +--- + +After about two months since the initial public release the team and community have managed to add features, fix issues and fulfill the demand for some of the more requested features like spell checking (it will only work on Windows 8 and later though) and support for Blogger categories. We hope you enjoy the new features as much as we enjoyed working on them. Read on to learn more about what issues have been fixed and what features have been added. + +The next time you start Open Live Writer and are connected to the internet, it should get updated automatically. But if you can't wait to try out the goodness, download the [updated setup here](https://openlivewriter.azureedge.net/stable/Releases/OpenLiveWriterSetup.exe). + +## Release Notes + +For spell checking to work you'll need to have Windows 8 or newer installed (Windows 7 does not have spell checking support) and you’ll need to install your preferred input language in [Windows 8 and 8.1][1] or [Windows 10][2] to enable spell checking in that language. Only one language can be spell checked in Open Live Writer at a time, but you can change the language at any time by going to **File > Options > Spelling** and choosing a new dictionary language. + +Google Blogger categories will automatically populate for easy tagging of your blog posts. In addition to categories, there are several other Google Blogger bug fixes in this release. The most notable issues were time zone differences causing scheduled posts to be scheduled at the incorrect time, failing to open drafts that were posted to Blogger, and failing to download and open posts from Blogger that are older than your most recent 500 posts. + +[1]:http://windows.microsoft.com/en-us/windows-8/add-language-keyboard +[2]:http://windows.microsoft.com/en-us/windows-10/how-to-add-an-input-language-to-your-pc + +### Bug fixes + +[#190](https://github.com/OpenLiveWriter/OpenLiveWriter/issues/190) - Saving doesn't mark categories as saved +[#103](https://github.com/OpenLiveWriter/OpenLiveWriter/issues/103) - Errors when using invalid url to insert an image +[#323](https://github.com/OpenLiveWriter/OpenLiveWriter/issues/323) - ArgumentNullException when getting recent posts on empty blog +[#301](https://github.com/OpenLiveWriter/OpenLiveWriter/issues/301) - Can't retrieve drafts from Google Blogger +[#247](https://github.com/OpenLiveWriter/OpenLiveWriter/issues/247) - Can't Edit Old Blogger Posts (>500) +[#224](https://github.com/OpenLiveWriter/OpenLiveWriter/issues/224) - Google Blogger scheduled post is scheduled at the wrong time + +### Improvements + +[#239](https://github.com/OpenLiveWriter/OpenLiveWriter/issues/239) - Fix issue with spaces in username +[#281](https://github.com/OpenLiveWriter/OpenLiveWriter/issues/281) - Test Plans + +### Features + +[#130](https://github.com/OpenLiveWriter/OpenLiveWriter/issues/130) - Add spell check feature back in OLW +[#234](https://github.com/OpenLiveWriter/OpenLiveWriter/issues/234) - Support Blogger categories + +--- + +### Special thanks to our contributors for this release: + +willduff avatar [@willduff](https://github.com/willduff) + +ScottIsAFool avatar [@ScottIsAFool](https://github.com/ScottIsAFool) + +martinwoodward avatar [@martinwoodward](https://github.com/martinwoodward) + +timheuer avatar [@timheuer](https://github.com/timheuer) + +hmemcpy avatar [@hmemcpy](https://github.com/hmemcpy) + +bbowyersmyth avatar [@bbowyersmyth](https://github.com/bbowyersmyth) + +kathweaver avatar [@kathweaver](https://github.com/kathweaver) + +jannavarro avatar [@jannavarro](https://github.com/jannavarro) + +hashhar avatar [@hashhar](https://github.com/hashhar) + +jmbucknall avatar [@jmbucknall](https://github.com/jmbucknall) + +demortes avatar [@demortes](https://github.com/demortes) diff --git a/_posts/2016-02-18-testing.md b/_posts/2016-02-18-testing.md new file mode 100644 index 0000000..886c484 --- /dev/null +++ b/_posts/2016-02-18-testing.md @@ -0,0 +1,35 @@ +--- +layout: post +title: 'This is how I test' +categories: [blog] +date: 2016-02-16 00:00:00 -0800 +author: kathweaver +download: true +--- + +I've been asked about testing by someone new, so I thought going through my process would be good. + +I'm testing Pull Request #117. + +The first thing I did is review the pull request and make sure I know what the new feature is. I review the entire pull request each time I test. + +The next thing I did was to write a test plan while I went through it. That test plan has it's own pull request now and I pull it and go through the checklist as I go. + +I make any notes when the program behaves differently then I expected. + +Here's where I get the code to test. I go to the actual pull request -- this one is 117, and scroll down to the bottom of the page. You'll see a green github icon that says "All Checks have passed" On the right is blue there is a "Show all checks". Click that and you'll see a AppVeyor build succeeded, and in blue "Details" on the right. Click "Details". + +An AppVeyor page opens, that has information including the application name "OpenLiveWriter", and a short description. On the right, you will see Console Messages Tests and Artifacts. You'll need to click on "ARTIFACTS". + +When you do, you'll see a file name list. You need to download and run the Releases\OpenLiveWriterSetup.exe. + +When you run it, you may get some messages from Windows saying that the program might not be safe, ignore them. + +OpenLiveWriter should open. The first thing you should do to determine that you have the right version, look for the new feature it should be there. + +Since I have already started this test, the first thing I did was to check the issue that was bothering me. It's resolved so I've let a comment for the author. The next thing I'll do is a full test of the feature. + +Finally I'll go through the app like I normally would to make sure nothing is broken. Using my testplan checklists of course. + +I might even though through the entire program and make sure nothing has changed. In fact, I probably will. + diff --git a/_posts/2017-05-24-version-0-6-2-released.md b/_posts/2017-05-24-version-0-6-2-released.md new file mode 100644 index 0000000..786d4b6 --- /dev/null +++ b/_posts/2017-05-24-version-0-6-2-released.md @@ -0,0 +1,48 @@ +--- +layout: post +title: "Open Live Writer Version 0.6.2 Is Now Available" +date: 2017-05-24 05:22:23 +0530 +categories: [news, release] +author: jongalloway +download: true +--- + +We're happy to announce a new release of Open Live Writer. We hope you enjoy the new features as much as we enjoyed working on them. Read on to learn more about what issues have been fixed and what features have been added. + +The next time you start Open Live Writer and are connected to the internet, it should get updated automatically. But if you can't wait to try out the goodness, download the [updated setup here](https://openlivewriter.azureedge.net/stable/Releases/OpenLiveWriterSetup.exe). + +## Release Notes + +This is primarily a maintenance release to handle issues with publishing images due to Google Blogger. They'd made some changes to how images are uploaded to Google Photos that prevent Open Live Writer from automatically configuring photo publishing. We've added some extra steps to try to configure it, and if we can't set it up for you automatically we link to a help page that shows you how to set it up. + +We also added in a few smaller bug fixes and improvements listed below, mostly submitted by the community. Thanks!!! + +We added a few features for better High DPI monitor support. + +As part of this release, we put a lot of work into making it easier for us to publish new releases. We've automated our build and sign process, so each code check-in will build a new installer for us. There's still some work to do on the Windows Store release process, but we've got a good start on that as well. Well this doesn't immediately translate to any new feature in this release today, it will help you get more frequent updates with both bug fixes and new features going forward. + +Special thanks to our contributors for this release: +@ScottIsAFool @vhanla @hashhar @zivkan @paulcbetts @onovotny @kathweaver @gruenwaldt @flcdrg @nimesh-madhavan @lextm + +### Bug fixes + +#562 Error: Can't Publish Files- The remote server returned an error: (501) Not Implemented +> This is the master issue for the Google Blogger image publishing problem. Other issues associated with this problem include #608, #600, and #564 + +#437 Blogger dynamic templates +#438 Fixed WordCounter regex to support Hebrew/Arabic +#521 Support atompub service link with relative url +#487 Adding new intillesense db file to gitignore. Minor annoyance + +### Improvements + +#589 Several NuGet packages should be updated + +### Features + +#450 Fix scaling of categories dropdown and options dialog +#585 Implement per-monitor DPI Support +#180 Add support to CSS3 templates + +> Note: Our previous code signing certificate has expired, so this release is signed by a new code signing certificate. Because of this, you may receive warnings from Windows Defender SmartScreen when you run +the installer, indicating that the program is not commonly downloaded and may be unsafe. For more information, see [this help page](http://openlivewriter.com/tutorials/unrecognizedApp.html). diff --git a/atom.xml b/atom.xml new file mode 100644 index 0000000..98f29da --- /dev/null +++ b/atom.xml @@ -0,0 +1,25 @@ +--- +layout: null +--- + + + + {{ site.title }} + + + {{ site.time | date_to_xmlschema }} + {{ site.url }} + + {{ site.author.name }} + {{ site.author.email }} + + {% for post in site.posts %} + + {{ post.title }} + + {{ post.date | date_to_xmlschema }} + {{ site.url }}{{ post.id }} + {{ post.content | xml_escape }} + + {% endfor %} + diff --git a/blog/index.html b/blog/index.html new file mode 100644 index 0000000..deab37f --- /dev/null +++ b/blog/index.html @@ -0,0 +1,12 @@ +--- +layout: default +title: Blog +permalink: /blog/ +download: true +--- + +{% for post in site.posts %} + {% if post.categories contains 'blog' %} + {% include news_item.html %} + {% endif %} +{% endfor %} diff --git a/getting-started/index.html b/getting-started/index.html index b6d915c..e739ce7 100644 --- a/getting-started/index.html +++ b/getting-started/index.html @@ -21,13 +21,13 @@

Give your post a title

Type a title for your post where it says Enter a post title.

-

Enter title

+

Enter title

Start writing your story

Write your story in the post window. If you want to format the text, use the commands in the ribbon. Create headings by using the options in the HTML styles group. Change the style of a font by using the options in the Font group. You can add links, pictures or video from the Insert group.

-

An example blog post

+

An example blog post

Publish your story

diff --git a/images/OLW_screenshot.png b/images/OLW_screenshot.png new file mode 100644 index 0000000..8840b67 Binary files /dev/null and b/images/OLW_screenshot.png differ diff --git a/index.html b/index.html index cb0d3bd..54e19bc 100644 --- a/index.html +++ b/index.html @@ -3,87 +3,87 @@ title: "Open Live Writer" download: true --- -

-Welcome to Open Live Writer

+

Welcome to Open Live Writer

Open Live Writer is like Word for your blog. Open Live Writer is a powerful, lightweight blog editor that -allows you to create blog posts, add photos and videos then publish to your website. You can also compose blogs posts offline -and then publish on your return. +allows you to create blog posts, add photos and videos then publish to your website. You can also compose blogs posts offline and then publish on your return. Open Live Writer works with many popular blog service providers such as WordPress, Blogger, TypePad, Moveable Type, DasBlog and many more.

+ +

+ +

About

- -

-About

Open Live Writer is an open source application enabling users to author, edit, and publish blog posts. -It is based on a fork of the well-loved but not actively developed Windows Live Writer code. +It is based on a fork of the well-loved but not actively developed Windows Live Writer code. Open Live Writer is provided under a MIT license.

-

-Get Connected

+

Get Connected

+ +

If you're interested in getting occasional notices of updates to Open Live Writer and hearing about opportunities to try new features, you can subscribe to our Announcements email list. -

If you're interested in getting occasional notices of updates to Open Live Writer and hearing about opportunities to try new features, -you can subscribe to our Announcements email list. You can also follow @OpenLiveWriter on Twitter and like the page for Open Live Writer on Facebook.

+ +

Get Support

+

User Support is available at Open Live Writer Help which is a Google Group. + -

-Get Involved

+

Get Involved

If you're interested in getting involved in any of the below ways, please subscribe to our mail list.

-

-Authors and Contributors

+

Authors and Contributors

-

Below are some of the people who have helped to bring you Open Live Writer.

+

Below are some of the people who have helped to bring you Open Live Writer.

-

-Support

+

Support

Having trouble with Open Live Writer? Notice a bug? Check-out frequently asked questions (FAQ) diff --git a/news/index.html b/news/index.html new file mode 100644 index 0000000..32740fb --- /dev/null +++ b/news/index.html @@ -0,0 +1,12 @@ +--- +layout: default +title: News +permalink: /news/ +download: true +--- + +{% for post in site.posts %} + {% if post.categories contains 'news' %} + {% include news_item.html %} + {% endif %} +{% endfor %} diff --git a/plugins/index.html b/plugins/index.html index 698c351..2d48c94 100644 --- a/plugins/index.html +++ b/plugins/index.html @@ -6,6 +6,6 @@ - /WriterRedirect/WriterDownloadPluginsURL/ ---

- Plug-ins are one of the great features of Live Writer and we are working on bringing them to you. - Check back here to see when some great plug-ins are available! + Plug-ins are one of the great features of Live Writer and we are working on bringing them to you. + Check back here to see when some great plug-ins are available!

diff --git a/setupFTP/blogOptions.png b/setupFTP/blogOptions.png new file mode 100644 index 0000000..4286ed1 Binary files /dev/null and b/setupFTP/blogOptions.png differ diff --git a/setupFTP/ftp.png b/setupFTP/ftp.png new file mode 100644 index 0000000..7682b8a Binary files /dev/null and b/setupFTP/ftp.png differ diff --git a/setupFTP/homeTab.png b/setupFTP/homeTab.png new file mode 100644 index 0000000..2245872 Binary files /dev/null and b/setupFTP/homeTab.png differ diff --git a/setupFTP/index.html b/setupFTP/index.html new file mode 100644 index 0000000..8635046 --- /dev/null +++ b/setupFTP/index.html @@ -0,0 +1,31 @@ +--- +layout: default +title: "Setting Up FTP" +redirect_from: +- /WriterRedirect/WriterFTPHelpV3/ +--- +

Setting up FTP

+ +

To be able to access photos hosted at an FTP site, you'll need to set up FTP in Open Live Writer

+ +

You will need the following information:

+ + +

Once you have these, you can enter the settings by going to:

+