Also, I want to put a BIG thank you out there to all of the beta testers for this Alloy update! As always you all have been a huge help in catching bugs and offering suggestions and feature requests!
2 Likes
I have been using this for awhile and can say this is a very solid update. All current Alloy users will love this new backend feature. It is so easy to implement and use. Like Adam said, the content of the blog is now what shines.
3 Likes
This is a brilliant addition to Alloy!! I really looking forward to employing it!
Thanks for the sneak peek!
Blessings,
—Mark
2 Likes
This fantastic update makes Alloy more accessible to MOST users. Great job, Adam!
2 Likes
Whoa! This is really fantastic news, can’t wait for it to be released, now I’m going to be checking for updates more frequently! I already loved using Alloy, but this is going to make it a no brainer.
2 Likes
I’m currently working on getting things ready for Alloy v2 update release… Until then feel free to check out the following Editor videos. They’ll give you an idea of how you’ll be setting up your blog and the online editor:
Getting Started: Getting Started wth Alloy - YouTube
Editor Setup: Alloy Editor Setup - Part One - YouTube
Using Editor: Alloy Editor Setup - Part Two - YouTube
3 Likes
Hi, this will be perfect for my clients, so that they can log in and write their own blog posts.
Now, if I look at the way my clients like to work, they want to use some pictures in a post. But they do not want to use an extra software like ftp to upload any pictures to a different directory, select the URL and paste it somewhere else. And they should not have access to the ftp, so that they do not start deleting or renaming important files in the websites’ structure.
So in the future, could we use this editor to insert pictures (up to a certain size) as well and store it together with the post / just in the folder we use for the posts?
Thanks,
Jan
1 Like
That would require a different approach to the way the editor works. This editor uses Markdown for its content, which has not changed from Alloy v1, so you’ll still insert images using a Markdown image tag (or if you really want to HTML image tag – but I’d suggest the Markdown tag). The editor provides a toolbar for inserting that Markdown image tag though, making it easier, but your clients will indeed need to store their images somewhere. I hear cries from users all the time to provide Remote Image support, and this is that very thing within your blog posts.
I won’t rule out having a central location in the Editor for users to upload images in the future, but that is not something that is currently being developed.
Also, please note that there should be nothing but your blog posts in your “Posts” folder.
Thank you! I will just make sure my clients will store the images somewhere safe, so that they are not deleted by accident 
And no, not in the Posts folder…
1 Like
Hey Adam, just having a look through your videos. In the second one (Editor setup) you disable the meta tags and then add in the robot ‘noindex’ tag. Just curious why do you do that as opposed to just un-checking the RW ‘index this page’ checkbox?
1 Like
Disabling the “Enable Robot Meta Tags” simply tells RapidWeaver not to add in the following tag:
<meta name="robots" content="index, follow">
The second tag I add in the “Other Tags” section specifically tells search engines to ignore the page.
Are either necessary though? No. But it should help in keeping that Editor page you’re building from showing up in search results.
I thought that is what you get if you check ‘enable robot meta tags’ but uncheck the index/follow tags?
All ends up the same, I suppose, I was just curious if there was something specific about the RW-generated one vs doing it manually.
1 Like
Sure you can do it that way as well. Up to you. I did it that way because I prefer to see it written out myself. Lots of ways to do things in site design.
Just wanted to update those following this thread – I’ve just pushed Alloy v2.0 to the update server. If you’re an existing Alloy user you should be able to check for updates in Stacks momentarily and have access to the new update, which includes the Editor stack shown in the tutorial videos linked above.
If you’re just now checking Alloy out you will received the most up-to-date version when you make your purchase.
I’ve got a blog post written up on the Elixir site about this update that tells a bit more about this major upgrade. I’ve also got a secondary blog post talking about a Stacks quirk that I wanted to inform everyone about as well, which we encountered during the beta testing process.
I hope you all enjoy the new update, and I can’t encourage you enough to watch the tutorial videos for the Editor. At the bare minimum you will need to watch Part One as it walks you through the process of setting up your secure login, which is a requirement to use the Editor. I think everyone will greatly benefit from watching both videos though. They can be found on the Alloy Tutorials page (along with the very important Getting Started video), as well as I am linking directly to each video below for quick reference:
Getting Started: Getting Started wth Alloy - YouTube
Editor Setup: Alloy Editor Setup - Part One - YouTube
Using the Editor: Alloy Editor Setup - Part Two - YouTube
There is also a documentation page specifically for the Editor stack on the Alloy site, which covers what each of the stack’s settings do.
I really hope you all enjoy Alloy and the new Editor stack. A lot of time and energy went in to trying to make this tool both powerful, but also easy to use.
3 Likes
Fantastic job 
1 Like
Thanks @Fuellemann! Appreciate it. As always, nice reviews and a like are always welcome on the Community site. 
1 Like
This looks really, really, really fantastic, Adam. Despite the various options currently available on the market, there is still a need for simple online blogging Stacks. Emphasis on simple, which Alloy v2 very much seems to be. The only two hangups I see for myself so far are:
-
Grid view? Is there a way to have the Blog Entries page display the summaries as a grid (left-to-tight, top-to-bottom), rather than a list?
-
I’m redoing a blog for a photographer as part of their site, and I can see the inability to upload photos through the Editor as a deterrent, at least in the case of this particular client. I realize this is not possible at this time, so maybe just consider it a feature request? I’m aware it may never be possible, though, given how the Editor is constructed.
Thanks so much, Adam!
Thanks for the kind words @markwilliams!
No, that is not a feature of Alloy.
As I mentioned above…
It is something that has been discussed in the beta tester group previously. But as I said it isn’t something I’m active development at this time.
Likewise! 
The latest development of Alloy looks really good.
I have a site currently with an old RWWriter blog that I need to upgrade urgently. Is there an easy way to migrate from another blog to Alloy, or will it be a case of copy and paste all the old blog entries.
Also keen to know, does Alloy work well at sharing content onto social media platforms like Linked in. I have had problems in the past when using Blogger so dont want to go down that route again.
Thanks
1 Like
Thanks @MrB!
I’m guessing that you’re asking about OpenGraph and Twitter meta tags for each individual post. If that is the case, then yes, each post receives both sets of tags, and you can customize it with your own account details in the main Alloy Control Center stack. This allows for the social media “cards” you often see when linking to OpenGraph and Twitter meta tagged pages on platforms like Twitter, Facebook and the like.
It is going to be a copy and paste operation. If your current service has the ability to export each blog post to its own Markdown file that might speed things up a bit. You could then just add in the necessary YAML Front Matter for each post and then upload them to your posts folder using FTP. But most likely you’re probably going to be simply copying and pasting content.
1 Like